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.

Several ​HTML5 sectioning elements automatically create ​ARIA landmark regions.

Landmark regions are exposed to assistive technologies and allow users to quickly find information in a page. Ideally, all content in a web page should be wrapped within landmark regions. For now, I'd like to propose to focus on the navigation menu.

In this specific case it's important to know that <nav> elements are mapped to an ARIA role=navigation. Therefore, <nav> elements are perceived by screen readers and users can jump to them using dedicated keyboard shortcuts.

In the wp.org network, some sections don't use <nav> elements at all. For example, the home page (screenshot from Safari and VoiceOver):

Other sections do use navigation landmarks but not for the main menu. For example, the Themes section has two of them:

Same in the Plugin section sub-pages:

For clarity, these are respectively:

• a <nav> element with a role="navigation": it was common practice to repeat the role even if redundant, to support old browsers assistive technologies
• a <div> element with a role="navigation", which is equivalent to a <nav>

Besides technical details, the most important navigation (the main one) doesn't use a navigation landmark. Wrapping the main menu in a <nav> element would be a good, simple, improvement.

Note: when in a page there are multiple landmarks of the same type, it's important to use an aria-label to help users to distinguish them. This is also what WordPress core and the bundled themes do.

Suggested:

• wrap the existing main menu markup in a <nav aria-label="Main menu">
• where present, add to the secondary navigation an aria-label="Secondary menu" (or any better wording)
• the toolbar already uses an aria-label="Toolbar", no need for any change

Optionally:

• modernize the markup: remove role="navigation" and just use a <nav> element

Note about the wording: When screen readers encounter a <nav> element or a role="navigation", they already announce "navigation": it's recommended to not use this word in the aria-label because it would be announced twice.

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

User-agent: * Disallow: /

Plugin pages, like ​https://wordpress.org/plugins/autoptimize/, often contain FAQ content.

When this is the case, we should output FAQ schema markup, with an aim to encourage Google to show FAQ questions+answers in the search results (therefore achieving extra visibility and clickthrough-rates).

Approach

• Add an additional node to the existing schema markup on plugin pages, for "@type": "FAQPage".

• Add a mainEntity property to house the questions.
  • Loop through each question/answer, and construct a Question node with an acceptedAnswer property.

Example output

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "@id": "{{CANONICAL_URL}}",
  "url": "{{CANONICAL_URL}}",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does the plugin do to help speed up my site?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them, and moves styles to the page head, and scripts (optionally) to the footer. It also minifies the HTML code itself, making your page really lightweight."
    }
  }, {
    "@type": "Question",
    "name": "But I’m on HTTP/2, so I don’t need Autoptimize?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests. That being said, <a href="http://engineering.khanacademy.org/posts/js-packaging-http2.htm">concatenation of CSS/ JS can still make a lot of sense</a>, as described in <a href="https://css-tricks.com/http2-real-world-performance-test-analysis/">this css-tricks.com article</a> and this <a href="http://calendar.perfplanet.com/2015/packaging-for-performance/">blogpost from one of the Ebay engineers</a>. The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it’s just HTTP/2, maybe it’s HTTP/2 + aggregation and minification, maybe it’s HTTP/2 + minification (which AO can do as well, simply untick the “aggregate JS-files” and/ or “aggregate CSS-files” options). And Autoptimize can do a lot more then “just” optimizing your JS &amp; CSS off course "
    }
  }, {
    "@type": "Question",
    "name": "Will this work with my blog?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Although Autoptimize comes without any warranties, it will in general work flawlessly if you configure it correctly. See “Troubleshooting” below for info on how to configure in case of problems."
    }
  },
  {...}
  ]
}

Sanitization concerns

All HTML tags should be stripped from fields, with the exception of the text property of an acceptedAnswer, which should:

• Accept <a>, <strong> and <em> tags.
• Disallow/remove any values/properties/attributes of these tags (other than the href attribute on <a> tags).
• Remove invalid markup (e.g., an <a> without a closing </a>).

Per discussion in the latest ​Meta team meeting, we would like to create a Components page for Meta Trac, similar to the ​Core Components page. This should hopefully encourage more component maintainers to step up, and provide more transparency for contributors on who to contact in order to move tickets forward.

Currently, the max uploads is 5 for all users. The photos team would like to increase the limit to 30 max uploads for all users with 30 or greater approved photos. The photo mod team is onboard with this change.

For legal reasons it is necessary that WordPress.org enforces acceptance of a ToS and Privacy Policy at login, and record the date and version of the policy most recently accepted by each user. This means:

