[DRAFT] Proposal: Technical Guidance WG
nornagon opened this issue · comments
The most critical and decision-heavy areas of work in Electron—releases, security, and upgrades—have working groups dedicated to them. However, several other categories of work require ongoing attention, but don't perhaps merit the overhead of a dedicated working group and don't fall into any of the other major working groups. These categories are:
- API design
- Build infrastructure
- CI
- Performance
None of these areas are clearly the responsibility of any existing working group.
We propose the creation of a working group that would be responsible for technical guidance on matters that do not fall into the responsibility of other existing working groups and do not merit a full working group. This Technical Guidance Working Group would meet on an as-needed basis to resolve issues that arise in the above areas.
Every member of the Electron maintainers group is responsible for making sure that Electron is technically excellent. It is not the intent of this group to allow others to abdicate their responsibility for designing good APIs, fixing CI issues, or improving build infrastructure. The purpose of this group would be to resolve conflicts where they arise and to oversee initiatives related to crafting policy as it relates to the technical direction of Electron.
Thanks for writing this up, I have only two concerns:
- This will be the new “cool kids group” to be in. That might be okay, but we should acknowledge that.
- How do we ensure that we’re creating a culture where people and WG feel a sense of ownership, motivated and empowered to do work and make decisions?
Closing this issue as it was resolved in the Thu Feb 21 session