Add guidance to proposal section #53
Conversation
|
👍 |
|
I'd also like to see a bit about why a project would want to join the foundation, i.e. what they can expect from the process and why they might want that. |
| * what set of Node.js users is the project interesting/critical to ? | ||
| * is there a direct relationship between the project and core Node.js | ||
| or one of the existing top-level projects? For example is it a | ||
| Node.js dependency ? |
There was a problem hiding this comment.
I wonder if "is it a Node.js dependency" might be misinterpreted. Suggestion "does Node.js itself depend on it"
|
Nit: |
|
This looks like a useful starting point to me. LGTM, with a couple of really tiny nits. |
|
These are some good questions. The state of the docs here need a big re-working to get in-line with what we're already doing. It's very hard to figure out the TSC is doing in practice and what the Incubator is for. There's also a few tough questions we need to address that I'll be logging over the next few days. This is all just to say that I think that we should merge this but shortly after re-work the README, this doc, and most of the other docs as well. |
Add additional guidance to proposal section to call out that proposals need to explain how the project will better the Node.js ecosystem.
|
Updated to address review comments so far. |
|
LGTM |
|
Can this be landed ? |
|
Should be safe but let's put it on the tsc-agenda for tomorrow just to be extra safe ;-) I'll land it tomorrow if there are no objections. |
|
TSC has decided to delay this for now while we figure some mission-y things out. |
|
Don't think this is relevant anymore. |
Add additional guiance to proposal section to call out
that proposals need to explain how the project will
better the Node.js ecosystem.