chore: update templates and scripts

Author: kgryte

organization/scripts/acceptance_emails.js

@@ -27,6 +27,8 @@ var mustache = require( 'mustache' );
 var mkdirp = require( 'mkdirp' ).sync;
 var readFile = require( '@stdlib/fs-read-file' ).sync;
 var writeFile = require( '@stdlib/fs-write-file' ).sync;
+var currentYear = require( '@stdlib/time-current-year' );
+var format = require( '@stdlib/string-format' );
 var ENV = require( '@stdlib/process-env' );
 var parseCSV = require( './parse_csv.js' );
 
@@ -50,7 +52,7 @@ var TMPL = readFile( tpath, FOPTS );
 var dpath = resolve( __dirname, 'tmp', 'accepted.csv' );
 var DATA = parseCSV( readFile( dpath, FOPTS ) );
 
-var SUBJECT = '[GSoC 2024] Congratulations! Your stdlib proposal was accepted!';
+var SUBJECT = format( '[GSoC %d] Congratulations! Your stdlib proposal was accepted!', currentYear() );
 
 
 // FUNCTIONS //

organization/scripts/announcement.js

@@ -58,7 +58,7 @@ var DATA = parseCSV( readFile( dpath, FOPTS ) );
 */
 function params() {
 	return {
-		'number_of_applications': NUM_APPS,
+		'number_of_accepted_applications': NUM_APPS,
 		'coding_start_date': CODING_START,
 		'sender_name': SENDER,
 		'projects': []

organization/scripts/rejection_emails.js

@@ -27,7 +27,9 @@ var mustache = require( 'mustache' );
 var mkdirp = require( 'mkdirp' ).sync;
 var readFile = require( '@stdlib/fs-read-file' ).sync;
 var writeFile = require( '@stdlib/fs-write-file' ).sync;
+var currentYear = require( '@stdlib/time-current-year' );
 var ENV = require( '@stdlib/process-env' );
+var format = require( '@stdlib/string-format' );
 var parseCSV = require( './parse_csv.js' );
 
 
@@ -47,7 +49,7 @@ var TMPL = readFile( tpath, FOPTS );
 var dpath = resolve( __dirname, 'tmp', 'rejected.csv' );
 var DATA = parseCSV( readFile( dpath, FOPTS ) );
 
-var SUBJECT = '[GSoC 2024] Proposal notification - stdlib';
+var SUBJECT = format( '[GSoC %d] Proposal notification - stdlib', currentYear() );
 
 
 // FUNCTIONS //

organization/templates/acceptance.md

@@ -20,7 +20,7 @@ GSoC projects have flexible timelines. Right now your project is set to the defa
 
 The community bonding period from {{bonding_start_date}} to {{bonding_stop_date}} begins now.
 
-http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html.
+http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html
 
 You should spend this time to get up to speed with the community, and to set up regular meetings with your mentors for the coming months. We'll be inviting you to our internal Slack channel shortly so you can connect with mentors and other maintainers more directly.
 

organization/templates/announcement.md

@@ -10,11 +10,11 @@ Contributor, Project: Mentors
 {{/projects}}
 Join me in congratulating them on their acceptance.
 
-I would like to thank all of the contributors who applied this year and everyone who submitted a patch. We certainly hope that you will remain a part of our community. I would also like to thank all the mentors for helping review patches and proposals.
+I would like to thank all of the contributors who applied this year and everyone who submitted a patch. We certainly hope that you will remain a part of our community. As one inspiring success story, one of the contributors selected this year was rejected last year, but stuck with it, engaged more deeply with the community, and successfully landed a project. In short, persistence pays off! 
 
 To everyone whose proposal is accepted, you should be receiving an email from your mentors shortly to discuss how you will be communicating over the summer about your project. You should meet with your mentors about once a week during the summer to go over your progress.
 
-I would like all project maintainers to strongly encourage GSoC contributors to submit pull requests early and often. This will go a long way toward making sure that you don't end the summer with a ton of code written that never gets merged. Contributors should help review pull requests by other contributors, so that we don't get bogged down reviewing too much code.
+I would also like to thank all the mentors for helping review patches and proposals. I would like all project maintainers to strongly encourage GSoC contributors to submit pull requests early and often. This will go a long way toward making sure that you don't end the summer with a ton of code written that never gets merged. Contributors should help review pull requests by other contributors, so that we don't get bogged down reviewing too much code.
 
 The GSoC coding period officially starts {{coding_start_date}} (https://developers.google.com/open-source/gsoc/timeline).
 

package.json

@@ -35,7 +35,9 @@
     "@stdlib/process-env": "^0.2.1",
     "@stdlib/regexp-eol": "^0.2.1",
     "@stdlib/string-base-snakecase": "^0.2.1",
+    "@stdlib/string-format": "^0.2.2",
     "@stdlib/string-trim": "^0.2.1",
+    "@stdlib/time-current-year": "^0.2.2",
     "mkdirp": "^0.5.1",
     "mustache": "^4.0.0"
   },