• The login form will need to include a checkbox such as [ ] I have read and accept the terms of service and privacy policy with appropriate links.
• Failure to check the box will prevent login.
• Login sessions should remain capped at 2 weeks to ensure all active users regularly accept new terms.
• On successful login, a usermeta or similar value should be set recording the timestamp and version of the ToS and Privacy policy documents (perhaps the currently deployed svn rev# for each?)
• It should probably also record the rev # of the login form and theme, since that may be relevant info.

Particularly for Trac newbies, "invalid" can feel like a bit of a put-down, even with an explanation of why the ticket is being closed.

Maybe not-a-bug, not-a-core-bug, or something of that nature would be better?

Bikeshedding welcome on this ticket.

My plugin has a short description longer than 150 characters in the readme.txt (due to the ampersand being turned into it's HTML entity taking it over the limit).

However, the API request for 'plugin_information' returns different results for the short_description at different times of the day.

curl --location -g --request GET 'https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]=wp-user-manager&request[fields]=short_description'

It can return:

The most customizable profiles & community builder WordPress plugin with front-end login, registration, profile customization and content restrict … Which is 150 chars if you don't count ' …'

But then a later call to the API returns:

The most customizable profiles & community builder WordPress plugin with front-end login, registration, profile customization…

It feels like some double trimming is happening somewhere along the line.

With the new-ish signup tool that allows us to un-spam registrations, it also lets us block users from that interface. However, while it does log who did the action, it doesn't do so in a trackable way. That is, we only get logged "Changed to blocked by X" but none of the reason.

Generally the reason is "Bio and/or registration URLs were spammy" but none of that is recorded.

What we need is a change to the notice.

1. Where was the account spammed/blocked from? This can be "Banned by X via ..."

2. A COPY of the bio and URLs (recommend truncation since some bios are 5000 word porn stories, not kidding). That way it's obvious to everyone else "Oh, yeah, the person with the bio about their casino is probably spam"

Example of a spammy signup:

url: ​http://10040656... from: metro hispania occ: Security guard interests: sex

or:

url: ​https://www.facebook.com/Huge-Market-1234566 from: Main Street

Those should be copied into the user notes.

Thanks to @dd32 for pointing me to #3935 form the ticket #6625.

Actually, that solution seems to work only with screenshots, not with icons and banners.

This is the plugin I'm working on: ​https://wordpress.org/plugins/wc-exporter-for-reviso/

Here is the assets folder: ​http://plugins.svn.wordpress.org/wc-exporter-for-reviso/assets/

And this is the result: ​https://it.wordpress.org/plugins/wc-exporter-for-reviso/

The screenshot-1-it_IT.png is used correctly but all the other localized images are ignored.

I know that adding text in images is never a good idea, but the reason for having a different image here is basically the logo in the top right corner: Reviso is a software that changes the name in Italy in Contabilità in Cloud.

Thanks.

The community translator is a tool that enables front-end translations of strings for projects that use GlotPress to store their translations. It consists of a few parts:

1. A front end script that highlights translatable strings, provides the UI to translate them, and submits the translations
2. A backend plugin that prepares translation data for the script (based on gettext filters, for example)
3. A GlotPress plugin to extend the api (gihub link coming soon)

Enabling it on WordPress.org would allow front end translations of rosetta, the plugin directory, the theme directory, etc. Demo: ​https://cloudup.com/iU6acgS9-x1

Patches:

• translate-api-plugin.diff​ contains the GlotPress plugin
• translator.diff​ contains the translation backend plugin, and the front end script which is a minified build from ​https://github.com/Automattic/community-translator/
• jumpstart-plugins.diff​ is the code to load the translator in the plugin directory
• jumpstart-rosetta-themes​ is the code to load the translator in rosetta sites and the plugin directory

TODOs:

• Do we want this to load for all users? Only previously active translators? something else?
• Fix URLs in the translator plugin for wporg cdn
• Design adjustments

props akirk hew julesaus

We need an admin-only tool that will allow us to mass-email plugins.

One exists but currently can only be run by a server admin, which limits usability.

1) Provide a list of plugins

2) Provide an email subject and body with basic substitutions

3) The tool would then email everyone with commit access and listed owner the message

Substitutions needed:

%USER_EMAIL% %USER_DISPLAY_NAME% %PLUGIN_URL%

With Helpscout you can pre-fill everything BUT the body: ​https://docs.helpscout.com/article/119-pre-fill

So it doesn't look like we can use that for our bulk-mail tool.

If it's secure and has the capability to be given a usable UX, whatever tool is used on the back-end should be fine.

Limiting the number of plugins mailed at a time is also fine. Handling more than 50 of those at a stretch is usually pretty annoying anyway :)

​https://s.w.org/robots.txt currently redirects to wordpress.org.

For SEO and performance reasons, we should implement a robots.txt file at this location.

The contents should be:

User-agent: *
Disallow:

It would be helpful if the forums logged who marked a post resolved (or unresovled) as well as closed etc.

