Community + Events update, August 30

Jen is working on recruiting new people for community team projects, starting with @courtneydawn on the Theme School project. Welcome Courtney!

We’re working on revising the Troubleshooting Workshop materials so they can be used by new trainers or for self-study (Amy is coordinating, reconvening the crew that originally planned the curriculum). v 2.0 will focus on adding more hands-on examples and a screencast-ready script.

Events this week:

  • 49 videos published to WordPress.tv
  • 287 WordCamps sold
  • WordCamps Wroclaw and Vegas announced their dates
  • WordCamps London & Tokyo opened ticketing
  • interviewed an organizer applicant for NJ, connected him with the local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organizer to collaborate
  • invoiced OnTheGo Systems for a new multi-event sponsorship for Toolset for 2013Q4 for North US, East US, and Europe/Africa regions.
  • The lively non-WordCamp discussion continues: https://make.wordpress.org/events/2013/08/20/organizing-a-non-wordcamp/

Events, Coming week:

  • Continue to support the 22 events in planning and the 15 events in pre-planning
  • Conclude our discussion of non-WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. events policy
  • Wrap up the Community/Events merger.

… Oh, and About That!

We know it’s been a while since we first decided on merging, and we’re finally kicking off the combined group this week.

Weekly IRC meetings will be on Thursdays at 1800UTC (2pm ET)

The newly combined 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/. will have categories for events and outreach, and we’re planning to include a bunch of new orientation material: who the team is, what our current projects are, and how to get information about (and better, get involved in) various projects. Stay tuned.

Docs Team Update for August 30, 2013

This Week

  • New Docs 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.: @sewmyheadon
  • @DrewAPicture will be working on new Codex doc for adding new media in WP 3.6: Inserting Media into Posts and Pages, which will build upon the existing Inserting Images into Posts and Pages article and will include audio and video as well.
  • Handbooks – We’re still working on both 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 and Theme dev Handbooks and could use all the help we can get. @hanni is organizing and will have more to report next week.
  • developer.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/ – @saracannon is working on design for Handbooks and dev.wp.org and will have more info next meeting.

#docs

Support Update, Aug 30, 2013

Transition to @jdembowski as support rep will begin next week.

  • Small clarifications were made about what being an IRC rockstar means (no keytars included)
  • @sivel updated some of our suggested IRC commands
  • Coming up with a wish list for people to give IRC OP powers

#support

Plugins Update, August 29, 2013

We have opted for me to stay on as lead 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’s rep for another term.

Plugins Directory stats for the last week:

Requested :192
Rejected : 62
Closed: 21
Approved: 151

Commits by plugin authors: 2944
Currently in the request queue: 74 (11 older than one week; 32 with no replies)

Plugins support email stats for the last week:

Currently open: 20 (4 with no activity in the last week)

#plugins

Theme Review Team Update: 08/26/13

Slightly slower, but we are still doing very well, here are the stats.

Currently

  • 23 new tickets are waiting for review.
    • 0 tickets are older than 2 weeks
    • 0 tickets are older than 1 week
    • 0 tickets are older than 3 days
  • 28 tickets are assigned.

In the past 7 days

  • 116 tickets were opened
  • 114 tickets were closed:
    • 87 tickets were made live.
      • 27 new Themes were made live.
      • 60 Theme updates were made live.
      • 28 more were approved but are waiting to be made live.
    • 26 tickets were not-approved.
    • 1 tickets were closed-newer-version-uploaded.

#themes, #trt

Mobile Group Update for Aug 26, 2013

Update

  • iOSiOS The operating system used on iPhones and iPads.: Submitted 3.7.1. A bug fix for a crash some users are experiencing when upgrading.
  • iOS: code clean up and partial refactoring is still underway and making progress
  • iOS: modernizing the app for iOS7 + MP6 in the works
  • iOS: laying the groundwork for a rich text editor.
  • iOS: kicking off work on a theme switching feature.
  • Android: continuing work on NUX (new welcome guide, better log in/sign up)
  • Android: better Media Library integration and Theme selection still in the works. Media needs another couple of weeks.
  • Android: Started work on a Native Stats features.
  • This is the last week of our Handbook push.

