View the meetup transcript in the Slack archives (A Slack account is required)
The no-replies default view for the forums has been cut down to 21 days, as mentioned in the agenda, this makes for a more maintainable list of relevant and timely questions, which can also easily be extended if there’s a need for it by manually supplying a URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org attribute (For example to view the past 30 days you would use the URL https://wordpress.org/support/view/no-replies?days=30)
This was a sought after enhancement to the forums that was brought up last week, so kudos to the meta 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. team for the swift modifications there!
Second item up was the labeling on the profiles compared to the labeling used when actually modifying the profiles (this is regarding a view only available to forum moderators and administrators on wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/), and how they are pretty inconsistent.
It turns out they are a bit more unclear than what we had first thought, and we have suggestions for relabeling on the forum side for two of the three states as it stands.
- Bozo relabeled as Modwatch
- Akismet Never Trust remains for now, at least until we’ve thought up a more sane label (it might remain as is, as it does what it says it does)
- Blocked (the user role) relabeled as Banned
See Meta ticket #916 – Profiles show incorrect flagged statuses for the discussion on this topic so far.
As a side note, the Bozo flag also prevents e-mail notifications from going out when a tagged user makes a reply to any thread.
The third item of the evening was profile badges for support members.
These badges are currently a manual process, where the badge is manually added to each profile, this can be a bit tedious, and it’s quite easy to miss somebody because they might not be as active on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. as many of us are etc, and we really don’t want that, we want the ones that give of their time to know that we really appreciate the effort they put forth.
@samuelsidler suggested utilizing the two badge formats (the badges come in two variants, one with a background color fill and one without) and using one for contributors and one for the “team” members, the ones that are moderators or similar. This appeared to be a much appreciated suggestions that we will follow up on.
A few ideas on how to automate the distribution of contributor support badges were also discussed, and we think the current limitation code on profile URLs can be leveraged for this purpose as well, and automatically adding a badge to an account if they have 100 or more topic replies within a 2 month period (that’s replies, not topics they’ve started them selves). Automation for IRC isn’t as easy as the forums, as there’s no link between a users IRC name and their wordpress.org profile name, the group will discuss this some more and hopefully involve some more of the IRC team in the discussions here to find a good way to do this.
The badge discussion was sparked by an interest to award some of the very active IRC contributors with badges and statistics for finding a way to identify contributors over IRC are currently being collected and can be manually generated. @Clorith will have the IRC list generated and the relevant profile names collected manually for this run while we get the ball rolling on the automation aspect of things.
