Samuel Sidler 4:43 pm on July 29, 2015
Tags: , , , ,   

Weekly i18n Chat Notes – July 28, 2015

A few more things were discussed at this week’s 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. i18n chat:

  • Translate Themes: Just a couple of things:
    • All active themes were imported! But syncing hasn’t been enabled yet so a few newer themes (since the start of the import) are not yet imported. They will be soon, don’t worry. 🙂
    • Language packs were enabled for themes! If a theme does not ship with translations and is fully translated into a language (in translate.wordpress.orgWordPress.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/), a language pack will be generated and automatically downloaded. Woohoo! Language pack generation is automatic. When a theme is fully translated (100%) in a language, a language pack will be generated. Some history from @ocean90:
      • 2010 – First language packs for importers
      • 2011 – CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ticket #18200 filed
      • 2013 – Ticket #18200 closed as fixed (WordPress 3.7)
      • 2014 – Language packs enabled for core (WordPress 4.0)
      • 2015 – Language packs for third-party plugins and themes (WordPress 4.3+)
  • Translate Project Prioritization: I’m working up a detailed list of what we should do and when, based on the post from last week (and comments). Design-wise, we’re going to stick with what exists in the theme directory and modify as necessary.
  • Translate Import Queuing: There’s a lot of projects that will be added and syncing. We’re going to work up a queueing system in case things get overwhelmed. This is needed before we start importing plugins.
  • Rosetta HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.: We need to “fix” the Rosetta header with the static, known sections, allowing Editors to add on at the end of it. Since we don’t have a showcase except on the homepage, my proposal is to set the following menu items: Home, Themes, Plugins, Forums (if they exist), Blog. Editors will be able to add additional menu items.
    • (Note here that we should really add the Download button to the Rosetta headers as well.)

Over the next week, we’re going to continue to improve themes on translate.wordpress.org, including language pack work and synchronization. If there’s time, we’ll also start adding filters / prioritization to projects.

#i18n, #l10n, #meeting-notes, #rosetta, #translations

Samuel Sidler 5:10 pm on July 21, 2015
Tags: , , , , , ,   

Weekly i18n Chat Notes – July 21, 2015

At our weekly chat today, we talked about a few things:

  • Forums: The Italian forums were launched! It’s a bit rough around the edges, so there’s a bunch of work still left to do. If anyone is interested in contributing to our bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org theme just let us know. The more help we can get, the faster we can get the forum theme in shape to launch it to other locales. (Big props to @ocean90 and @medariox!)
  • Translate: Tons of things going on and upcoming here.
    • Themes are being imported. Currently ~1100 out of a total of ~1900 themes. The rest should be imported by next week’s meeting.
    • As part of the import, we’re noticing that quite a few themes have a textdomain that is different than the theme’s slug. Language packs will not support that. Instead, we’ll contact theme authors and work with the theme review team to ensure this won’t happen again. (Also, @Otto42 is adding modifying theme-check so that it checks for this issue.) Some stats on that were shared in 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/, but note that they’re for all themes, not just active themes. The actual numbers will be different.
    • Meanwhile, we need to start considering how to sort and prioritize themes and plugins. This post has some ideas and the comments section is open for more. We should have a list to start on by next week’s meeting. There are some backend changes that @dd32 needs to work up first.
    • One method of prioritizing is favorites. @dd32 is working up changes to the theme directory (and elsewhere) so themes can be favorited. ❤️ We can use theme 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. favorites to prioritize projects (per-user) on translate.wordpress.orgWordPress.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/.
    • @ocean90 is also testing plugin imports with a few select plugins to ensure the import script works well.
    • Additionally, the language pack script currently exists for plugins and will be modified for themes (thanks @ocean90!).

Most of our focus right now is on language packs and theme/plugin translations. Summarized, here’s the next steps:

  • Finish theme import
  • Enable theme directory syncing (every new/updated theme gets imported)
  • Implement some prioritization (including a side project: adding favorites to themes)
  • Modify the theme directory to support translated theme names/descriptions
  • Enable language packs for themes
  • Start importing top n plugins
  • Enable language packs for top n plugins

