Proposal for updated support guidelines

The support guidelines serve as the guidestones for support moderators (and 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 reviewers) in setting expectations around what is and what isn’t acceptable behavior.

The guidelines were last fully reviewed during 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. San Francisco in 2013, and a lot has happened in those 10 years. Some guidelines were added ad-hoc to account for timely situations, while others have just become dated, and may not necessarily reflect the current state of the WordPress user base, it’s surrounding ecosystem, or the outward facing opinion we wish to nurture.

The following is a collaborative effort in refining, simplifying, and clarifying the guidelines as they are today, into something that is both easier to understand for users, but also makes the job of those moderating much easier in the long term.

The proposal is available in a separate document, to make it easier to reading in an isolated (and easily comparable to the current iteration) manner.

Note that some changes would initially impact existing forum content. As these are new guidelines; once implemented, they will only relate to new content moving forward. The reasoning being that existing content were a product of the guidelines of their time, and moderating this existing content every time a guideline changes is just not something that can be done..

Read the new guideline proposal
(the doc is ready only, please leave your comments in this post)

As these are a result of work during WordCamp Us 2023, if you are at the venue and wish to discuss something, please feel free to reach out and a summary of it will be posted as a comment here. Otherwise, please use the comment section below for feedback, or questions, if there are uncertainties as to why some guidelines may have been removed, amended, or added to, this helps ensure everyone that wants to can have their opinion voiced, and that the same response does not have to be repeated in private channels.

The feedback period ended on 2023-10-01 00:00 UTC

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!

Talking Point: Allowing Self-Archival of Topics

This is not for tomorrow’s agenda, but is still something that should be talked about with more than just the people who happened to be online at the time.

tl;dr Proposal

I propose we allow users to archive their own topics (not replies). In addition, we should lengthen the time-to-edit to allow people to remove semi-sensitive data.

Longer Explanation/Reasoning

One of the ongoing concerns in the forums is a double-edged sword. We want the forums to be more welcoming to more people, and the needs of the people have changed considerably in the decade+ since we codified the forum guidelines. At the same time, making it easier for people to get where they need to be and do what they want to do causes an extra burden on the volunteers.

Part of simplifying the experience for users and lessening the load for volunteers comes with an added twist of privacy and legality.

It came up today (2 Sept 2020) that someone had posted information that isn’t exactly ‘private’ but could land them in legal trouble for sharing. They did so by posting a debug log that had information that probably should not be public.

Over the course of the discussion, many pain points were identified (including talking to 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 about making it clearer to the users that some data should not be shared on public forums). The one we can action on from the forums side would be to alter our policy of “No, we don’t delete posts except in extreme circumstances” to “allow users to delete their own posts whenever they want.”

Why This Needs to Happen

Back in 2010, the user base for WordPress was different. It was not unacceptable to think that most people coming to the forums were aware of the basics of servers and FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients., as few one-click-to-install services existed. Having MultisiteMultisite 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. require people demonstrate some server awareness (by editing a wp-config.php file) was seen as reasonable and logical. We actively wanted that barrier to entry, as the support and maintenance of Multisite would need you to know how to log in to the server and possibly use command line.

Today, a number of companies offer WordPress managed hosting, where they do everything for you. While we have amazing tools like WP-CliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/, the average user has shifted, and not everyone needs to care about Ubuntu flavours or packaging their own PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. versions.

  • WP 3.0 (released in 2010) had 37,579,278 downloads
  • WP 5.4 (released in 2020) had 60,771,290 downloads
  • WP 5.5 (released a month ago) is around 16,700,000 already

To be clear, I think this is a good thing for the ongoing growth of WordPress. But it also means we need to reevaluate how we handle things in the forums. The decisions made a decade ago were never meant to be immutable and permanent. They are, in fact, guidelines for a reason. Our user base is going to keep growing and changing, and we must adapt.

Recognizing that our user base is different means we need to change our expectations. It is no longer fair to assume that everyone knows a user ID isn’t a security risk, or that posting in public means Google will find it eventually. Instead of trying to educate an ever growing user base, we can simply permit people to remove posts.

In addition, with the landscape of privacy awareness, it’s unfair to expect all forum moderators for all nations to be up to speed on the legality of sharing private information. There’s no possible way any volunteer can always know what is safe for public consumption from their e-commerce store, and what is privileged information, after all, and we should not be asking them to do so!

Proof of Concept

I can speak to this directly. In previous years, when the Plugins team emailed all developers to ask them to update their plugins for compatibility, we would receive hundreds of requests to close plugins. In April 2020, we added a change that permitted developers to close (but not reopen) their own plugins on their own.

