Support Team Update for May 29th

Item discussed in today’s #wordpress-sfd support 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.: @jerrysarcastic‘s idea. Jerry’s been very popular these last few meetups. 😉

It was a fun conversation and mostly it revolved around what his idea is and where to put it for now.

The What Part

The current support handbook’s audience really is people who want guidance for being a forum moderator. As @Ipstenu said the support handbook is “How to make more Jans and Mikas.”

Jerry’s idea is for producing a handbook that can be used for people who want to help others outside of a moderator role. Some of those forum members may be web developers not familiar with WordPress coding standardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards.. Or non-coders who want to help and look for guidance as to how to best do that.

The Where Part

The where part was quickly settled at least temporarily. The stub is located at https://make.wordpress.org/support/trouble/ and the first step will be to create a TOC. Once that’s filled out then posts and examples can begin to be populated.

You do want to contribute, right?

Have you ever read a forum reply and thought “That was really a good answer!” (that’s happened to me) or even “That reply is missing a step”? This handbook can be a place to document and share those answers and solutions.

Visit Mika’s Break/Fix WordPress site and poke around. There are some great posts there and that’s really along the lines of what this idea is about.

Read again Jerry’s post and reply back there. What do you think should go into the table of contents, how should it be organized? Got any ideas for a topic or post? I myself want to write something about how plugins can be modified without editing just by using actions and filters in another small 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.

There can be a lot of ideas for that handbook; please chime in make suggestions. Any offers to contribute will be appreciated.

The transcript of today’s meetup can be found at this link.

#support

Plugin team update for May 29, 2014

Repository stats for the week:

Plugins requested : 194
Plugins rejected : 53
Plugins closed : 7
Plugins approved : 133

77 plugins currently in the queue, 32 awaiting their initial reply and 3 older than a week.

3717 commits to the repo (919691-923404)

Support stats for the week:

29 open tickets, 8 with no activity in the last 7 days.

#plugins

Theme Review Update for May 26, 2014

Currently

  • 73 new tickets are waiting for review.
    • 3 tickets are older than 2 weeks
    • 25 tickets are older than 1 week
    • 45 tickets are older than 3 days
  • 59 tickets are assigned.
    • 38 tickets are older than 2 weeks
    • 54 tickets are older than 1 week
    • 59 tickets are older than 3 days

In the past 7 days

  • 132 tickets were opened
  • 151 tickets were closed:
    • 127 tickets were made live.
      • 10 new Themes were made live.
      • 117 Theme updates were made live.
      • 24 more were approved but are waiting to be made live.
    • 22 tickets were not-approved.
    • 2 tickets were closed-newer-version-uploaded.

#themes, #trt

Docs Team Update: May 22, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. Deprecated files issue: @siobhan asked us to discuss Item 1 under Current Priorities in the DevHub chat summary – does it make sense to use @deprecated tags in the file headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. of deprecated files? The consensus reached by the team was @deprecated tags should not be used in a file header to designate a file as deprecated, or that it contains deprecated items.

2. DevHub: The weekly chat summary included a list of the team’s current priorities, which includes several open 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets. There was also an explanation of the team’s current organization structure and goals. They currently need feedback on code reference explanations, as well as the proposed search results badges.

3. Handbooks: @samuelsidler posted a summary of the weekly Handbooks chat containing the current status of both Developer Handbooks. Good progress was made on both, and there are several new contributors. If you’re interested in helping, you can contact @blobaugh and @sewmyheadon at the email addresses listed in the post. A reminder that the next Docs Sprint is Saturday, June 7, 2014 at 10am PDT – they’ll be meeting in-person in Seattle, and virtually in #wordpress-sfd.

4. Admin Help: @Clorith said the team is defining components (work flows) for user testing. They’ll be looking into doing more in-person testing at local WordPress meetups and WordCamps, which will eliminate potential time constraints from user testing services. I suggested they also reach out to 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. organizers for help in identifying areas that new users are struggling with. (weekly chat summary)

You can read the chat logs here.

#docs

Plugin Team update for May 22, 2014

Repository stats for the last week:

Plugins requested : 211
Plugins rejected : 38
Plugins closed : 11
Plugins approved : 276

64 plugins are in the review queue, with 16 older than a week and 29 awaiting their initial review.

5421 commits to the repo this week (914268-919689).

Support stats for the week:

16 open tickets, 8 with no activity in the last seven days.

#plugins

Support Team Update for May 22nd

Item discussed in today’s #wordpress-sfd support 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..

Handbook updates for people starting with support

@jerrysarcastic elaborated on his idea from last week. Elaborated as in really provided a detailed description of what he meant and the goal is. 😉 This topic would be great for a make/support post and Jerry has said that he’ll create one there.