Of course, some of these will happen in parallel with others and there are numerous parts to each line item, but we’re making great progress. By next week, we’ll probably be able to cross off an item or two. 👏

#forums, #i18n, #l10n, #meeting-notes, #plugins, #rosetta, #themes

Samuel Sidler 5:33 pm on July 20, 2015
Tags: ,   

Translation Project Sorting Ideas

We’ve been collecting some ideas for sorting all of the projects that are being imported (themes and plugins). I want to collect some of the ideas here, along with my thoughts on them. If you have other ideas, we’d love to hear them!

  • Prioritizing by popularity: Projects could be organized by how popular they are, that is, how many users and/or downloads they have. For translators, the projects that are used the most by users are often considered the most important.
  • Prioritizing by fewest strings remaining: If a project is almost complete – e.g., just a few strings away – it can be considered higher priority. By enabling this option, we’d give translators a way to complete more projects faster. Personally, I think this is better than doing by percentage because 1 string remaining in a project of 10 is fewer than 10 strings remaining in a project of 1000, despite the latter being a lower percentage.
  • Prioritize by permissions: If a translator is the translation editor for a specific project – or a few specific projects – we could show those projects first, since they have permission to approve translations for that project.
  • “Hide” fully translated projects: If a project is fully translated and strings are fully approved, we could “hide” those projects or at least put them at the very bottom of the list. For themes and plugins, this will put them on the last page of results. Searching will still find them, of course.
  • Starring or Favoriting: Everyone has one or two themes/plugins that they really love and want to see available in their language. Giving translators the ability to “favorite” a project and have it raise to the top would make it easier to keep track of new strings in their favorite projects. We could even create a new “tab” for “Favorites” that could be the default if a translator has favorites.
  • Sort by waiting: Translation editors should be able to see which projects have waiting strings so they can approve them. Within this view, we should probably prioritize projects based on some of the ideas above.
  • Improved search: Translators should be able to search by author name (theme or 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.) and see a list of their projects, for example.
  • Consider “alerting” when changing a translation: It’s hard to explain this, but if I, as a translation editor, change the translation of “gallery” in one project, GlotPress should alert me to the fact that other projects have a translation of “gallery” that is the “old one” and possibly even offer to update all projects with the new translation.

The ideas above are just that: ideas. We may not implement any of them or all of them. But it’s important to list them and think through how we can improve the translation experience.

What other ideas do people have on sorting, prioritizing, and generally improving the translation experience of translate.wordpress.orgWordPress.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/?

#i18n, #translations

Samuel Sidler 10:50 pm on July 14, 2015
Tags: , , , , , ,   

Weekly i18n Chat Notes – July 14, 2015

We had our weekly chat today and talked about a few things.

  • Forums: We’re still waiting for one issue to get fixed in bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org before we can enable initial forums for the Italian community.
  • Translate: Lots of great progress.
    • Design implementation is done.
    • Paging is done. Basic search is part of it as well.
    • Import scripts are done for themes and in-progress for plugins.
    • @dd32 tested an import of all themes and it works! 🎉
    • Role 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. design changes are still pending, but the design is ready, so it’s just a matter of implementation.

Because of the progress on themes, we think we can do the initial import for themes very soon. It’s know that there will be issues, especially in categorizing and sorting through all ~1500 active themes that will be imported. We’ll work through those issues, fix them, and be ever-more ready for plugins.

Also, because we’re so close, I posted on make/polyglots and make/themes to give them the heads up and added some documentation to the translator handbook to walk through how some of this will work on their end.

As we get closer to the initial import of plugins, there will be a post on make/plugins and we will email plugin authors ahead of time, with a specific date, so they have an opportunity to commit any missing translations to SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/..

(See also: the meeting notes from last week.)

#forums, #i18n, #l10n, #meeting-notes, #plugins, #rosetta, #themes

Samuel Sidler 11:02 pm on July 10, 2015
Tags: , , , , ,   

Plugins, Themes, and Translate.WordPress.org

As mentioned a few times, we’re going to be enabling the translation of active plugins and themes in the WordPress.orgWordPress.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/ repositories on translate.wordpress.org. Today, we had a chat in #meta-i18n (logs) about how the non-technical side of this will work.

