-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identifying core initiatives + Find Champions #390
Comments
+1 from me, and other ideas of areas we should consider focusing initiatives around: #278 |
Another possible benefit: A clear set of core initiatives may also give the community a better sense of the roadmap, direction, and vision for the project. |
SGTM, also we can consider using the Github team and project to organize things better. These initiatives should be less formal than working groups but can make meetings when neccesary.
@ktrott +1 |
SGTM |
I would not necessarily use the term "roadmap" for these. They are areas that need coordinated attention in order to make progress. A roadmap implies that the resources are being officially dedicated and assigned to address those but that's not necessarily the case. The idea would be to identify these areas, identify who the champions are, and identify some reasonable path for how to get actively involved. I will put my name in as the "champion" for the Promise-based APIs in Core initiative as I have already started work on that. I'm also going to add a couple more initiatives:
|
@jasnell +1 on mentoring and the idea that it's not JUST a goal of CommComm. We can and should work together on this - please let the CommComm know how we can help the TSC in further enabling this, if we can. ❤️ |
For completeness we should include N-API as it is an ongoing inititiative. |
See nodejs/node#16414 & https://github.com/Fishrock123/bob I'm quite set on seeing this one through to the end one way or other. |
RE GYP, seems to me more then ever we should fork. The main benefit of upstreaming to Chromium was the code-review & CI setup, but that has recently became broken (also code-review eyeballs has reduced to 2 people) |
@refack Are you saying the Chromium code-review and CI are broken? Can you elaborate? |
@bnoordhuis has been looking at cmake as an alternative for build Node.js itself but I know that does not solve the overall GYP issue. |
@fhinkel Just for |
Initial implementation landed 🎉 |
Hey all. So I think that it is important that the TSC identify a number of "Core Initiatives" and find champions to own the process / keep the committee up to date.
What is a "Core Initiative"... I'll make up a definition right now 🎉
Examples:
Identifying "Core Initiatives" should make it easier for first time contributors to get involved in the project.
If the TSC prioritizes core initiatives it will make it easier for organizations to make decisions regarding headcount they are allocating to work on the project
We do have prior art with the NAPI and HTTP2 work that was done in a somewhat similar model.
edit: to clairfy, prioritization is in regards to how important the initiatives are, not prioritizing them over current work being done.
For example figuring out an SSL story for 10.x has a 6 month windows, it is very high priority. Fixing the installer, while important, is lower priority.
The text was updated successfully, but these errors were encountered: