We've talked about this quite a bit in the context of DevHub where User Contributed Notes are occasionally used as a feedback mechanism. Basically, we need a way for docs consumers to report problems or suggest edits of published documentation on .org.

The initial proposal would be to build or use something akin to ​Post Forking on the front-end of handbooks and eventually other places like DevHub or HelpHub.

Personally I don't think an MVP has to be a complete solution, it mostly needs to cover the rift drawn between moving away from the Codex where any user could edit anything to the now largely closed systems on .org.

I think starting with the handbooks would be the way to go.

Plugin and theme authors currently have the power to mark threads as resolved within their own support forum, which is great.

Problem description However, some of the larger plugin/theme shops have a support team to help out on their own support forums. I think it would be useful to be able to recognize those people in the support forums, like we’re able to recognize authors.

Proposal So what I would like to propose is adding a new role: Plugin/Theme Support. Everyone with this role should have rights to mark topics within their own support forum as resolved, and should not be affected by posting speed limitations for their own support forum. This role should also show in the forums as ‘Support’, similar to author.

The reason why I propose a new role, instead of adding the capability to the contributor role is because, in my opinion, they serve a different purpose. Let me explain.

A contributor is someone who helped your open source project forward. This can be by providing feedback, writing code, creating images, doing marketing or being a friend of the project, for example.

Someone working on support does contribute his/her (paid) time to your project and is in that way a contributor. However, I think there are more than enough valid use cases where you don’t want someone who contributed code (for example) once to be able to close support request on behalf of the author.

That’s why I think having a separate support role would be viable. It would show the community that this person is vetted and answering on behalf of the plugin/theme author.

Related ticket This proposal is related to ticket #2598.

Managing support role Of course, it should be possible for plugin authors to manage the list of support people. I see two reasonable ways to do so, which should be mutually exclusive.

One way is by adding the usernames to the readme.txt file, the same way contributors are currently added. The other way would be to add users the same way committers are currently added, on the Advanced View of the plugin.

Showing support staff To be transparent about this, we’d probably also need a place to list people in the support role. This could be the Advanced View page, or even the plugin page itself.

Replace the contents of ​https://ps.w.org/robots.txt with:

User-agent: * Disallow: /