From a moderator perspective, this would help track down plugin developers (for example) who automate resolving tickets. It would also mean we'd know who to ping if someone closed a post without a comment.

Example:

• Marked Resolved by Mika 11 Jan 2017, 22:00
• Marked unresolved by Otto 11 Jan 2017, 22:30

or

• Closed by Jan 13 Feb 2017, 11:30
• Opened by Marius 14 Feb 2017, 00:13

Various Rosetta sites have a blog with a "Hello World" post. These should be deleted. Because of the incorrect hreflang setup on these sites, these posts cause an absolute SEO nightmare as Google seeks out their (non-existent) siblings across the whole network.

E.g., ​https://tg.wordpress.org/2012/08/23/hello-world/ ​https://tt.wordpress.org/2014/07/08/hello-world/ ​https://fao.wordpress.org/2016/07/20/hello-world/ ​https://dzo.wordpress.org/2015/02/24/hello-world/ ​https://kab.wordpress.org/2015/02/24/hello-world/ ​https://sa.wordpress.org/2011/07/26/hello-world/ ​https://hau.wordpress.org/2016/07/15/hello-world/ ​https://bre.wordpress.org/2015/07/17/hello-world/ ​https://ak.wordpress.org/2016/03/05/hello-world/ ​https://es-pr.wordpress.org/2016/03/05/hello-world/ ​https://rup.wordpress.org/2016/03/05/hello-world/

I don't have an easy way of finding them all from the outside-in - I'm hoping that these should be easy to round up?

It's also worth considering that in many cases, these are the only blog posts on these blogs. E.g., ​https://dzo.wordpress.org/news/, ​https://bre.wordpress.org/news/

When that's the case and we're removing them, can we also please:

• Remove the entire blog
• Remove menu links to the (removed) blog
• 301 redirect requests to the blog root URL (e.g., ​https://bre.wordpress.org/news/) to the local site root (e.g., ​https://bre.wordpress.org/)

After hovering the mouse over the collapsible element, the mouse icon turns into a cursor. Since the element is clickable and has some information inside, it would be great if the mouse icon turns into a pointer when a reader hovers the mouse over a collapsible element.

Screenshot :

Nowadays, Openverse has a solid brand documented mostly in the Design Library (​https://www.figma.com/file/GIIQ4sDbaToCfFQyKMvzr8/Openverse-Design-Library?node-id=0%3A1) and it would be great to update the icon and main color defined for the profile badge (​https://make.wordpress.org/meta/handbook/tutorials-guides/profile-badges/) since those are outdated.

Here is attached the SVG file of the symbol, and the new hex color is #C52B9B

The per_page argument for the Plugins API query_plugins action seems to return the wrong number of results in some cases.

So, if you limit the per_page to 20, you only get 19 items back event though that there are more than 20 results available.

We are hitting this issue with the WP-CLI plugin search command, which shows the exact count of elements returned. See ​https://github.com/wp-cli/extension-command/issues/156 for the related issue.

On some locales (like Catalan), most of the translations are done by 3-4 people (with 2 of them being GTE), even if according to ​https://translate.wordpress.org/locale/ca there are 10 GTE, and almost a 100 contributors.

This is a problem not only because it simply doesn't scale (with the amount of strings that themes & plugins have, 3-4 people are not enough), but also because is extremely hard for GTEs to identify "active" contributors to help and guide them so they become one day GTE, and for contributors to find active GTE so their strings get approved and don't stay forever as pending.

Ideally, there should be a way of "filtering" the teams page (​https://make.wordpress.org/polyglots/teams/?locale=ca) with some kind of "active" filter, with active being a rule such as "has translated/reviewed more than X strings (could be 0) in the last 3-4 months".

That could help to really asses the health of a team, as you could quickly identify how many people is actively contributing to the project.

Also, if that filter included some kind of aggregated cross-project stats (similar to the ones you get "per-project" in translate.wp.org), pointing to the projects they contributed, it would be easier to "measure" the amount of contributions people is doing: I, as a GTE, am more in validating strings translated by someone who contributes regularly than strings from someone who only translated 1 string two months ago. Computing such a huge amount of stats won't be light in terms of resources, but in order to be useful, these stats don't need to be "live": a weekly update would be more than enough to get a sense of the current state.

This would also give extra visibility to the health of the team, on top of the "activeness" filter: knowing there are 100 people active when 99 of them only have translated one string isn't a sign of healthy at all.

Hello,

Not sure if the meetings calendar could support it but I find most of the time the first couple early meetings in the day hide the others out there. It would be nice if the current time would change the view so the next few meetings are displayed with all others hidden in the popup link. This might help expose meetings that are about to occur instead of just displaying stale (past) meetings. *This would only apply to the current day.

Thoughts? Thanks

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.