What’s Next

  • iOS: 3.7.1 release once approved
  • iOS: iOS 7 improvements ready by Sept 1
  • iOS: Merge refactor and iOS 7 branches next week
  • iOS: Continue to make progress on themes and rich text editor features.
  • Android: NUX welcome guide
  • Android: Continue to make progress on Media Library and Theme selection.
  • Android: Continue to make progress on Native Reader
  • Handbook: Wrap it up this week.

More info in the dev chat summary.

#mobile

Community Team update August 23

This week:

  • 17 videos published to wp.tv
  • 407 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. tickets purchased
  • Published WordCamp dates for Denver and Nepal
  • Approved for pre-planning: Norway and Louisville
  • Review Guidelines group published their final analysis: https://make.wordpress.org/events/2013/08/20/wordcamp-guidelines-august-19-update-since-you/
  • There’s a lively discussion about non-WordCamp events: https://make.wordpress.org/events/2013/08/20/organizing-a-non-wordcamp/
  • Invited David Bisset (@dimensionmedia) to join the WordCamp CentralWordCamp Central Website for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each. blog as a beat reporter.

Coming week:

  • Continue to advise the 20 events in planning and the 16 events in pre-planning
  • Continue to discuss non-WordCamp events
  • Merge Community and Events groups, as planned in the spring. We’ll be merging P2s in to make/community, with events and training/outreach stuff in separate categories.
  • Finally, we decided that I’ll be continuing as rep for the next term.

    #community

Support Team Update – Aug 23

Hi, we moved since chat is Thursday.

There’s a massive writeup of what we talked about this week here: https://make.wordpress.org/support/2013/08/meetup-roundup-2/

Summary: IRC needs some sort of official representation, we’re not going to make another support team. Instead, they’re going to have some ‘rockstars’ act like the support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. mods. They’ll come to our IRC chats and report in on what’s happening. Also they’ll have author access to make/support and can post there as needed to do the same. (PS: Yes, support mods, you should come too 😉 )

The next rep will be @jdembowski (time of switchover to be sorted out when all the teams sort that out).