As a quick recap: We’re making good progress on the relevant pieces of Rosetta, GlotPress, and all the related scripts needed to import plugins and themes that are in the WordPress.org directories into translate.wordpress.org and make them available for translation. Every 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. and theme will then be able to take advantage of languages packs, meaning no more delay in language updates and smaller plugin downloads.

Here are a few of the points we discussed on how this process will work:

  • Eventually, all active themes and plugins in the WordPress.org directories will be imported into translate.wordpress.org and made available for translation. The “eventually” is important to note as we will be importing a few at a time to ensure GlotPress can scale accordingly. It’s also important to note that “active” is a theme or plugin that has been updated in the last year. Further, even plugins and themes that are not i18n-ready will be imported so that their descriptions can be translated.
  • Additionally, any plugins or themes that do not live in the WordPress.org directories will not be allowed on translate.wordpress.org. For example, commercial plugins.
  • During the initial import, we intend to import all strings – included translations – directly from the plugin’s svn repository on WordPress.org. We will not continuously import these strings, however. Ideally, after the initial import, a plugin would then delete the strings from the svn repository, making their download smaller and immediately taking advantage of the language packs generated by translate.wordpress.org.
  • For a language pack to be updated, the string must be updated in translate.wordpress.org.
  • The above point means that if a theme or plugin author uses a different site for translations, those translations must be brought over to translate.wordpress.org. If the theme or plugin has an active translation community, they can work with the polyglots team to bring translation editors over to the community. These translation editors can be limited to specific plugins, at the discretion of the locales translation editors. These translation editors can import strings for the plugin/theme, should they wish to continue using a different site for translations. (When we get closer to this, I’ll create a sample post that theme and plugin authors can use.)

That’s a lot to take in, so please let it digest. 🙂

One thing we also discussed was the possibility of enabling GlotPress installations to “talk to” each other, such that translate.wordpress.org could import strings from another GlotPress site (for example, translate.yoast.com), whether as a feature of GlotPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or a plugin. Currently, this is an open question. We plan to discuss the technical questions of this possibility at next week’s #meta-i18n chat (Tuesday, July 14 2015 11:00 UTC). Note that we will not wait for this feature before continuing with our planned import.

A few other notes:

  • We discussed the possibility of adding a banner to the specific plugin/theme’s page on translate.wordpress.org pointing the external site where translations are active, should a plugin/theme not use translate.wordpress.org as the canonical source for their translations. Currently, I believe the answer is “no banner” but it’s a conversation we should have and re-evaluate over time.
  • Outside of that, it occurred to me after our chat that we will need to add translation editors to the relevant theme/plugin page. For example, if a translator editor only has permissions to approve translations for Hello Dolly, we should note that on the Hello Dolly page within translate.wordpress.org. Example: “Strings for [project name] are approved by the German translation editors [link], as well as username, username, and username.”

If you’re interested in any of this topic, we’d like to get some feedback on any/all of the above. Please leave your comments here, not in #meta-i18n, so others can see your feedback. We’re especially interested in feedback from plugin and theme authors who do not currently have translations and one’s who use an existing product for their translations.

#i18n, #meeting, #plugins, #themes, #translations

Samuel Sidler 1:36 pm on July 7, 2015
Tags: , , , , , ,   

Weekly i18n Chat Notes – July 7, 2015

After a four week hiatus (!) we had our weekly i18n chat today. We’ll be continuing these chats every week on Tuesday 11:00 UTC 2015, just like before.

