Make WordPress Core

Tagged: community Toggle Comment Threads | Keyboard Shortcuts

  • Jen Mylo 11:45 pm on December 8, 2012 Permalink
    Tags: community,   

    Team Reps for Core Team 

    I was going to wait until after 3.5 came out to post this, but since you all have the weekend free now, might as well take advantage of it, right? Time to vote for team reps again!

    Right now there are 8 team reps for core team. Count ‘em, 8! (Counting them: Boren, Jaquith, Nacin, Koop, Aaron Campbell, Scribu, DH-Shredder, and Helen). We need to whittle that down to 2 so that there’s more balance with the other contributor groups. Much simpler voting this time around: just write down the names of the two people you’d like to see as team rep. From now on we’ll be doing these votes every 6 months so we can share the responsibilities and continue to grow new leaders.

    Consider before you vote:

    • People you vote for should WANT to be the team rep, since there are responsibilities involved. People willing to do the job can help voters by leaving a comment on this post saying they are interested in being a team rep this term.
    • Team reps should not already be responsible for another group (and realistically, probably shouldn’t be the release lead, but that’s hard to guess at since the 6 months between team rep votes isn’t the same as the time frame for release cycles).

    Easy-peasy, yeah? Voting will end on December 15, so vote before then, please.

    Here’s a big, easy-to-spot link to the voting survey!

    Longer explanation of team reps, why we’re voting now, etc after the jump if you don’t know the background or weren’t around when we did team reps before.

    (More …)

     

    • helen 12:07 am on December 9, 2012 Permalink | Log in to Reply

      Guess I’ll ask that folks not put in a vote for me. I was very flattered to be recognized the first time around, and will happily do it again in the future, but expecting a baby right around the start of April makes me a bad choice for this period :)

  • Jen Mylo 7:45 pm on April 5, 2012 Permalink
    Tags: community, ,   

    Organizing Our Contributor Groups 

    Hi there, core contributors (and those who follow them). One of the things I’ve been meaning to do in the contributor community for the last 3-4 years is organize it so that when we say “contributor” it doesn’t just mean core code and the different contributing groups can all be on the same page. You may have seen some surveys sent/posted to the forums/docs/theme review teams etc. Your turn!

    In order to create a closer relationship between all the contributor groups, ensure our policies and agendas don’t conflict, recognize outstanding contributors, and just generally level up, we need some organization. To wit:

    • I’d like to identify who the active contributors are in each group.
    • I’d like to appoint someone from each group (based on votes from the active group participants) as a group liaison to the rest of the WP project and any cross-team initiatives to improve communication.
    • I’d like to set up a central P2 for communicating project-wide things so that no contributor group ever has to hear important announcements after the fact and we can discuss any issues that come up that could use the help/attention of people from other groups (including core).
    • I’d like to try and set up a monthly IRC chat and/or Google hangout for the liaisons to have some real-time communication.
    • I’d like to organize an annual contributor summit. Similar to the core team meetup concept, but more inclusive.

    The core code contributor team is the most in the know right now, but I’d like to make things a little more equal. Even within core, sometimes I hear people saying they wish they had more of a voice. The way the survey is set up, first you’ll pick how many reps you think core needs to have in the game (just one for core, or a couple, with each representing a different level of experience/seniority to make sure more issues/concerns are heard?), then you’ll vote on who you think the rep(s) should be. Note that inclusion in the survey does not mean that person has agreed to be a rep… I just pulled from our credits list and teams page for 3.4. Once the votes are in, I’ll contact people to see if they’re up for it.

    The survey is at http://wordpressdotorg.polldaddy.com/s/core-contributors
    and is password protected to help reduce spam responses: core2012

    If you could fill it in before the weekend is over (or right now… it’s only a few multiple choice questions), that would be great.

    Thanks!

     

    • Pete Mall 7:53 pm on April 5, 2012 Permalink | Log in to Reply

      1. Didn’t need the password.
      2. I think the conditionals are screwed up. It seems to be asking me all questions no matter what I picked (1/2/3… reps).

    • Jon Brown 8:34 pm on April 5, 2012 Permalink | Log in to Reply

      Took me a minute to figure out what you meant by Q.9. I’m assuming you mean representatives _at the core community summt_ mentioned in Q.7?

      Also do you really want “people that just follow core” to fill this out?

      • Jane Wells 8:57 pm on April 5, 2012 Permalink | Log in to Reply

        Realistically, only people who consider themselves contributors ought to submit a survey. That said, if some extra people fill it in, it’s not that big a deal. It asks for names, so I can double check status if it looks fishy.

    • Mert Yazıcıoğlu 9:05 pm on April 5, 2012 Permalink | Log in to Reply

      A little off topic but I think the “Core Contributor” term needs to be expanded a tiny little bit. Authors of accepted patches get the “props” (which is right) but people who report the bug itself do not. As far as I know, Core Contributors list is generated by a script that checks “props” in the commit messages and I think it is unfair because a person who reports 100 bugs gets no credit while a guy who submits a simple patch do get.

      Am I missing something?

      • Jane Wells 8:05 am on April 6, 2012 Permalink | Log in to Reply

        “Core contributor” has traditionally been shorthand for “core code contributor” or “core developer,” while testers have been another contributor group, though there is frequent overlap (much like forums + docs). I haven’t done the survey for testers yet, as I am making my way through the groups one by one.

      • Mark 8:37 am on April 6, 2012 Permalink | Log in to Reply

        If you wanted to widen this – someone who answers 1,000 or 10,000 forum questions to help the community at the http://wordpress.org/support forums gets zero acknowledgement while someone who contributes a 10 line patch gets a credit. WP is nothing without all these people.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel