Call for Support Team Representative(s)

It’s time to select team representatives for 2023 across the WordPress project, including the Support team!

What is a 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.?

Within the WordPress project, each contributor team has a minimum of two team representatives. Often abbreviated to “team reps,” these people represent the team across the project, share key updates across all contributor teams, and generally help to support the team as a whole. You can read more about the team rep definition and expectations on the Team Reps page and in last year’s announcement.

Currently, the Support team has one representative: @sterndata. Previous reps include @andrea_r, @clorith, @macmanx, and @ipstenu.

Expectations for team reps can vary from team to team. In general, Support team reps help to:

  • prepare for and run Support weekly team chats
  • providing as-required updates to other contributor groups
  • generally representing Support across the project, or in the occasional chat
  • maintain a high-level perspective and awareness on current Support projects

Team reps should expect to dedicate 1 to 2 hours per week to these activities. Any active Support contributor can be a team rep, and we can have more than two team reps. Likewise, an existing team rep can continue in the position, as well, though having new people in these roles is encouraged!

Opening nominations

Any active Support person can be a team rep, and anyone can nominate a team rep. Self-nominations are also accepted. Everyone is welcome to give some thought as to who is a good fit for this role and nominate them in the comments of this post.

Nominations for Support team reps will be open until December 1, 2022. Those selected as team reps will take over these responsibilities starting in January 2023 and would be in this position for the full year, until December 2023.

After the nominations close, if there are enough nominees that we need to make a selection, I will publish a poll the in the Support meeting on December 1, so everyone can cast their votes. We’ll keep the polls open for 24 hours. Keep in mind that whoever is selected as a team rep will need to accept the role. So if someone nominates you, and you aren’t available or interested, don’t worry!

If you have any questions about the team rep role, want to learn more, or any other doubts, please share them here in the comments!

Trac Tickets for 3.8 (AKA: Support Works Backwards)

I made a ticket for a weird caching issue: https://core.trac.wordpress.org/ticket/26676

I think the ONLY other one that’s jumping out now is the plugins page is blank. If you’ve managed to solve that one (all I can see is ‘host fixed it!’), reply here. This is probably related to @andrea_r‘s comment: https://make.wordpress.org/support/2013/12/wherefore-the-wtfbbq-post/#comment-157012

WordPress 3.6 Beta has landed for @andrea r’s…

WordPress 3.6-BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. has landed for @andrea_r‘s birthday.

WordPress 3.6 Beta 1

PLEASE test 🙂 I will send you cookies.

Again with a meetup

The awesome Jerry is taking on Gravatars because it fits with the user section he has just completed.

HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. is still up for grabs.

Some proofreading going on and we’re wondering if we can un-techie “install on your own server” for newbies. Maybe soften it to “your web host”.

Jerry has moved “your Profile” from chapter 7 and put it under “Managing Users on your WordPress Site” in Ch06.

Also we noted about being careful with internal linking in the manual, depending on final home.

Fastest 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. ever! There were only 3 of us.

Today’s Meetup

In keeping with my whirlwhind crazy, I may miss today’s 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. (there was a baby born!). In case I miss it, here’s a quick update of who needs to do what 🙂

@jerrysarcastic – You’ve got ‘Adding Users’ which needs to get done.
@ericlewis – It looks like you finished comments (yay!) so remember to check it off on https://make.wordpress.org/support/user-manual/ 😉
@andrea_r and @ipstenuMultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network., you lazy moving pair!

Unassigned:

  • GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com/.
  • HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information.

I cannot express how awesome you all are for getting us this far so fast!

Post hoc ergo propter hoc approaching and defining…

Post hoc ergo propter hoc: approaching and defining support goals

Breaking out from the Codex thread below – and using, inter alia, Siobhan’s comment as a starting point, let’s get some outlining goals going on:

  • A clear division between developer docs and user docs
  • A self-contained, concise yet complete landing page for the user coming in
  • Plot a useful journey for different people who want to “learn WordPress”, from beginner to ninja/rockstar/whatever the individual wishes to be – (imho this needs to both respect that not everyone will want to do everything, nor indeed have the nouse (everyone is unique, and has their own strength), whilst respecting and encouraging the learning process – it’s a balance to ensure that eveyone gets to where _they_ want to be, with the best tools and information not where we, or anyone thinks they should be. Without passion, we’d not be here – I think at this point I’m merely restating what everyone thinks and goes without saying, but, let’s just get it documented.)

So, there’s some overlap and a meeting point with the core contributors‘ handbook, and this is where we need to be super disciplined. I know so many of us, @ipstenu, @andrea_r, @lorelle, @esmi (and everyone here, and more!) have been mulling this over for a good deal of time, so I’m just very much about grouping the discussion and the years of thought and care into a thread.

Let’s go!

#goals

Codex work

We should probably get a conversation going not only about needed Codex work but *how* to approach a better structure and how to get the work done.

I’m leaning towards a re-org and maybe a bit of a division between users docs and programmer notes. A good example of this the Pages page. It starts out as a user doc then jumps right into code.

Things like Handbooks need to be sorted out and linked to as well.

I think if we could sort out the right approach first and focus on specific pages or topics later, then we’d start making big progress. Possible if we even approached it like a WP dev cycle, with clear targets and a deadline.

Possibly a mentorship program as well, wehre we could round up people to help and start handing out assignments and being there to keep people on task and for any questions they have.

All thoughts welcome here. 🙂

#codex, #docs

Hello world!

Welcome to make.wordpress.org/support. This is the new blog for the Support contributor team, made up of 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. moderaters and documentation contributors, as decided on the mailing lists. Anyone helping in the #wordpress IRC channel is included as well. @Ipstenu is the 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. for this group, with @esmi and @andrea_r as the backup reps per the votes we took a while back from members of the two mailing lists. I’ve added them and a couple of other people as editors on this site, and they will be adding the more active contributors in turn.

I think it would be good for us to set up a weekly IRC chat time to get things started, gain some momentum, and round up some new contributors in the process. We can identify some common goals among the more active contributors to focus on at first, and put together a schedule for how to move forward.

I have several goals for this group based on the surveys and feedback from the community that I’d like to see accomplished over the coming months:

  • Create a guide to contributing to WordPress support.
  • Start a mentorship program for potential support volunteers to help them ramp up with confidence.
  • Handbooks! Field Guides! Whatever we call it, discrete, targeted pieces of documentation tied to specific releases and each curated by a single editor for the sake of consistency and accountability (separate from the ongoing wiki that is the Codex), that can be viewed, downloaded, or printed. This will take a lot of discussion, so we should schedule a chat about this sooner rather than later to get started on the one for end users. Other contributor groups will also be tackling handbooks specific to their areas (core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org., etc.).
  • Start tracking stats around support activities and sharing them with the broader community.
  • Make a plan for improvements to the support forums.
  • Make a plan for how to best bubble up support issues to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team.

What are your goals for this group? Introduce yourself so everyone knows who everyone else is, say a little bit about your background and your general activity level as a WP support volunteer, and let us know your goals for the group are and what you think we should focus on first. Also mention your location/time zone, for the sake of being able to set up an IRC chat. Thanks!