Repository navigation
[key packages] Open Enrollment #144
Description
Split 3/3 of #105
For all those maintainers that are searching for help, we need to define groups standards,
best practices and any tooling support we provide to other packages.
This would need a defined process, but would open the support to the greater community.
What to discuss here
- Define a process to share all the tooling and know-how that will be build helping the Pilot and High Impact packages
- How a maintainer can ask for help to this group?
Activity
wesleytodd commentedon Jan 31, 2019
Not only how can the maintainer ask for help, but I think it should be something they can do with very little effort on both sides. Like a checklist submitted via PR here which any automation we support looks at, and for which we just need to review at most before merging.
JamesMGreene commentedon Feb 23, 2019
It's probably more formalized than we're hoping for but it might be worthwhile to review what the JS Foundation does for applying to have a project brought into the fold.
https://github.com/JSFoundation/TAC
dominykas commentedon Sep 18, 2019
Another related doc: https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md