Title: Community Team should take ownership / look at WordCamp Meta tickets
Author: Jon (Kenshino)
Published: November 3, 2016

---

 [  ](https://profiles.wordpress.org/kenshino/) [Jon (Kenshino)](https://profiles.wordpress.org/kenshino/)
6:09 am _on_ November 3, 2016      

# Community Team should take ownership / look at WordCamp Meta tickets

**Proposal:**

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](https://make.wordpress.org/community/2016/11/03/proposal-various-changes-to-wordcamp-site-and-plugins/),
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 P2P2 P2 or 
O2 is the term people use to refer to the Make WordPress blog. It can be found at
[https://make.wordpress.org](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 metaMeta 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 tracTrac Trac is the place where contributors create issues
for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](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

Cheers!

### Share this:

 * [  Threads ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=bluesky)
 * [  Facebook ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=facebook)
 * [  X ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=x)
 * [  LinkedIn ](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcommunity%2F2016%2F11%2F03%2Fcommunity-team-should-take-ownership-look-at-wordcamp-meta-tickets%2F%23respond&locale=en_US)

 1.  ![](https://secure.gravatar.com/avatar/5783a2d9b93f04f6d0a1ddabddcfd71f15136d7eaea7a87f9962d3f93f780224?
     s=32&d=mm&r=g)
 2.   [Ian Dunn](https://profiles.wordpress.org/iandunn/)  1:44 am _on_ November 5,
     2016
 3.  > the changes are pretty obvious and is unlikely to need any form of a debate
 4.  I think the person proposing something is almost always going to think that the
     change is obvious and should just be accepted 😉
 5.  A lot of the smaller requests don’t seem bad on the surface, but there’s often
     good reason to say no to them when they’re examined from a broader perspective.
     For example, people tend to propose small improvements, but those end up taking
     a disproportionate amount of development time to review, merge, and maintain. 
     That takes time away from projects that have a large impact.
 6.  > discuss metaMeta 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.
 7.  A regular ticket scrub in SlackSlack Slack is a Collaborative Group Chat Platform
     [https://slack.com/](https://slack.com/). The WordPress community has its own 
     Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
     sounds like it could be helpful. It’d exclude some people because of time zones,
     but maybe for smaller uncontroversial stuff that’d be ok?
 8.  > we should keep entry barriers as low as possible
 9.  I hear you, the current process is cumbersome. I think there were good reasons
     to switch to it, but it has its own problems, so I’m glad you brought all this
     up.
 10. I think creating a p2 post is easier for many people than learning TracTrac Trac
     is the place where contributors create issues for bugs or feature requests much
     like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).,
     because Trac’s UXUX UX is an acronym for User Experience - the way the user uses
     the UI. Think ‘what they are doing’ and less about how they do it. is awful, though.
 11. **For all the deputiesProgram Supporter Community Program Supporters (formerly
     Deputies) are a team of people worldwide who review WordCamp and Meetup applications,
     interview lead organizers, and keep things moving at WordCamp Central. Find more
     about program supporters in our [Program Supporter Handbook](https://make.wordpress.org/community/handbook/community-deputy/).
     and Central staff: how do you feel about Trac?** Would you be willing to use it,
     or do you prefer having these kinds of discussions on the p2? What do your ideal
     process look like?
 12. 
     ### Other solutions?
     
 13. I also wonder if there are other solutions, like [UserVoice](https://uservoice.com).
     Something like that would be great because it would let everyone vote on proposals,
     but they’d only get a certain number of credits, so they’d have to prioritize.
 14. That’s very important since we have such limited resources. People will often 
     say they want some new thing, but they’d say no if they realized that it meant
     they’d have to give up something else, which is always the reality.
 15. It’d be really nice if we could have a single tool that everyone could use, rather
     than having things split between Trac and p2.
 16. We could also look at fixing some of Trac’s UIUI UI is an acronym for User Interface-
     the layout of the page the user interacts with. Think ‘how are they doing that’
     and less about what they are doing. problems. CoreCore Core is the set of software
     required to run WordPress. The Core Development Team builds WordPress. has made
     their new ticket form much simpler by removing unnecessary options, etc.
 17.  * ![](https://secure.gravatar.com/avatar/241584c8900ae5ccd62ff4c9db7d58e58bc9e0dc0162d4bdcac2a916d586c7ed?
        s=32&d=mm&r=g)
      *  [Francesca Marano](https://profiles.wordpress.org/francina/)  11:14 am _on_
        November 30, 2016
      * > For all the deputiesProgram Supporter Community Program Supporters (formerly
        > Deputies) are a team of people worldwide who review WordCamp and Meetup applications,
        > interview lead organizers, and keep things moving at WordCamp Central. Find
        > more about program supporters in our [Program Supporter Handbook](https://make.wordpress.org/community/handbook/community-deputy/).
        > and Central staff: how do you feel about TracTrac Trac is the place where
        > contributors create issues for bugs or feature requests much like GitHub.
        > [https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).? Would
        > you be willing to use it, or do you prefer having these kinds of discussions
        > on the p2? What do your ideal process look like?
      * I think having all discussions in Trac would be awesome + ticket scrub once
        a month? bi-monthly?

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/community/2016/11/03/community-team-should-take-ownership-look-at-wordcamp-meta-tickets/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcommunity%2F2016%2F11%2F03%2Fcommunity-team-should-take-ownership-look-at-wordcamp-meta-tickets%2F&locale=en_US)
to post a comment.

# Post navigation

[← Proposal: Various changes to WordCamp site and plugins](https://make.wordpress.org/community/2016/11/03/proposal-various-changes-to-wordcamp-site-and-plugins/)

[WordPress Community Summit 2017 →](https://make.wordpress.org/community/2016/11/03/wordpress-community-summit-2017/)