This last release cycle, we received under 20 requests, while over 100 plugins were still closed.

By allowing people to take agency over their own experience, the developer satisfaction rose. I firmly believe this will have the same effect on forum posters.

Ideas/Solutions

These are ordered in what I believe are ‘easiest to hardest’ to do:

  • Extend the time-to-edit (currently 1 hour, proposals were for 3 days to 7 days)
  • Make the link to edit more obvious
  • Rewrite the WALL O TEXT before the post box to something smaller/actionable
  • Link to the guidelines (maybe a checkbox) at the post box
  • Allow OP (and only op) to self-archive (the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org would become a 410 GONE with a simple message of “This post has been removed by it’s author”)
  • Allow people to report individual replies, not just posts
  • Have a popup if ‘Debug Log’ is pasted in
  • Have Carike’s Flow be a thing (It’s already in progress)

Pros and Cons

Pros:

  • Giving users agency makes happy users
  • Smaller burden on forum mods
  • Legally protected from privileged data
  • Reduction of harassment towards mods when telling people no
  • SEO bonus as less valuable posts will be removed, making the Google Beast happier

Cons:

  • Solutions may be lost for other people with the same problem (this is often referred to as the DenverCoder9 problem)
  • Some people may act maliciously and hide/edit the post to try and cover their tracks
  • Longer post editing will cause out-of-sync issues, where answers no longer make contextual sense

Conclusion

Allowing users to remove their own posts, and giving them a longer time to edit, will give them power over their own representation online, and allow them the freedom to make mistakes without dog-shaming them about them in perpetuity.

#proposal #guidelines

March 7th Support Team Meeting Summary

General announcements

The first iteration of user documentation for the new block editor is now live, either via https://wordpress.org/support/article/wordpress-editor/ but also from the Support page under the title “Writing Posts” for general discovery.

As some may have noticed recently, we’ve lost a lot of wonderful German contributors. In light of this we’ll be reaching out to the existing moderators there to see if anyone would want to be the liaisons between our global team and their local one, as well as how things are going, and what we can do to help.

If you are a part of the German community and would like to help out there, or have questions, feel free to reach out. This also goes if you’re from another community and would like to get more involved, we’d love to welcome you into our midst!

Another subject in this weeks meeting is burnout, and because @macmanx puts it better than I, here is a quote:

When we say “please take the time you need” (or similar) whenever you mention burn-out or other difficulties contributing to the forums, we mean it sincerely in a “I care about you” fashion, not a “go away” fashion.


When you tell us you need to step away, please don’t expect us to ever push back.


Every contribution you make is valued and appreciated, but we want you to put your needs first. We can guarantee that we’ll do our best to stay on top of things while you’re out, and that the forums will still be here if you want to come back. What we can’t guarantee is your health and happiness, and that’s why we’d rather you always put that first.


If you need to step away, please do so. We want you to take care of yourself, and we’ll look forward to when you’re feeling ready to return.


On a somber note, long time contributor and community member Alex Mills passed away recently. As one of his requests, we would love to help keep his plugins going, someone is taking ownership of maintaining them already, but if you wish to help out in supporting one or more of them, it would be very much appreciated.

WordPress 5.1

We’re seeing an increase in 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 compatibility issues leading to broken media libraries. We’ve been unable to pinpoint the source, as it’s happening with many plugins, so this may be bad caches, hopefully we’ll learn more and have something a bit more solid, but worth noting.

Checking in with international liaisons

Members of the Italian, Swedish, Greek, Spanish, Russian, Dutch and Indian communities were present for this weeks discussions.

The Russian team has some intercommunication troubles they are working out, and we’ve offered to assist in any way we can if they wish it.

Open floor

Reviews with links in them are often frowned upon, as they are at times used for spam, but some users do it without being aware that it’s bad at all.

Based on this, if a review contains a link, we’ll now do the following:

  1. Remove the link from the review (but leave the review if it’s legitimate)
  2. Leave a user note of the action
  3. Post a response letting the reviewer know that links shouldn’t be used in reviews.

This way we educate users, without causing distress or anger. This of course does not apply to obvious spam entries, which get treated like any other spam.

In other news, the WordPress 5.0 retrospective kickoff was posted over at https://make.wordpress.org/updates/2019/03/01/5-0-release-retrospective-kickoff/

Attendance

@abdullahramzan, @amboutwe, @bcworkz, @benlumia007, @bethannon1, @binarywc, @bph, @clorith, @cristianozanca, @diddledan, @fahimmurshed, @fernandot, @fierevere, @howdy_mcgee, @ipstenu, @jdembowski, @JNashHawkins, @kartiks16, @macmanx, @numeeja, @RDD, @sterndata, @t-p, @tobifjellner, @webdevmattcrom and @xkon attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it’s the only thing that ever has.

