Next Node.js Certified Developer Contributors Meeting

[bnb]

Per the meeting today (#7), we wanted to get another meeting on the Calendar to discuss next steps as a group.

I wanted to be sure that we included everyone in this process, including those that didn't have a chance to participate in the discussion today - I went ahead and created the @nodejs-certified-developer/contributors team to make sure everyone can be made aware as effectively as possible.

Mark has planned for the next meeting to be on March 22nd at 11:00am ET. We're trying to accommodate many time zones here, so hopefully that will work for almost everyone. If we need to tweak it for more individuals to be able to make it, we can definitely attempt that for the next meeting 👍

[mrhinkle]

The call information is here:

Topic: Node.js Certification Meeting
Time: Mar 22, 2018 11:00 AM Eastern Time (US and Canada)

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/601197698

Or iPhone one-tap :
US: +16465588656,,601197698# or +16699006833,,601197698#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
Meeting ID: 601 197 698
International numbers available: https://zoom.us/zoomconference?m=0VdFdwxfdveMJeNogF1dmqbAbCNCA_qB

[mrhinkle]

Meeting Notes - March 22, 2018

Attendees:
Mark Hinkle, Node.js Foundation Executive Director
Caitriona Mulholland: LF Certification Team
Chetan, Node Contributor
David Clements, Principal Architect, Nearform
Jayco, NodeSource
Ruy Adorno, Node Contributor
Thomas Hunter II, Intrinsyc
Tierney Cyren, Developer Advocate at Node Source, Community Chair
Annie Fisher, Project Manager
Nathan White
Liz Kline, LF Certification Team

Intro to Call: Preparing for Alpha, bringing this group together to finish up the great work already accomplished by Tracy Hinds and team.

Background & Next Steps:

HackerRank is the testing environment for the exam.

Four individuals have been issued codes to do preliminary testing, reviewing for any “show stoppers” prior to launching into Alpha. Candidate handbook is being reviewed and updated as well.

REQUEST: Please take the exam prior to our next session (Thursday, March 29th)

Initial Concerns:
Version concerns
Response: compatibility should not be a worry, approaches to answers may be the issue, which would require tweaking rather than re-writes.
Ordering of questions: asking testers to review to make sure questions are grouped properly, in the correct order.
Response: Questions are pretty independent. Suggest starting with java, but shouldn’t be any hard dependencies.
Remember: if alpha testing, you are disqualifying yourself from the NCD. Will recognize all instead as the Developers of the Exam.
All agree: Priority is moving forward. Technical input will be needed for all bugs id
Next steps:
Evaluator test takers (codes have been sent out to identified test takers) - please take by next session.
Alpha testing period, then survey those test takers for fixes, bugs, enhancements, etc.
Pass fail ratio is reasonable? would be one thing we’re looking for in this round
Plan for updating test in light of updates
Remember, by taking NCD exam, this reflects that you are a developer of the LATEST release, thus update plan must support.
Suggestion: Track to the last update (version control) on a timeline for updates, so have it align with the feature lock down date of the new version, then set this as cadence. NOTE: This will be difficult to align with the community.
Hybrid approach: Looking to hire someone to handle maintenance.

1. Framework that provides a feedback loop for Community contributions
2. Vendor/Contractor to keep up to date on a regular basis
   Suggest utilizing this group for community response to the tasks prioritization for this vendor/group. Will keep this weekly meeting for the feedback loop.
   Next week: Feedback on Alpha, identify & review maintenance proposals (vendor identification, development of statement of work)
   Suggested next steps: Potential vendors put forth proposals, then these are evaluated by Mark & sub-sect of Community. SOW would be based on what are the more relevant identified priorities, and would be a 6 month, year project and would provide direction on service pre and post launch.
   Make sure all of the content for Cert. is reflective of the current LTR cycle, informed by process from Cert. Committee
   Exam is updated within 30 days of LTS release
   Bugs reported by test takers are addressed technically and work with HR framework
   Service level applied
   Group will start to put together an RFP and send to Mark before next meeting. Node.js staff will then review for any issues, fill in as needed, required. This would level the playing field and estimating.
   ACTION: Mark will add this to Github: PR new file in NCD Certfiication repo: name RFP.md - then group can provide feedback from there. This will go out to all members (public repo).