This week, we discussed the following:

  • Forums: While the bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org 2 forums aren’t quite ready yet (literally no plugin has been ported to bbPress 2 yet), we’re going to move ahead anyway. @ocean90 is going to work on setting up forums for the Italians within the next week, but is running into permissions issues with bbPress.
  • Translate: @ocean90 implemented most of the @isaackeyet‘s design for translate.wordpress.orgWordPress.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/. With the new designs, there’s only a handful of technical things left before we can start adding additional plugins or themes:
    1. Finish design implementation: The big piece that’s left is adding the sub-project drop down in the top right box, which is needed to allow switching between sub-projects. Additionally, a green outline needs to be around the box if a project is at 100%, but this isn’t blocking anything.
    2. Paging. Without paging, the list of plugins will grow unwieldy. @dd32 is going to work on paging (which needs to be done here).
    3. Roles 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. Changes: The roles plugin won’t scale if we add hundreds (thousands!) of new projects. We need a UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. here – designers wanted! See #1101.
    4. Search: Not needed for an initial import of the top n plugins, but required for when we add all plugins. We’re putting this on hold for now as paging will suit our needs for the foreseeable future.

Beyond the technical list above, we need to talk about how plugins will be imported. Let’s chat this Friday July 10 13:00 UTC 2015 about importing plugins into translate.wordpress.org. If you’re interested in this topic, join us in #meta-i18n.

(As a reminder, all WordPress community meetings are listed on the meeting calendar.)

#forums, #i18n, #l10n, #meeting-notes, #plugins, #rosetta

Sara Rosso 3:55 pm on July 6, 2015
Tags: contributor day, ,   

WCEU 2015 Contributor Day Marketing group notes This…

WCEU 2015 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://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ – Marketing group notes

This is the 2nd time we’ve had a Marketing contributor day group at WCEU, and the 3rd I’ve led (also at WCLDN) We had 15 people join the Marketing day group, which was double that of last year’s group, and I heard from several people that they weren’t sure they would be able to contribute on Contributors Day until they joined, so that was great.

We worked on 3 main things:

  • Furthering the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. WordPress presentation started at WCEU 2014
  • Generating a list of ideas for other marketing contributor day groups to tackle
  • Re-imagining the Features page on WordPress.orgWordPress.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/

Open Source WordPress Presentation

  • If you haven’t heard about it, it’s a reveal.js presentation (i.e., manageable on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/, platform-independent, easily modifiable by anyone who knows HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.) incorporating a lot of the reasons and selling points I’ve shared in some of popular enterprise presentations at WordCamps. The idea of this presentation is to help agencies and freelancers ‘sell’ WordPress and they can customize it to their market / country with a great set of starting examples and case studies, and focus more on building sites vs. selling WordPress.

We came up with an outline at WCEU 2014 and the outline is almost complete for me to get a first draft online in a Github repo. With the work we started in 2014, I took some personal/work time to further it between meetings, and will continue to do so. We made some progress on the open source and multilingual sections.

Marketing Sub-group ideas for Contributions
We took 10-15 minutes to brainstorm some ways that we could contribute back to the Community and here are a few things we came up with:

  • 1-page datasheet/flyer about WordPress features
  • Information banners with infographics
  • Comparison charts of different CMS
  • 1-page summary of the WordPress ecosystem (or a map/graphic)
  • Infographic about security? non-technical
  • Benefits of open source
  • Redesign features page
  • Modular Landing page for presenting WordPress
  • Redesign tag landing page tempate for .org Showcase with tag description/intro
  • Country-specific landing pages (aka tag landing page) for .org Showcase

Re-imagining the Features page on WordPress.org

This was a fun exercise to try and we broke the group up into two teams so they could work together, faster. We were lucky to have some UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. designers in the group, and each team took a different approach. Here are their suggestions below, one focused more on content and addressing the three audiences we believe are addressed/interested in this information (user/content creator, administrator, and developer), and the other focused more on the display of information.

I did preface the exercise by saying I wasn’t guaranteeing we could change the page, but I think it’s a good exercise for the community and it would be nice if we could update it – some of the content is rather old, like highlighting “ability to have comments.” 🙂

I’m not able to post pictures, so you can check out the gallery I uploaded here on GDrive of the team and their landing page suggestions:
https://drive.google.com/folderview?id=0B9wRJsOfSKgzflJJVkNiaFFreXpqOEJKcGFnUDlqUTNHcDVSeTkyMWV5blpFdDJzbDFfSGc&usp=sharing

#contributor-day, #marketing, #wceu

Ian Dunn 7:44 pm on June 16, 2015
Tags: git, sandbox,   

