Jen 6:36 pm on September 5, 2013
Tags: team reps ( 27 )

New Team Reps

For teams that sent in two names, per the previous discussion only one is going to be the listed rep for these next 3 months. Having a backup that can fill in if you’re sick can be at the discretion of the team dynamic how you want that to work.

Documentation: Eric Amundson (new)
Support: Jan Dembowski (new)
Theme Review: Emil
PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Review: Pippin
Mobile: Isaac
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.: Sam
Community Outreach: Amy
Polyglots: Remkus He promised they will do updates this time. 🙂
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: TBD, they talked about it in yesterday’s dev chat and I posted to make/core asking for result

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): Joseph O’Connor
Why is accessibility listed differently? At previous team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. discussions we talked about only having team reps for groups responsible for specific products/things, and having groups that were more aspect-based that might contribute to multiple product teams (such as accessibility and 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.) get their reporting done via the teams where the specific actions were relevant, so that they’d be more hooked in to the main groups and the updates would be grouped by product. We can discuss this again if feelings have changed, but in the meantime I’ll go ahead and list Accessibility here as a standalone until such time that we do the legwork necessary to make sure their updates are being covered by the product teams.

I’ll get in touch with each team rep this week to confirm their understanding of the role, and will re-write the description on the about page.

#team-reps

Emil Uzelac 6:38 pm on September 5, 2013

Thanks Jen 🙂
Jose Castaneda 7:43 pm on September 5, 2013

Awesome! Keep up the good work folks! 🙂
Marko Heijnen 8:51 pm on September 5, 2013

I’m really curious how this process went. It seems the open way of choosing has gone for some groups.
- Jen Mylo 9:52 pm on September 5, 2013
  
  Process decisions were here: https://make.wordpress.org/updates/2013/08/21/meeting-notes-from-81313/
  
  Basically, it came down to each team deciding the best way for them. For some with only a handful of active members, a chat is enough to nail it down with consensus. For others with a lot, nominations and a poll might be desired. Having the voting be open to people who are not contributors on the team kind of defeats the purpose of having the person rep the active members, so it made more sense to make the selection process be flexible and trust the teams to make their decisions together. Most teams posted their choice after a weekly team chat. That said, in all cases the rep chosen does get agreed on (via whatever method) by the active team.
  - Marko Heijnen 10:05 pm on September 5, 2013
    
    I’m an active member of Polyglots but I have no idea how the voting went. Otherwise I wouldn’t have left me comment here.
    I have no clue how all groups elected their rep but there should always be a post on 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/. showing where it will be decided. Also the place where it will be decided should be an open place where people can join like P2 or IRC. Not having this defeats the purpose of having a rep since he/she doesn’t have to have the support of the (active) members.
    - Jen Mylo 10:40 pm on September 5, 2013
      
      Ah, polyglots was a special case, my bad. Everyone else was in public irc and/or blog (mostly irc I think). Polyglots never posted a single update here over the past six months, and when I spoke to Remkus about it, I wanted to think about if polyglots is really active as a team or if there are parts there that are related to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., to outreach, to support, etc. that could be reported under those teams instead.
      
      I asked him to describe for me what the actual polyglots activity was, and what he described was basically he and Zé setting up translator access, handling questions, and discussing i18n issues, but agreed they weren’t being posted anywhere. So I apologize if there is an actual team structure for polyglots that is more than that. Can you point me to where that team activity happens? A regular irc chat or something, vs the one-offs that people tend to post to the blog about translations?
      
      Remkus argued in favor of polyglots remaining a team that reports independently, and committed to posting updates this term, so I said okay. That said, we’re going to start doing more international outreach via other groups that have been more engaged here, with the hope that it could all roll into polyglots when it has more active members and activity other than that described above.
      
      If you are interested in being the rep for that team, we can certainly revisit it — I can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Remkus and he can post on the polyglots blog. I was really under the impression after my chat with him that there wasn’t a cohesive team there yet, so I apologize.
      
      @defries: Can you work this out on the polyglots p2 with Marko and whoever else is active there? Thanks.
      - Marko Heijnen 10:46 pm on September 5, 2013
        
        Zé mentioned one time that GlotPress is a part of polyglots. So that part has activity on IRC, blog.glotpress.org and TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. Thats why I’m currently a bit mixed. Not sure what the ideal logic would be.
        
        Jen Mylo 10:53 pm on September 5, 2013
        
        Ah, got it, that makes more sense. As we last defined it, the GlotPress software is actually a sister software project, like bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. or BuddyPress (each of which has its own domains, blogs, communities, etc), not a contributor group of the main WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ project.
        
        What we *are* still missing is way to bring in the sister projects into a closer relationship, which we identified in October as something we wanted to do (one suggestion was having a rep from each project join the team reps group), but never really formed a policy or action around. I can bring that up again, it’s something we should have dealt with.
        
        Jen Mylo 11:01 pm on September 5, 2013
        
        Posted about it at https://make.wordpress.org/updates/2013/09/05/sister-projects/
      - Remkus de Vries 6:15 am on September 6, 2013
        
        There is no more team structure than Zé and I currently at Polyglots. The way I see it Marko has taken the role of lead for GlotPress, but like you’ve already concluded, GlotPress is a sister project and a part of Polyglots.
        
        Jen Mylo 12:05 pm on September 6, 2013
        
        You mean “and not a part of Polyglots,” yes?
Pingback: WordPress › Sister Projects « Make.WordPress.Org Updates
Andrew Nacin 3:54 pm on September 9, 2013

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s rep is Mike Schroder.

I like accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) as its own team. While most of their work ends up supporting the core team, I could see them working with WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ as well as sister projects in the future. (And they’ve already done some work to help both polyglots and GlotPress.)

While accessibility might be largely aspect-based (not unlike docs), this team is highly specialized, well organized, and driven. Unlike “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.” they are clearly a group of contributors with little overlap with other groups, and have concentrated expertise. They have been looking at things with great depth and breadth, have been doing fantastic work, and have been working hard to align themselves closely with individual projects/products/initiatives. Things may change over time, but for now, they are a perfect fit for being a proper team with a representative to ensure open lines of communication.
- Siobhan 6:58 pm on September 11, 2013
  
  Agree with nacin on this. From the perspective of docs, it’s been really useful to get in touch with the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team whenever we need anything in that direction. Also, they keep an eye on what we’re doing and always offer useful advice. They’re an active and cohesive team and I don’t think they’d function as well if they were spread across different groups.
  
  In relation to this, I’d love to see the design corps that was discussed – it would be really useful to have an active group of designers that could be contacted for different projects.

Share this: