So interestingly, due to https://make.wordpress.org/community/feature-requests-for-community-sites/ – one must create a P2 post and also a Meta Trac ticket for any ideas to go through. (Incidentally, not everyone in the Community Team knows this).
This makes little sense in the grand scheme of things. In many of the tickets that I posted in the proposal post, the changes are pretty obvious and is unlikely to need any form of a debate. It just requires code changes.
In my opinion, only larger or controversial changes should require a P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. discussion. While I agree that the community team should take ownership of decision on it’s own systems, the way to do so is to actually discuss meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets that are worthy by having a Community Team member, take charge of these tickets and bring it out for discussion in the Community Team meetings.
Every other team does their bug scrub in a similar fashion and it is what WordPress developers like me are used to. This 2 step approach isn’t helpful (at least not for small issues)
My suggestion is moving forward – we should keep entry barriers as low as possible. Anyone can create a meta trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket, but not everyone can post to Make / Community.
- Non-developers who simply want to word their request / suggestion in P2 should continue to do so
- After approval, a technically inclined person (if needed) can post onto Meta Trac
- Developers who are used to trac should just create a ticket in trac
- This ticket can ideally be discussed and raised by the ticket creator in Community Team meetings
- Or, the Community Team can have a few people, possibly Ian – bring up some of these tickets for discussion. Afterall he looks through them.
https://wordpress.slack.com/archives/community-team/p1476945622000888 for some background