Editing WordCamp.org CSS Locally with Git

Over on make/Community, we’ve been discussing ways to eliminate some of the worst pain points that 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. organizers have with building their sites.

There’s one discussion in particular that I’d love to get feedback from 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. team members on, which is determining the best way that we can support a traditional development workflow.

Right now organizers have to edit the CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. for their site in Jetpack’s CSS editor, which is painful because it wasn’t intended for the kinds of use cases that we have.

Instead, we want to allow organizers to build their sites in a local sandbox, managing the code with GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/, and be able to easily push updates to production.

If anyone is interested in giving feedback or helping to build the tools we need, please check out the discussion.

#git, #sandbox, #wordcamp-org

Samuel Sidler 10:00 am on May 19, 2015
Tags: , ,   

Weekly i18n chat

Just a reminder that the weekly i18n chat will happen in 1 hour from this post at 11:00 UTC. If you haven’t joined us before, we discuss progress on a number of fronts for i18n on WordPress.orgWordPress.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/. We’ll likely be discussing the forums plugins audit today, in addition to other things, so read through that post ahead of time.

#i18n, #l10n, #rosetta

John James Jacoby 1:55 am on May 15, 2015
Tags: , ,   

WP.org Forums Plugins Audit

The version of bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org powering the WordPress.orgWordPress.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/ support forums is (despite being near and dear to my heart) out of date to the point of being a bottleneck towards progress on Rosetta. The plan has always been to migrate everything to bbPress 2.x, but the caveat to that otherwise (relatively) easy feat is the custom functionality that’s already built into the bbPress 1.x plugins that modify coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. behavior in a way that might not easily port over directly.

Below is an audit of those plugins, along with a brief description of what they do and the level of effort I estimate it will take to port that code. Thankfully, about half of these plugins will no longer be necessary. The other half will need to built as WordPress plugins that modify bbPress 2.x behavior.

fwiw, bbPress 2.6 is imminent (has been for a while) though I’m comfortable adding any actions or filters to bbPress core that might prevent an otherwise easy port. Stephen Edgar and myself are both available to help/assist/guide and/or to start porting these ourselves as well.

The plugins below represent 10 years of modifications to the WordPress.org support forums, and also represent an enormous opportunity for any volunteers who might want to help build the next generation of WordPress.org but maybe are not sure where to start.

Let’s use the comments below as the beginning communications towards what will likely be several individual initiatives, all working towards the common goal of bringing our support forums and the related moderation tools up to speed with the rest of bbPress and WordPress.org.

