What does this allow us to do that can't already be done today? The main gain I can think of is helping users find knowledgeable people (which could volunteer themselves today as part of a collaborative and inclusive community). There's not anything presently stopping individual committers from taking greater responsibilities for sections of code, issues, and PRs.
Jonathan G On 11/13/19, 9:59 AM, "Jeremy Mitchell" <[email protected]> wrote: I would like to propose the idea of open source component leads for TP, TO, TR, TM and TS. I think having a component lead would help with the following: - Help the release manager compile comprehensive release notes for that component - Help the release manager determine release scope related to that component (what to not cherry pick to a release) - Release candidate testing/validation for that component - Manage issues related to that component (i.e. apply labels (component, type and severity)) and close old/irrelevant issues. - Develop a first pass roadmap (maybe a roadmap.md file at the root of the component?) for that component and potentially create milestones and facilitate discussion around the roadmap/milestones. - Clean up old PRs for that component - Drive standards for that component IMO these component leads would probably need the following qualifications: - someone that works with the component on a day-to-day basis and is obviously very experienced with the component. - is a committer so they can do things like apply labels, create milestones, merge PRs, etc. Ideally these component leads would represent different companies, however, maybe that is a goal and not a requirement at the moment. I bring this up because I think having component leads would help the quality, organization and transparency of the TC project as a whole and would provide potential contributors with a better vision of where TC is headed. Thoughts? Jeremy