Margaret Mead

#weekly-chat

November 15th Support Team Meeting Summary

General announcements

WordPress 5.0-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. 4 is currently out, if you can, please help test it to make sure we knock out any bugs whenever possible.

@macmanx put forth a call for reviews, so to speak, to encourage us (and others) to leave a Health Check review if they used it to resolve a problem. Negative reviews can be of-putting (although we’re happy to see that the reviews are read, which is pretty awesome), and negative ones weigh heavier than positive ones when users read them.

Checking in with international liaisons

We had members from the Russian, Italian, Greek, German, Urdu and Spanish communities present during this weeks discussions and updates.

Attendance

@abdullahramzan, @bcworkz, @bemdesign, @bethannon1, @binarywc, @clorith, @cristianozanca, @felipeelia, @fernandot, @fierevere, @firoz2456, @geoffreyshilling, @howdy_mcgee, @ipstenu, @jcastaneda, @jdembowski, @jeherve, @macmanx, @numeeja, @otto42, @sterndata, @t-p, @tobifjellner, @tokyobiyori, @xkon, @zodiac1978 and @zoonini attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

Just remember, when you’re over the hill, you begin to pick up speed.

Charles Schultz

October 25th Support Team Meeting Summary

General announcements

WordPress 5.0-beta1 has been released, please make sure you read the 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. post properly, as there are some considerations you may need to take for this beta period.

Checking in with international liaisons

Members of the Swedish, Russian, Italian, Dutch, Spanish, German, Serbian and Greek support communities took part in this weeks support chat.

Links in reviews

Our big ticket item, links in reviews.

We’ve long had a guideline mention that we do not allow links in reviews, but they’ve not always been upheld the same way. Basically, a link in a review to a persons own website is often used as an attempt to get a free link and some free visitors, which is why we’ve drawn a hard line to avoid spam.

There can be nuances here though, so evaluating things on a case by case basis will help in the long run. A link may not always be bad, it may have value in relation to the experience at hand.

Also, when redacting a post or flagging a user, always leave a post explaining what is happening so the user isn’t confused as to why their post has changed.

If in doubt, feel free to ask the rest of the team on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., we’re here for each other!

Open floor