To Do!

  • Add the IRC Rockstars (if/when they accept) to make/support as Editors
  • Flesh out a support handbook section for IRC (volunteers welcome)
  • Come up with suggestions for the doc-bot for @sivel (being handled at https://make.wordpress.org/support/irc-doc-bot/ )

#support

Meta Team Update: August 22

Thanks to a design from @melchoyce, code from @iandunn, and review and deployment from @otto42, we shipped a new global footer! There’s a few bugs to fix with it. If you notice anything (other than the display issues on the make P2s), file a meta trac ticket and let us know.

That’s not all, we also re-launched jobs.wordpress.net, with a brand new design courtesy @melchoyce, development and deployment from @coffee2code, and a brand new moderation duo, @mercime and @chriswiegman. Our new moderation duo will be pushing the site forward with proposed changes and design improvements where needed (like making the site responsive). If there are things you’re interested in helping with or issues you see, file a ticket or let them know.

Speaking of our new jobs.wordpress.net duo, we’ve officially added them to our 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. team and posted a page listing team members. There might be people left off (I’m still new!), just let me know and I’ll add them.

As a smaller team, we don’t have regular meetings, but a number of us met this week to do some ticket triage and agreed to keep our current two team reps for this next period. I’ll be 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. with @otto42 as my backup.

During our ticket triage, we went through about half of the open WordPress.org tickets on the core trac, closing a number of them and migrating others over to the meta tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. There’s a few tickets that need follow up from me, but we hope to get that number down to 0 in the not-too-distant future, with all our tickets on the meta trac.

For this coming week: work on developer.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/ is progressing, a spec for make.wordpress.org should be live, work on make.wordpress.org will be starting up, and we’ll probably do some more ticket triage.

Outstanding issues:

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 team: We need feedback on improving the plugin dev FAQ. Do you want to publish that more broadly?

#meta

Meeting Notes from 8/13/13

Sorry for taking so long with these. I got sick last week and lost a few days.

Attendees: Someone from every official product team except theme review and polyglots. Theme folks said the time would be an issue, but no word from polyglots. Will reach out to them to see what’s up, has been no activity here from them in general.

Agenda: Reps/Leads/[Advisors] Roles, Elections/Appointments, Summit Planning, Team Stats, New Contributor Materials, Make.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/ Landing Page

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. Role/Elections

Proposed changes to team reps role/process based on the experiences of the first term:

  • Term of 3 months for a rep rather than 6 months for 2 reps that swap halfway through.
  • Have outgoing rep recommend the next rep, like with release leadRelease Lead The community member ultimately responsible for the Release. on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Recommend to their team, get general acceptance from the team before recommending to team reps. Each team can handle the internal decision process however works best for them (poll, just propose a couple names, ask for volunteers, whatever), but the outgoing team rep will make the decision on the recommendation. Other outgoing team reps would only object to a recommendation if it was someone not active on the team or someone operating outside the general .org rules (someone selling proprietary themes wouldn’t be okay, for example). If a team can’t agree on who to make the rep, the larger team reps group will arbitrate.
  • As before, we are iterating on something that was brand new last time around. It’s all an experiment with good intentions. If something doesn’t work, we can fix it.
  • Next round of rep would be chosen in December. Each team take a week to decide who will go from now until then.

Discussion points:

  • Some felt 3 months too short. Others felt it was a more realistic time commitment.
  • Several team reps dropped out during the course of the six month term this time.
  • Possible lack of continuity with shorter terms something to keep an eye on.
  • What about term limits?
  • Tiny teams that don’t have enough people can’t really rotate very frequently/adhere to term limits.
  • Shorter term makes it possible to share the responsibility among more people, also helping to identify who steps up and is reliable and could be ready for more leadership in areas other than administration.
  • Some people still wanted 2 reps all the time. Main reason for proposing just having one active rep at a time and having a backup that isn’t actively participating in meetings has to do with process management. It was noted that backups should participate in everything so that if they need to step in for the main rep they’ll know what’s going on, but that touches on the problem that reps currently are not really doing the job as originally laid out. Reps should be filling in the whole team regularly on what’s going on with team reps/other teams, so almost any team member should be able to act as a backup if needed without special ramp-up information passing.
  • Some disagreement about what to do re Docs/Support rep(s). Again, slightly misses the idea of a team rep being a conduit/liaison rather than a subject matter expert or lead. Any team rep should be able to represent their team by talking to the people running various projects/components in their team. Some teams will have more disparate subgroups than others. For now, docs and support will have two active. Community team will try to be an example as it grows in the coming term of how the different-projects-in-one-one-team could work.

Lead Role

Sam, Jen, Drew and Pippin agreed on a proposal for creating an official lead role for teams analogous to the lead developer role and separate from team reps, but all agreed to table the discussion until new reps were rolled in. Of note, whatever happens with that, it would not be the job of reps to choose leads, but an internal team matter signed off on by Matt, same as with the core role.

Summit Planning

Going to post on wordpress.org and allow the community to suggest locations. Jen will also do continued research on possible locations. We’ll shoot to choose a place by Sept 15, acknowledging that date can’t be chosen without venue. Shooting for Februaryish or May, depending on location/weather.

Contributor Stats

No specifics here, just a heads up that it’s on Sam’s radar and we’ll need the help of all teams to start gathering useful participation stats so we can watch trends around contributor engagement.

make.wordpress.org home page

Getting worked on, with an upcoming surge (hopefully to launch) during/immediately following WC Birmingham when Jen, Sam, Otto, and others will be together.

Project Queue

Sam published https://make.wordpress.org/meta/project-queue/ to keep track of priorities on .org site projects.

#meeting-notes