Migrate? LOE File Description
In Progress (@nullbyte) Low _author-badges.php Adds badge to 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. and theme author replies for their replies in plugin snd theme-related forums (reviews, plugins and hacks, themes and templates) that pertain to their
Pending Testing & Review
(@justingreerbbi)		 Low _bb-mail.php Custom email subject from headers for support forums
Done (@jmdodd) Medium _codify.php Converts [[wiki markup|links]] into <a href=”http://www.example.com/wiki_markup”>links</a>.
Done (@jmdodd) Low _geriatric-threads.php Add <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. name=”robots” content=”noindex,nofollow” /> to old closed topics
In Progress (@justingreerbbi) Low _lowfollow.php View replies by IP address
In Progress (@nullbyte) Low _mailing-list.php WordPress Announcements/Development News mailing list form
Yes Medium _plugin-reviews-listing.php Plugin forum custom views
Yes Medium _plugin-support-listing.php Plugin forum custom views
Yes Medium _plugin-svn-tracker-support-mock.php SVN_Tracker_Support_Mock
In Progress (@nullbyte) Medium _plugin_stickies.php Sticky topics for plugin forums
Done (@Clorith) Low _reg-hack.php This is to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. those stupid spam registrations
Done (@Clorith) Medium _registration-captcha.php Captcha for registration
Done (@Clorith) Low _registration-speed-limit.php max number of attempts per time period // time period user must wait before getting freed
In Progress (@nullbyte) Low _reviews.php Miscellaneous modifications related to the reviews forum/feature.
Yes Low _subscribe_to_plugins.php Subscribe to Plugins for wp.org
Yes Low _subscribe_to_tags.php Subscribe to Tags for wp.org
Done (@coffee2code) Low _support-wporg-notifications-allow-superadmin-regex.php WordPress.org Notifications Allow Superadmin Regex
Done (@coffee2code) Low _support-wporg-notifications.php WordPress.org Notifications
In Progress (@nullbyte) Low _tag-codex-links.php Forum codex links
In Progress (@Kenshino) Medium _template-mods.php Custom template queries
Yes Medium _theme-reviews-listing.php Custom views for theme forums
Yes Medium _theme-support-listing.php Custom views for theme forums
In Progress (@nullbyte) Medium _version-dropdown.php New topic form WordPress version dropdown field
Yes Low _views.php Custom bbPress views
Yes High bozo.php Bundled bbPress 1.x plugin that implements the bozo feature
No None _bb-quicktags.php Inserts a quicktag toolbar on the post topic form.
No None _default-role.php This should only run once per new user, as it’ll then have a capabilities meta for this site.
No None _email_login.php Disable email login???
No None _fix-badly-utf8-trimmed-strings.php FIlters topic title and terms via return iconv( ‘utf-8’, ‘utf-8//ignore’, $string );
No None _fix-topics-replied.php fix_topics_replied
No None _fix-user-search.php bbPress user search doesn’t deal with empty role arrays well
No None _fix_code_clickable.php this replaces the make_clickable function with one that won’t do anything inside <code> blocks
No None _forum_row_click.php disable until we can make this not open in a new window. If only you could do <tr href>. Curses, W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/., curses.
No None _gravatar-retina.php copy of bb_get_avatar, but with support for the devicePixelRatio 📱 cookie on .org
No None _hack_utf8_slugs.php Sanitize URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org’s with dashes (Previous versions of bbPress didn’t try using mb_strtolower(), so all slugs were in original case. This makes the slug in the database and the one which we test again different, which causes 404s.)
No None _hidden-forums.php Hides configured forums from general forum listings and prevents the forum’s topics listings. Only directly are its topics accessible.
No None _inception-fix.php Because of either bad data or some other bug, the support forums don’t know the date of their first post properly.
No Medium _international.php Hack all the i18n w.org login, menu urls, CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., keymaster roles, admin capabilities and user caps and roles
No Low _memcache.php Custom memcache settings
No None _never-upgrade.php Never upgrade the bbPress 1.x database
No None _new_plugin_post.php FilterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. post titles and tags for plugin and plugin reveiew topics
No None _new_theme_post.php Filter post titles and tags for theme and theme reveiew topics
No None _no-duplicate-emails.php DO not allow duplicate email address’ for bbPress users
No None _profile-additions.php Custom profile fields and profile sanitization
No None _queries.php Query Debug
No None _random_seed.php Skip the DB for random_seed transient – just generate an new (not very good) rnd_value on the fly
No None _return_helpers.php
No None _security.php This file loosely corresponds to wp-content/mu-plugins/security.php
No None _spamhell.php Spam Hell. Blocks for assorted spammers.
Maybe Low _add-replies-argument.php Hangs a replies=# onto every topic link, so by appropriate styling users can see new posts
Maybe Low elfakismet.php Adds the ability to stop akismet check after a user has x posts, and to always check for any you don’t trust.
Maybe Low _bb-google.php
Maybe Low _phishing_honeypot.php Check a couple of specific IP addresses and email Nacin if true
Done (@SergeyBiryukov) Low _registration-chars.php Block certain types of characters from being in usernames on registration.
Done (@SergeyBiryukov) BP? _registration-log.php Check user registration log
Maybe Low _ssl.php SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. overrides and tweaks
Maybe BP? _stats_extra.php stats logger for support forums
In Progress (@netweb) High _support-forum-admin-mods.php Related to Bozo
Maybe Low _support-forum-autoload.php Autoload 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.
In Progress (@netweb) Low _support-forum-mods.php Moderator support for support forums and plugin/theme author moderators
Maybe Low _block-spam-searches.php block_spam_searches_parse_query

#forums, #plugins, #rosetta