The discussion focused on the goal for updating the handbook for users to begin providing support and those users are not moderators or experienced users/developers. This is to include working examples along the lines of http://breakfix.elftest.net/

I think it’s a great idea and begins to head into knowledge base territory. That’s a big task but a section like that would really help people get started and be a great resource for any 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. Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

I’m really looking forward to Jerry’s post as well as feedback from the support community.

The transcript of today’s meetup can be found at this link

#support

Theme Review Update for May 19, 2014

Currently

  • 60 new tickets are waiting for review.
    • 0 tickets are older than 2 weeks
    • 8 tickets are older than 1 week
    • 44 tickets are older than 3 days
  • 63 tickets are assigned.
    • 31 tickets are older than 2 weeks
    • 53 tickets are older than 1 week
    • 59 tickets are older than 3 days

In the past 7 days

  • 148 tickets were opened
  • 145 tickets were closed:
    • 119 tickets were made live.
      • 16 new Themes were made live.
      • 103 Theme updates were made live.
      • 19 more were approved but are waiting to be made live.
    • 26 tickets were not-approved.
    • 0 tickets were closed-newer-version-uploaded.

#themes, #trt

Docs Team Update: May 15, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. DevHub: Work continues on moving the parser out of alpha. @siobhan posted a list of the project’s current priorities/issues, along with a list of other issues that need to be resolved. There are also several 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets open. If you are interested in helping out, you can attend the weekly chat on Tuesdays at 19:00 UTC.

2. Admin Help: @trishasalas stepped down as project lead, and @Clorith will be the lead moving forward. The weekly chat discussion included user testing and other options for identifying problem areas for users.

3. Handbooks: @blobaugh posted a summary of the Handbooks chat, along with the current status of the 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 Developer Handbook. @sewmyheadon will be wrapping up work on the new Theme Developer Handbook intro this coming week. Contributors are still needed for both handbooks, so if you’re interested, please attend the weekly chat on Wednesdays at 21:00 UTC.

4. Reserved Terms: We discussed how to resolve #27962. There needs to be a generic, top-level reserved terms list somewhere in the Codex/handbooks. Right now, the only place that list appears is in the register_taxonomy() Codex page, and is hard for developers to find. We discussed where such information would be on DevHub – a general, best practices area for developers, or in one (or both) of developer handbooks. Several options were suggested. For now, we decided to do a Codex page so the Trac ticket can be closed. @trishasalas volunteered to take responsibility for completing that task.

You can read the chat logs here.

#docs

Support Team Update for May 15th

Items discussed in today’s #wordpress-sfd support 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..

Issues related to WordPress being upgraded to 4.0-alpha

When the 3.9.1 maintenance release came out some users experienced their installation upgrading to 4.0-alpha. This was related to broken language packs. Those language packs were pulled back and replaced resolving the issue.

This has occurred before and there may be a post on this topic on make/polyglots on that topic. If that happens then that link will be posted on make/support.

Closing topics on the forums

Sometimes forums members will post a support request on an old topic that may be resolved or about an old version. It’s fine to close those but please leave a note as to why the topic was closed.

Updating the support handbook

@jerrysarcastic brought up a question about @ipstenu‘s site http://breakfix.elftest.net/ and if it could be included in the handbook. That site was created when the make blogs were just beginning and Mika had intended to do something with that site along those lines.

The purpose of that site was for providing training in DC on how to support WordPress. It’s a neat site and has many good working examples. Mika said that that was the goal and she’d previously had a conversation with Jen about that already.

@samuelsidler pointed out that the handbook does have a section getting started on contributor day and that perhaps that can be incorporated in there. The idea is to create a middle step to get encourage people to provide support.

@jerrysarcastic said he’d look at what needs to be done to incorporate that site into the handbook.

The transcript of today’s meetup can be read on-line at this link.

#support

Theme Review Update for May 12, 2014

Currently

  • 44 new tickets are waiting for review.
    • 0 tickets are older than 2 weeks
    • 4 tickets are older than 1 week
    • 24 tickets are older than 3 days
  • 54 tickets are assigned.
    • 28 tickets are older than 2 weeks
    • 44 tickets are older than 1 week
    • 52 tickets are older than 3 days

In the past 7 days

  • 136 tickets were opened
  • 129 tickets were closed:
    • 105 tickets were made live.
      • 4 new Themes were made live.
      • 101 Theme updates were made live.
      • 29 more were approved but are waiting to be made live.
    • 24 tickets were not-approved.
    • 0 tickets were closed-newer-version-uploaded.

54 tickets assigned to 28 reviewers and 5 of  which haven’t had a response in nearly 3 weeks.

#themes, #trt