When a forum thread is intentionally, permanently archived as a result of editorial/quality/spam decisions (e.g., see ​https://wordpress.org/support/topic/great-theme-alx/), the page should return a 410 HTTP status rather than a 404 status.

Sometimes people report 0-days in the forums. Perhaps we should add a notice not to report those and direct people to the right places.

Core: ​https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/ Plugins: ​https://developer.wordpress.org/plugins/wordpress-org/plugin-security/reporting-plugin-security-issues/

Props to @benlk for the idea!

@sevlad suggested adding counters to moderation links that require an action, see an example screenshot.

For a quick access from any page, it might also be a good idea to add these links under "My Account" in admin bar, as a follow-up to [6303].

Profile badges don't seem to automatically appear for all areas. My core and plugins badges appeared on my profile on their own (as far as I can tell), but my Speaker badge had to be added manually with some difficulty, and my Meta badge hasn't appeared at all after getting first props a few weeks ago (see [2016]).

The following code should be adapted and added to profile templates (values from ​https://profiles.wordpress.org/jonoaldersonwp/ used for reference).

<script type="application/ld+json">
{
    "@context":"https://schema.org",
    "@graph":[
        {
            "@type":"Organization",
            "@id":"https://wordpress.org/#organization",
            "url":"https://wordpress.org/",
            "name":"WordPress",
            "logo":{
                "@type":"ImageObject",
                "@id":"https://wordpress.org/#logo",
                "url":"https://s.w.org/style/images/about/WordPress-logotype-wmark.png"
            },
            "sameAs":[
                "https://www.facebook.com/WordPress/",
                "https://twitter.com/WordPress",
                "https://en.wikipedia.org/wiki/WordPress"
            ]
        },
        {
            "@type":"WebSite",
            "@id":"https://wordpress.org/#website",
            "url":"https://wordpress.org/",
            "name":"WordPress.org",
            "publisher":{
                "@id":"https://wordpress.org/#organization"
            }
        },
        {
            "@type":"ProfilePage",
            "@id":"https://profiles.wordpress.org/jonoaldersonwp/#webpage",
            "url":"https://profiles.wordpress.org/jonoaldersonwp/",
            "inLanguage":"en",
            "name":"{{Page title}}",
            "description":"{{Meta description}}",
            "isPartOf":{
                "@id":"https://wordpress.org/#website"
            }
        },
          {
            "@type":"Person",
            "@id":"https://profiles.wordpress.org/jonoaldersonwp/#profile",
            "name":"Jono Alderson",
            "image":"https://secure.gravatar.com/avatar/beed0f5ca54ae221655b9f30a1f6fe66?s=200&#038;d=mm&#038;r=g",
            "jobTitle":"Special Ops",
            "worksFor": {
             "@type":"Organization",
             "name":"Yoast"
            },
            "sameAs": [
                "https://www.facebook.com/jonathan.alderson",
                "https://www.linkedin.com/in/jonoalderson/",
                "https://twitter.com/jonoalderson"
            ],
            "mainEntityOfPage": { "@id" : "https://profiles.wordpress.org/jonoaldersonwp/#webpage" }
        }
    ]
}
</script>

NOTE: Optional nodes (like worksFor) should only be included when the relevant profile fields are populated.

NOTE: https://meta.trac.wordpress.org/ticket/4277 changes the title and description contents; values here should also change and use the new values specified in #4277.

NOTE: https://meta.trac.wordpress.org/ticket/4278 is required to retrieve/set social profiles in the sameAs array.

NOTE: If name is not set, fall back to username.

Hello,

While I was working on these tickets: #2100 and #2907

I've noticed that my error log was getting grumpy and I saw this error:

[22-Jul-2017 11:26:20 UTC] PHP Notice: Undefined index: consumer_key in tggr-source-twitter.php on line 152

For some reason when you view the results page on the front end the twitter module bugs out randomly ( not all times ) and after that php error all the settings are getting reset so you are losing all login information etc.

I haven't been able to find out why.

@dipeshkakadiya is on it for a solution so we can implement it on gwtd3 new website as well.

Pointers for devs: Grab the /trunk of Tagregator through svn, apply the extra patches to have the latest as they have not been implemented yet and then work on this ticket.

When toggling a status in the Flag section, the toggle afterwards is missing the capitalisation, this is because it just sets the label afterwards to the command, rather than the textual label for it.

The attached patch adds internationalised Enable/Disable text which it switches in/out instead of using the command. It's hard-coded inline with the JS, as that's the format of the current JS and changing it up further probably deserves a rethink of the entire flagging UI and storage.

For the new CampSite theme we had the idea to include a speakers bio page with an improved sessions list not only showing the session title, but also an excerpt as well as links to the slides and WordPress.tv video. We decided against a page template and rather add this additional markup to the post types plugin.

Individual news articles (like ​https://wordpress.org/news/2019/01/wordpress-5-0-3-maintenance-release/) correctly use canonical URL tags.

However, archives / the homepage / categories do not.

E.g., ​https://wordpress.org/news/, ​https://wordpress.org/news/page/2/, ​https://wordpress.org/news/category/testing/ should all have/use canonical URL tags.

If a ticket on bbPress or Meta Trac is closed with a particular resolution the resolution cannot be changed without reopening the ticket:

eg: bbPress Trac (Meta is identical):

BuddyPress and Core Tracs can change resolution withot reopening the ticket:

Taking a punt that the following code needs to be added to bbPress and Meta Trac "workflow-*.ini" files. I know bbPress and BuddyPress "workflow-*.ini" files are yet to be open sourced, presuming the same for meta:

Via: https://meta.trac.wordpress.org/browser/sites/trunk/trac.wordpress.org/conf/workflow-core.ini#L64

# Once the ticket is closed
# - reopen
# - change the resolution to something else
...
...

change_resolution = closed -> closed
change_resolution.name = change the resolution, set
change_resolution.operations = set_resolution
change_resolution.permissions = TICKET_EDIT_DESCRIPTION
change_resolution.default = -31

Aside: It wouldn't hurt to add the "mark as duplicate" section also ;)

E.g.,

​http://pingomatic.com/ should redirect to ​https://pingomatic.com/ ​http://pingomatic.com/stats/?cat=dog should redirect to ​https://pingomatic.com/stats/?cat=dog

E.g., ​https://wordpress.org/support/view/plugin-committer/corylamleorg should 301 to ​https://wordpress.org/support/view/plugin-committer/corylamleorg/

​https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2 should 301 to ​https://wordpress.org/support/view/plugin-committer/corylamleorg/page/2/.

​https://wordpress.org/support/view/no-replies should 301 to ​https://wordpress.org/support/view/no-replies/

There are a couple problems with our current data set. They're not strictly related to each other, but I'm creating a single ticket for this because I'm guessing that the solution to both will be the same: switch from our current data source to a better one.

• Problem #1: Incorrect IPv4 results. No data source will be perfect, but [several online database had correct results for instances where ours weren't ​https://make.wordpress.org/core/2017/04/14/nearby-wordpress-events/#comment-32448].
• Problem #2: No IPv6 support. Without this, the results will quickly lose effectiveness. As of May 2017, ​IPv6 adoption is at 18% globally and rising relatively fast. Some countries are as high as 32%.

It looks like our database was updated recently (March 2017), but I can't find any info on where the original data comes from. @dd32, @tellyworth, do either of you know? Do you have any thoughts on other potential sources?

While we were building the new bbPress theme we discovered that the WordPress theme live on ​https://wordpress.org/news/ would've been the best starting point. We now had to hack together stuff from various places.

Wouldn't it make sense to open-source that theme used at /news/ as well?

"Skip links" are one of the most simple and better known ways to improve accessibility for keyboard users and assistive technologies users. They allow to bypass blocks of content that are repeated on multiple pages, typically: navigation menus.

They're implemented since years in WordPress core and the bundled themes. They're also part of the WCAG recommendation:

Success Criterion 2.4.1 Bypass Blocks ​https://www.w3.org/TR/WCAG21/#bypass-blocks

In order to be effective, a skip link used to bypass the top navigation needs to:

• be the first focusable element in a page
• be revealed on focus
• point to the main content in the page

Far from pretending to be a complete analysis of all the .org network pages, I've gone through the main pages linked in the main navigation menus. To recap:

• Home: no skip link
• Showcase: no skip link
• Themes: no skip link
• Plugins: skip link is not the first focusable element
• Mobile: no skip link
• Support: skip link is not the first focusable element
• Get involved (Make): no skip link
• About: skip link is not the first focusable element and it doesn't appear on focus (conflicts with clip-path: inset(50%); inherited by social-icons.css)
• Blog: no skip link
• Hosting: no skip link

I realize the .org network is made of different templates coming from different sources and I guess it's a complicated setup. However, it would be great to make sure the skip to content link is actually present in all pages and works properly.

Hello,

There's no Twitter Card found for ​https://developer.wordpress.org/ on sub-pages.

INFO:  Page fetched successfully
INFO:  6 metatags were found
ERROR: No card found (Card error)

​https://cards-dev.twitter.com/validator

Copied over from ​#wp12696:

Replying to apeatling:

It would be awesome if you could pass an ordering parameter to plugins_api() that would allow you to return a list of filtered plugins in a specific order.

I'd love to be able to use the API to return a list of the most popular / newest / recently updated plugins on the repo that contain the tag "buddypress".

Something like this would be awesome:

$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'page' => 1, 'order' => 'popular' );

Even better, also allow search filtering:

$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'search' => 'album', 'page' => 1, 'order' => 'popular' );

I'd be happy to implement this if I can get access to the API source on WordPress.org.

Reply from Otto:

This wouldn't be terribly difficult to add to the API, but it's pointless until core supports doing it there and is able to request the ordering. So, moving to the plugins component.

Now that the arguments for plugins_api() have been documented, paired with the fact that there are existing filters in plugins_api() for modifying arguments, I think there's now a more compelling case for implementing an 'orderby' (or similar) argument in the dotorg API.

Adding the ​https://core.trac.wordpress.org/browser/trunk/.editorconfig file to the root of the meta repo should help avoid basic coding standards issues when contributing to the meta team.

Using the same .editorconfig from core should not cause any issues with the current meta projects.

​https://editorconfig.org/

To provide debugging information some users post their full logs in a reply. These can be up to 10k lines which makes reading the page really annoying because you have to scroll like 5 minutes.

Examples:

• ​https://wordpress.org/support/topic/qtranslate-x-compatibility-2/#post-8250157
• ​https://wordpress.org/support/topic/no-confirmation-email-received-2/#post-8235539

I suggest to prevent posting replies which have more than X chars/words/lines and to recommend using a service like Pastebin or GitHub gists.