Don’t forget about our work on improving the support guidelines, we’re collaborating on GitHub (https://github.com/Clorith/wporg-support-guidelines) for it, but discussions can also happen on Slack. If they do happen on Slack, please someone summarize them on to GitHub as well for visibility.

Attendance

@anevins, @bemdesign, @bethannon1, @clorith, @contentiskey, @cristianozanca, @fernandot, @fierevere, @firoz2456, @geoffreyshilling, @ipstenu, @jcastaneda, @jdembowski, @keesiemeijer, @macmanx, @nikolam, @numeeja, @otto42, @peterbooker, @RDD, @sterndata, @t-p, @tobifjellner, @wfsupport, @xkon, @zodiac1978 and @zoonini attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

When you take care of yourself, you’re a better person for others. When you feel good about yourself, you treat others better.

Solange Knowles

September 20th Support Team Meeting Summary

Troubleshooting blank editors

Please give the post on troubleshooting blank editor screens from @designsimply a read, and provide any troubleshooting steps you think may be missed in the comment section. Please note, this is about the editor it self being blank (JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. issues), and not WSOD errors in general, which is a different ticket item.

Checking in with international liaisons

Representatives from the Italian, Russian, Dutch, Swedish, Serbian and German communities took part in this weeks meeting, including a checkin before the 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/. at 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. Würzburg!

Attendance

@bemdesign, @binarywc, @builtbynorthby, @clorith, @cristianozanca, @designsimply, @fierevere, @geoffreyshilling, @ipstenu, @jdembowski, @jeroenrotty, @macmanx, @nikolam, @numeeja, @raduconstantin, @RDD, @sterndata, @t-p, @tobifjellner, @wfsupport, @wido, @zodiac1978 and Sam O’Daniel attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

It is amazing what you can accomplish if you do not care who gets the credit.

Harry S. Truman

September 13th Support Team Meeting Summary

General announcements

WordPress 4.9.9 has been given a tentative release date of November 5th. This is subject to change, but is the current working date.

Checking in with international liaisons

Members of the Russian, Hindi, Dutch, Brazilian, Urdu, Swedish, German and Spanish communities were part of this weeks meeting, letting us know things are going well in their respective communities as well.

Open floor

The 404 page on the forums isn’t very helpful, as many things may have happened to a topic before you end up on this page. Adding a bit more information will help users going forward. We’ll be ticketing this and following up on the 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/..

At 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. US this year, we’ll be doing another of our onboarding sessions. If there are items you feel should be included please reach out to @zoonini or @bethannon1 and they’ll help facilitate this!

Attendance

@abdullahramzan, @anevins, @bcworkz, @bemdesign, @benlumia007, @bethannon1, @binarywc, @builtbynorthby, @clorith, @contentiskey, @felipeelia, @fernandot, @fierevere, @firoz2456, @hardeepasrani, @ipstenu, @jcastaneda, @jdembowski, @joyously, @numeeja, @raduconstantin, @RDD, @sergeybiryukov, @sterndata, @t-p, @tobifjellner, @tokyobiyori, @zodiac1978 and @zoonini attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

Change will not come if we wait for some other person of if we wait for some other time. We are the ones we’ve been waiting for. We are the change that we seek.

President Obama

September 6th Support Team Meeting Summary

General announcements

Some page builder themes appear affected by a removed function in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ (it had been deprecated for a while). Some of them may therefore need updates to be fully compatible with Gutenberg again.

Checking in with international liaisons

Representatives from our Italian, Swedish, Greek, Dutch, Spanish, Russian, Belgian, Brazilian, German and Urdu communities were present during this weeks meetings.

Open floor

When handling reviews, and they need to be archived, remember to inform users of why. This is very apparent with Gutenberg related posts, as many users are first time posters who may not be familiar with forum etiquette. Let them know what is going on and why.

We’ll also be making a more official post about review handling on the make/support page. A few support team members have recently blogged about this privately, but we’ll want something more official we can link back to.


In other news, we’ll be revising the Forum Guidelines, trimming them down and making them more discoverable.

We’ll work on discoverability after revising the content though, to help users more easily digest the content and understand what lies behind it. We’ll be collaborating on this in the coming weeks, so look for a make/support post on that as well.

Attendance

@abdullahramzan, @anevins, @bcworkz, @bemdesign, @benlumia007, @bethannon1, @binarywc, @clorith, @contentiskey, @cristianozanca, @felipeelia, @fierevere, @firoz2456, @geoffreyshilling, @howdy_mcgee, @ipstenu, @jcastaneda, @jdembowski, @jeroenrotty, @joyously, @mindmantra, @numeeja, @RDD, @sterndata, @t-p, @tokyobiyori, @zodiac1978, @zoonini and pri attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

We make a living by what we get, but we make a life by what we give.

Winston Churchill

June 28th Support Team Meeting Summary

General announcements

In light of the past days events, just a re-iteration that security things pop up now and then, please practice responsible disclosure by reporting incidents to hackerone.com/wordpress, such topics are always touchy and emotions are easily mixed in so just refer to that site and avoid any public discussions about unpatched issues

Google Chrome’s July update will be rolling out soon, and it will mark any website not served over 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. as “Not secure” in the address bar. We may see some questions pop up from users who are unfamiliar with https and wants to know why their site is suddenly no longer secure. We can educating them on the benefits of a secure website, and that the message is not necessarily dangerous, but more of a push towards a safer browsing experience. We’ll link to whatever resource Google provides when this change comes, but until they have one our user manual page on https is a good start.

WordPress 4.9.6 (and beyond!)

There’s no new incidents for 4.9.6, and leads for 4.9.7 have been picked. This means we’ll likely get a release date for the next WordPress release some time in the next week.

Checking in with international liaisons

Representatives from the Russian, Italian, Serbian, Greek, Urdu, Brazilian, Spanish, German and Swedish communities joined in, it was a grand gathering this week, and some new information was shared with the new Urdu forums!

Open floor

With HelpHub (our new user documentation project) not far away, some pre-defined replies are likely to change, as we refer users to articles there instead of the Codex (don’t worry, we will be redirecting codex pages, so existing links will keep working).

Attendance

@abdullahramzan, @abletec, @amboutwe, @bemdesign, @bethannon1, @clorith, @contentiskey, @cristianozanca, @felipeelia, @fernandot, @fierevere, @firoz2456, @geoffreyshilling, @ipstenu, @jcastaneda, @jdembowski, @joyously, @macmanx, @mariovalney, @nikolam, @numeeja, @peterbooker, @pixolin, @RDD, @sterndata, @t-p, @tobifjellner, @wido, @xkon, @zodiac1978 and @zoonini attended.

Read the meeting transcript in the Slack archives. (A Slack account is required)

Contributor tips
WordPress is a community of well-meaning individuals. Always remember that behind every action, there’s a real person.