You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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
The text was updated successfully, but these errors were encountered: