Skip to content

Commit 0ab9eb3

Browse files
hackygoluckymikeal
authored andcommitted
Add Education initiatives and Outreachy to Foundation section of website (#929)
* update signup form * add education and outreachy under Foundation * add education initiative copy * add outreachy copy
1 parent 2c26585 commit 0ab9eb3

File tree

4 files changed

+222
-6
lines changed

4 files changed

+222
-6
lines changed

locale/en/foundation/education.md

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
---
2+
title: Education Initiatives
3+
layout: foundation.hbs
4+
---
5+
6+
## Education in Node.js
7+
8+
Here we will ask fun questions like, 'what is education in [Node.js](https://nodejs.org/en/)?'
9+
10+
Notice we didn't say 'answer'? Education initiatives from the Node.js Foundation explore what it means to be learning Node.js. Who uses it? How are folks learning it? How can we as a community make the experience better and inclusive for existing users and rad, diverse group of learners?
11+
12+
A few people who are exploring this currently:
13+
14+
- [Tracy Hinds](https://twitter.com/HackyGoLucky), Education Community Manager for the Node.js Foundation
15+
- Education Advisory Group for the Node.js Foundation
16+
- Lots of awesome community folks who have been doing cool stuff for a while in Node.js and deserve to be heard, like you!
17+
18+
Please participate. [File issues, PRs, and create the community you'd like to be a part of](https://github.com/nodejs/education).
19+
20+
21+
### Roadmap
22+
23+
This roadmap is a living document, and it is likely that priorities will change, but the items below should give some indication of education initiatives for this calendar year.
24+
25+
**Certification**
26+
27+
The Node.js Foundation (in partnership with The Linux Foundation) will be performing the following tasks to build and ship the Node.js certification:
28+
29+
- Define Certification(s), the number of levels (parallel or sequential), titles, program goals
30+
- Define Scope Statement of Certification
31+
- Define the in-browser hosted exam environment which will be provided to candidates. Must be exactly reproducible and consistent in function.
32+
- Conduct job task analysis(JTA) which is to define the Domains of work and corresponding Tasks within each domain a Certification Candidate should be able to perform
33+
- Define the exam blueprint containing the specific exam Domains and Tasks and their relevant weight within the exam(Domains and Tasks will be opensourced. Blueprint will be secure and not public facing, testrunner will also be opensourced).
34+
- Publish determined domains and tasks for ecosystem to prepare complementary trainings with ample notice.
35+
- Write performance-based exam items (problems to solve) based on the Domains and Tasks defined by the JTA
36+
- Exam items must be written and formatted to comply with an auto-grade script that is run on answers provided (i.e. machine-gradeable)
37+
- Consideration of non-English speaking users including items written in a way that they are translatable
38+
39+
- Provide subject matter expert (SME) support and review to
40+
- Script and program the exam items
41+
- Set-up Certification registration portal
42+
- Deploy the exam
43+
44+
- Conduct secure pilot testing (alpha, beta)
45+
- Determine the exam passing score via psychometrician-led standard setting process
46+
- Support the public launch of the exam including program marketing
47+
- Manage certification program including:
48+
- Creation and documentation of program policies and procedures (Candidate Handbook, Candidate Agreement, etc.)
49+
- Technical support and help desk
50+
- Candidate appeals and sanctions considerations
51+
- Regular SME advisory from cert advisory board and consultants
52+
- Regular renewal of job analysis and item creation (example: every 3 years)
53+
54+
55+
Work may be organized into committees or subcommittees representing, but not limited to the following:
56+
57+
- Job Analysis Committee--define the Domains of work and corresponding Tasks within each domain a Certification Candidate should be able to perform
58+
- Item Writing Committee--writing/developing the individual item tasks into problems for the exam.
59+
- Standard Setting Committee--will set the passing/cut score. This process is led by the psychometrician. Aggregation of scores weighted by the committee.
60+
- Certification Advisory Board--perspectives from industry experts for the cert lead(education community manager) for essential decisions related to standards, policies, and procedures of the certification.
61+
62+
Work will be divided into collaborative group sessions and individual self-paced assignments in accordance with project schedule. Time commitments will vary.
63+
64+
**Docs**
65+
- Stay tuned and help your friends at the [Docs WG](https://github.com/nodejs/docs)
66+
67+
**Resources for learning Node.js**
68+
- Stay tuned and participate [in our convos](https://github.com/nodejs/education/issues/4)
69+
70+
71+
## Contact
72+
73+
For questions about education initiatives or a little inspiration, please send an
74+
email to <a href="mailto:[email protected]?subject=Education-questions">[email protected]</a>.
75+
76+
<!-- Begin MailChimp Signup Form -->
77+
<link href="//cdn-images.mailchimp.com/embedcode/classic-10_7.css" rel="stylesheet" type="text/css">
78+
<style type="text/css">
79+
#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
80+
/* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
81+
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
82+
</style>
83+
<div id="mc_embed_signup">
84+
<form action="//nodejs.us14.list-manage.com/subscribe/post?u=c7c2e114a827812354112c23b&amp;id=f5f8d4eddb" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
85+
<div id="mc_embed_signup_scroll">
86+
<h2>Subscribe to get updates and give input for education initiatives</h2>
87+
<div class="indicates-required"><span class="asterisk">*</span> indicates required</div>
88+
<div class="mc-field-group">
89+
<label for="mce-EMAIL">Email Address <span class="asterisk">*</span>
90+
</label>
91+
<input type="email" value="" name="EMAIL" class="required email" id="mce-EMAIL">
92+
</div>
93+
<div class="mc-field-group">
94+
<label for="mce-FNAME">First Name </label>
95+
<input type="text" value="" name="FNAME" class="" id="mce-FNAME">
96+
</div>
97+
<div class="mc-field-group">
98+
<label for="mce-LNAME">Last Name </label>
99+
<input type="text" value="" name="LNAME" class="" id="mce-LNAME">
100+
</div>
101+
<div id="mce-responses" class="clear">
102+
<div class="response" id="mce-error-response" style="display:none"></div>
103+
<div class="response" id="mce-success-response" style="display:none"></div>
104+
</div> <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
105+
<div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_c7c2e114a827812354112c23b_f5f8d4eddb" tabindex="-1" value=""></div>
106+
<div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div>
107+
</div>
108+
</form>
109+
</div>
110+
<script type='text/javascript' src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'></script><script type='text/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';}(jQuery));var $mcj = jQuery.noConflict(true);</script>
111+
<!--End mc_embed_signup-->

locale/en/foundation/index.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -62,12 +62,9 @@ email to <a href="mailto:[email protected]?subject=Trademark">trademark@nodej
6262
#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
6363
/* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
6464
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
65-
#mc_embed_signup form {
66-
padding: 0px 0px 0px 0px;
67-
}
6865
</style>
6966
<div id="mc_embed_signup">
70-
<form action="//nodejs.us14.list-manage.com/subscribe/post?u=c7c2e114a827812354112c23b&amp;id=e842100924" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
67+
<form action="//nodejs.us14.list-manage.com/subscribe/post?u=c7c2e114a827812354112c23b&amp;id=f006b61f29" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
7168
<div id="mc_embed_signup_scroll">
7269
<h2>Subscribe to our Node.js project newsletter mailing list</h2>
7370
<div class="indicates-required"><span class="asterisk">*</span> indicates required</div>
@@ -88,10 +85,10 @@ email to <a href="mailto:[email protected]?subject=Trademark">trademark@nodej
8885
<div class="response" id="mce-error-response" style="display:none"></div>
8986
<div class="response" id="mce-success-response" style="display:none"></div>
9087
</div> <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
91-
<div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_c7c2e114a827812354112c23b_e842100924" tabindex="-1" value=""></div>
88+
<div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_c7c2e114a827812354112c23b_f006b61f29" tabindex="-1" value=""></div>
9289
<div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div>
9390
</div>
9491
</form>
9592
</div>
9693
<script type='text/javascript' src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'></script><script type='text/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';}(jQuery));var $mcj = jQuery.noConflict(true);</script>
97-
<!--End mc_embed_signup-->
94+
<!--End mc_embed_signup-->

locale/en/foundation/outreachy.md

Lines changed: 100 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
---
2+
title: Outreachy + Node.js
3+
layout: foundation.hbs
4+
---
5+
6+
### Outreachy
7+
8+
**Welcome to Node.js + Outreachy**
9+
Outreachy provides a collaborative environment in which newcomers from underrepresented backgrounds can get help working on their first contributions and a focused opportunity for them to dedicate a full-time effort to learning and contributing to FOSS. The program also assists people with finding mentors to help them with their projects. By participating in the program, interns develop a good understanding of the power of FOSS and skills necessary to continue contributing to it.
10+
11+
The Node.js project is excited to partner with Outreachy to invite newcomers with diverse perspectives into our community for the December 2016 cohort.
12+
13+
Participation is open internationally to all women (cis and trans), trans men, and genderqueer people. Additionally, it's open to residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. We are planning to expand the program to more participants from underrepresented backgrounds in the future.
14+
15+
**Quick links**
16+
17+
- [The Node.js project on GitHub](https://github.com/nodejs/node)
18+
- [Getting started for applicants](https://wiki.gnome.org/Outreachy#Introduction)
19+
- [Mentor prep](https://wiki.gnome.org/Outreachy/Admin/InfoForMentors)
20+
21+
**Schedule**
22+
23+
- October 17: application deadline at 7pm UTC
24+
- October 17 - November 8: applicants are encouraged to continue making contributions for the project they applied for; submitted applications are open for editing
25+
- November 8: accepted participants announced on this page at 4pm UTC
26+
- December 6, 2016 - March 6, 2017: internship period
27+
28+
**What is Node.js?**
29+
From our guiding principles, "The goal of the Node.js project is to provide a JavaScript-based application development platform that is current, reliable, and stable.
30+
31+
Contributors to Node.js work on behalf of the community of users who build their applications and businesses with the Node.js platform. Accordingly, contributors must demonstrate an ongoing commitment, not only to the Project, but to the stability and vitality of the community as a whole...
32+
33+
The Node.js community is large, inclusive, and excited to enable as many users to contribute in whatever way they can. If you want to report an issue, help with documentation or contribute to the code base of the project, you’ve come to the right place."
34+
35+
**PARTICIPANTS**
36+
37+
How can I familiarize myself with the community and project?
38+
39+
- We’re on IRC! Connect to irc.freenode.net in the #node.js channel with an IRC client or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js).
40+
41+
- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
42+
- Read more about our [contributing](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md) and [collaborator](https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md) guidelines
43+
- Check out some of our [international communities](https://nodejs.org/en/get-involved/)
44+
- Introduce yourself to the project's mentors and discuss what your tasks during the internship program would be.
45+
46+
**How to apply and application tips**
47+
48+
The application process is described in detail at https://wiki.gnome.org/OutreachProgramForWomen#Send_in_an_Application. A contribution is required and you answer questions when you apply. You are expected to work full-time on the internship although you can indicate any pre-planned time off in your application.
49+
50+
In order to make your application stronger, here are a few things you could consider including:
51+
52+
- Previously worked projects/coding experience. If it is docs, related experience if any
53+
- What do you intend to learn from the selected project? Or rationale behind choosing the specific project
54+
- How do you think this internship is going to help you achieve what you wanted?
55+
- Your next choice of projects if your first choice is not available
56+
57+
Also include information or link on your merged patch (which is a requirement to be considered for the internship). Please be available and responsive throughout the application period so we can work with you on improving your application.
58+
59+
**Questions about the Node.js project?**
60+
61+
With open source, just finding out where to ask your question can be intimidating. Email [Tracy Hinds]([email protected]) if you have any questions during the application process and she’ll be happy to find the person most helpful, if she isn’t it.
62+
63+
**MENTORS**
64+
65+
For information about expectations for mentors and to volunteer to be a mentor, see [Outreachy mentors](https://wiki.gnome.org/Outreachy/Admin/InfoForMentors).
66+
67+
The volunteer mentors are:
68+
69+
- [Franziska Hinkelmann](https://plus.google.com/u/1/116713283748910059509?prsrc=4)
70+
- [Rich Trott]([email protected]), IRC: Trott
71+
- [Dan Shaw]([email protected]), IRC: dshaw
72+
- [Myles Borins]([email protected] ), IRC: thealphanerd
73+
- [Priyanka Sulugodua Prakash Murthy]([email protected])
74+
75+
**Project administrator**
76+
77+
- Tracy Hinds, Education Community Manager at the Node.js Foundation Reach her at [[email protected]]([email protected]) or on IRC: hackygolucky
78+
79+
**PROJECTS**
80+
**Improve the vm module in Node.js core**
81+
*Mentor:* [Franziska Hinkelmann](https://plus.google.com/u/1/116713283748910059509?prsrc=4)
82+
The vm module is used in the Node.js command line and in DOM implementations, such as jsdom. Sadly, there are many open issues related to the module and it needs some love. Recent changes in V8, Node's JS engine, now make it possible to fix several of the issues and improve the vm code base significantly.
83+
84+
This project includes learning how to build and debug Node.js core, how the vm module is implemented, some Node internals about the global proxy, and how to use the V8 API. You will be coding in C++ and write tests in JavaScript. No worries if you're not too familiar with these languages, a desire to learn and curiosity are much more important than a fixed skill set.
85+
86+
Mentor based in Europe.
87+
https://github.com/nodejs/node/issues/6283
88+
89+
90+
**Project TBD**
91+
[Rich Trott]([email protected])
92+
93+
**Project TBD**
94+
[Dan Shaw]([email protected])
95+
96+
**Project TBD**
97+
[Myles Borins]([email protected] )
98+
99+
**Project TBD**
100+
[Priyanka Sulugodua Prakash Murthy]([email protected])

locale/en/site.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,14 @@
128128
"announce": {
129129
"link": "foundation/announcements",
130130
"text": "Announcements"
131+
},
132+
"education": {
133+
"link": "foundation/education",
134+
"text": "Education Initiatives"
135+
},
136+
"outreachy": {
137+
"link": "foundation/outreachy",
138+
"text": "Outreachy + Node.js"
131139
}
132140
},
133141
"getinvolved": {

0 commit comments

Comments
 (0)