Hi Rich, Thanks a lot for starting this thread and driving this effort. I'm glad to offer help and join the force if it can have an umbrella issue/ticket that we can go into the concrete subtasks.
So far, I share some common feelings as you described above: * Super-high committer bars even trade committer titles with certain effort (25 PR = committer; this can encourage speculation instead of collaboration, and generally, the PMC will later find that the newly elected committers vanished since "the trade is finished"). * Committer/PMC elections influenced by company affiliation/role rather than by public discussion - Yes, of course. It may indicate another problem with the ability to say no and how we build such an environment. Besides, emphasizing the importance of a project's vision may also help since an OSS community exists to solve a specific range of problems. Without a clear definition of the vision, a project is at high risk to continue. Also, this can be a rectification for thinking too tightly of so-called "no code contributions". All the sentences I use above can be associated with one or more concrete real stories. I don't know if we use this story directly (vs. anonymously) in the advice page. Best, tison. <rbo...@rcbowen.com> 于2023年10月31日周二 22:47写道： > Hi, folks, > > As discussed various times on Slack, I am planning to create some > concrete, practical advice to our project communities about how to grow > their developer communities. I've put a bullet list here - > https://community.apache.org/communitybuilding/ - and will be > developing that over the coming year (I hope). > > I have become more than a little concerned about trends that I'm seeing > across the Foundation: Super-high committer bars with no real > justification; Ignoring contributors, who then eventually go away in > frustration; Off-list discussions that are then never discussed in the > view of the community; Committer/PMC elections influenced by company > affiliation/role rather than by public discussion. I am hoping that we > can address some of these by education, and by having "official" pages > that we can point to when projects are learning how to be ASF > projects. > > Yes, some of this happens in the Incubator. My concern is post- > incubator, when the decision-makers on the project arrives post- > incubator, and so don't benefit from that experience. A second- > generation problem, you might say. > > Anyways, as always, I welcome and appreciate your participation in > writing this stuff, and in organizing it. > > Thanks. > > --Rich > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
