I'd like to be added to the Streaming Connectors component (already edited Wiki) :)
Ah, naming, one of the hardest problems in programming :P Some comments: I agree with Robert that the name "maintainers" will be somewhat misleading regarding the authoritative difference with committers / PMCs, especially for future newcomers to the community who don't come across the original discussion on this thread. Simone's suggestion of Overseer seems good. The name naturally matches its role - - A group of "Overseers" for components, who keeps an eye on related mail threads, known limitations and issues, JIRAs, open PRs, requested features, and potential new overseers and committers, etc, for the component (original maintainer role). - A "Shepherd" for individual PRs, assigned from the overseers of the component with the aim to guide the submitting contributor. Overseers typically pick up new PRs to shepherd themselves, or the leading overseer allocates an overseer to shepherd a PR which hasn't been picked up yet after a certain period of time. Or perhaps we can also simply go for "Shepherds" for components and "Assigned Shepherd" for individual PRs? -- View this message in context: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PROPOSAL-Structure-the-Flink-Open-Source-Development-tp11598p11932.html Sent from the Apache Flink Mailing List archive. mailing list archive at Nabble.com.
