Title: Make WordPress.org – Page 33 – A self-referential site --- [ ](https://profiles.wordpress.org/obenland/) [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 3:52 pm _on_ August 3, 2016 Tags: [meta ( 33 )](https://make.wordpress.org/meta/tag/meta/) # 󠀁[Plugin Directory Chat Agenda](https://make.wordpress.org/meta/2016/08/03/plugin-directory-chat-agenda/)󠁿 Agenda for this week’s meeting on [August 4, 2016 at 00:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160804T0000): * Plan Milestone 6 from [existing tickets](https://meta.trac.wordpress.org/query?status=!closed&component=Plugin+Directory). * Review [feedback from Open Beta](https://make.wordpress.org/meta/2016/07/28/plugin-directory-v3-next-steps/). We’ll be meeting in [#meta](https://make.wordpress.org/meta/tag/meta/) on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). If you have anything to propose to add to the agenda, please leave a comment below. See you in the chat! * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F08%2F03%2Fplugin-directory-chat-agenda%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jmdodd/) [Jennifer M. Dodd](https://profiles.wordpress.org/jmdodd/) 6:42 pm _on_ July 29, 2016 Tags: [forums ( 18 )](https://make.wordpress.org/meta/tag/forums/), [i18n ( 17 )](https://make.wordpress.org/meta/tag/i18n/)    # 󠀁[Rosetta Forum Upgrades In Progress](https://make.wordpress.org/meta/2016/07/29/rosetta-forum-upgrades-in-progress/)󠁿 The following forums have been upgraded to bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. [https://bbpress.org](https://bbpress.org) 2 and redirected to their new locations: * pt.forums.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/](https://wordpress.org/) to pt.wordpress.org/support * id.forums.wordpress.org to id.wordpress.org/support * mya.forums.wordpress.org to mya.wordpress.org/support * de.forums.wordpress.org to de.wordpress.org/support * zh-cn.forums.wordpress.org to cn.wordpress.org/support * bs.forums.wordpress.org to bs.wordpress.org/support * th.forums.wordpress.org to th.wordpress.org/support * ja.forums.wordpress.org to ja.wordpress.org/support * ru.forums.wordpress.org to ru.wordpress.org/support * ug.forums.wordpress.org to ug.wordpress.org/support * bg.forums.wordpress.org to bg.wordpress.org/support * sr.forums.wordpress.org to sr.wordpress.org/support * tw.forums.wordpress.org to tw.wordpress.org/support * hr.forums.wordpress.org to hr.wordpress.org/support * he.forums.wordpress.org to he.wordpress.org/support * ka.forums.wordpress.org to ka.wordpress.org/support * fi.forums.wordpress.org to fi.wordpress.org/support * nl.forums.wordpress.org to nl.wordpress.org/support * mk.forums.wordpress.org to mk.wordpress.org/support * ca.forums.wordpress.org to ca.wordpress.org/support * sk.forums.wordpress.org to sk.wordpress.org/support * pl.forums.wordpress.org to pl.wordpress.org/support * ro.forums.wordpress.org to ro.wordpress.org/support * es.forums.wordpress.org to es.wordpress.org/support * br.forums.wordpress.org to br.wordpress.org/support I’ll continue to update this list as I upgrade forums. **All existing language-specific forums have been upgraded to bbPress 2.** For larger forums, I will set redirects in place about thirty minutes before the end of a upgrade run to avoid having to backfill posted content. This will be noticeable to users when they are forwarded to the in-progress new forum location. Moderator roles are being transferred from the old forum to the new one. Ported metadata includes user topic and topic tag subscriptions and favorites, as well as the topic resolution and WordPress version. See https://meta.trac.wordpress.org/ticket/1544 for known issues and bug reports. [#forums](https://make.wordpress.org/meta/tag/forums/) [#i18n](https://make.wordpress.org/meta/tag/i18n/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F29%2Frosetta-forum-upgrades-in-progress%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/obenland/) [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 7:40 pm _on_ July 28, 2016 Tags: [plugin directory ( 45 )](https://make.wordpress.org/meta/tag/plugin-directory/) # 󠀁[Plugin Directory v3: Next Steps](https://make.wordpress.org/meta/2016/07/28/plugin-directory-v3-next-steps/)󠁿 ### The Past 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. team kicked off the new version of 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. directory at the end of February. Some of the initial desired improvements included: moving to WordPress, open-sourcing the codebase, improving search, feature parity, and making the plugin review process more scalable. One aspect that was looked at were taxonomies. [An outline of the challenges](https://make.wordpress.org/plugins/2016/02/25/re-thinking-tags-in-the-plugin-directory/) was posted on make/plugins and followed up by [a proposal on how these can be met](https://make.wordpress.org/meta/2016/05/20/taxonomies-in-the-plugin-directory/). Another aspect was the design itself, with prototypes published ([#1](https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/), [#2](https://make.wordpress.org/meta/2016/05/20/plugin-directory-prototypes-single-view/)) and feedback gathered, before they were converted into a theme. Finally, [I spoke at WordCamp Europe](http://wordpress.tv/2016/06/30/konstantin-obenland-the-2016-plugin-directory/) about the work done so far, providing more details about some of the decisions made, and asking the community for feedback on the prototype during [an open beta phase](https://make.wordpress.org/meta/2016/07/12/plugin-directory-v3-open-beta/). ### The Present (and Feedback) We’ve received a lot of feedback about the plugin details page and some improvements that could be made. A number of people mentioned that too many “read more” links can make it hard for users to find relevant information, blending the sections together, and that content may not be indexed properly by search engines. Others were concerned about the effects of partially hiding the plugin description, the loss google site links for sections, and how the accordion behavior may not be ideal on smaller touch devices. Another part of the new directory that received a lot of feedback is the simplified plugin cards on the front-page and search results. Many reported that they missed some of the specific data, present in the old directory; namely, active install count, last updated date, and author. Without this information they’d have to view the details of each plugin to get more information and make an informed decision. In terms of search, there are a number of improvements that still need to be made. Various queries includes subjectively irrelevant results and often do not surface a plugin despite searching an exact match of its name. One suggestion to mitigate that we’ll explore, is to emphasize matches in tags and matches in a plugin’s description. A future enhancement we’d like to add that has been discussed quite a bit is showing categories on the front page instead of (or in addition to) curated sections to show the breath and depth of the directory. An additional section could also include“ trending” plugins, with an algorithm backing it. Plugin authors really like the dashboard, but there’s no reason that it can’t be entirely public, instead of housed within `wp-admin`. If a plugin author is logged in, this view would show options for them. For other visitors, an overview of every plugin from a plugin author could be helpful. One of the decisions we made early on was to switch from freeform tags to categories. However, this switch limits the ability for plugin authors to change tags at-will and doesn’t allow the same flexibility as freeform tags, requiring editorial decisions on categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. names. Conversely, unlimited freeform tags have been abused and are not helpful to users. One idea is to bring back freeform tags, but limit the number show (and indexed) to five. In bringing parts of the `readme.txt` file into the 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., we attempted to make it easier for developers to manage their plugins without making a commit. However, there are other ways we could solve this. For example, compatibility could be crowdsourced automatically from installed versions of plugins and WordPress. The developer-provided value would become less interesting in this case. Knowing if the user thinks it works is more interesting than knowing if the developer thinks it works. In other cases, we could also allow editing of the `readme.txt` file within a web UI, automatically committing these changes 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/. for the plugin author. ### The Future Going forward we’d like to discuss community feedback and review some of the design decisions, as well as plan how the interfaces for plugin reviews and plugin authors should look like and behave. An important first step will be to reinstate weekly meetings, starting next week, and get back into a rhythm of setting milestones, attaching tickets to them, and complete them in due time. The next Plugin Directory meeting will be [ August 4, 2016 at 00:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160804T0000). [#plugin-directory](https://make.wordpress.org/meta/tag/plugin-directory/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F28%2Fplugin-directory-v3-next-steps%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 5:55 pm _on_ July 27, 2016 Tags: [wordpress-meta-environment ( 5 )](https://make.wordpress.org/meta/tag/wordpress-meta-environment/) # 󠀁[Meta Environment Now Supports Contributing with Git](https://make.wordpress.org/meta/2016/07/27/meta-environment-now-supports-contributing-with-git/)󠁿 [The Meta Environment](https://github.com/WordPress/meta-environment/) has always managed its coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality in 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/](https://git-scm.com/), but up until now, it used SubversionSVN 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/. to check out the actual files that make up each 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. website. New contributors are much more likely to be familiar with Git than 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/., though. Requiring them to learn SVN in addition to all of  our other tools and processes introduced an unnecessary burden. The goal of the Environment is to help make contributing as easy as possible, so it makes sense to switch to Git instead. As of today, [that switch is complete](https://github.com/WordPress/meta-environment/issues/13), and new installations will use Git automatically. The two exceptions are: 1) Any 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. or theme that doesn’t have an official Git mirror; 2) the entire 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/](https://wordpress.org/) site, since [it’s in the process of migrating to GlotPress 2](https://github.com/WordPress/meta-environment/issues/54). In those cases, SVN is still used. If you have an existing installation, it will continue to use Subversion until you` git pull` the latest copy of the Environment, and run `vagrant provision`. During that provision, each site’s `public_html` folder will be backed up to `public_html- old-svn-backup`, and a new Git-based `public_html` folder will be provisioned. If you’re working on any unfinished patches, just copy the modified files from the old directory to the new one. If you’d like to learn more about contributing with Git, check out this guide from the Meta Handbook: > [Contributing With Git](https://make.wordpress.org/meta/handbook/documentation/contributing-with-git/) [#wordpress-meta-environment](https://make.wordpress.org/meta/tag/wordpress-meta-environment/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F27%2Fmeta-environment-now-supports-contributing-with-git%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/drewapicture/) [Drew Jaynes](https://profiles.wordpress.org/drewapicture/) 4:52 am _on_ July 26, 2016 Tags: [devhub ( 4 )](https://make.wordpress.org/meta/tag/devhub/), [meta-devhub ( 2 )](https://make.wordpress.org/meta/tag/meta-devhub/)    # 󠀁[No DevHub chat this week](https://make.wordpress.org/meta/2016/07/26/no-devhub-chat-this-week/)󠁿 We won’t be having a DevHub chat this week. I will be unavailable to run the chat and it sounds like [@coffee2code](https://profiles.wordpress.org/coffee2code/) won’t be available either. Chats are normally held on [Tuesdays at 18:00 UTC](http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160712T1800) in the [#meta-devhub](https://wordpress.slack.com/messages/meta-devhub/) channel. We’ll pick up scrubbing the [remaining tickets](https://meta.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=Developer+Hub&order=priority) in the DevHub component report next week at the usual time and place. [#devhub](https://make.wordpress.org/meta/tag/devhub/), [#meta-devhub](https://make.wordpress.org/meta/tag/meta-devhub/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F26%2Fno-devhub-chat-this-week%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jmdodd/) [Jennifer M. Dodd](https://profiles.wordpress.org/jmdodd/) 5:09 pm _on_ July 12, 2016 Tags: [forums ( 18 )](https://make.wordpress.org/meta/tag/forums/), [meta ( 33 )](https://make.wordpress.org/meta/tag/meta/)    # 󠀁[Forum Upgrade Update](https://make.wordpress.org/meta/2016/07/12/forum-upgrade-update/)󠁿 Hello again! It is time for a progress update on the forum upgrade project. ​ ** Plugins** 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. has had volunteers working on converting various forum-related plugins for the past year or so, and we’re now at the point where those plugins are being committed. When doing conversions, I’ve tried to concentrate on the spirit of the code, rather than having an exact match. We can’t adhere strictly to the filters and actions that were previously available in bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. [https://bbpress.org](https://bbpress.org) 1, as these do not always map well to a bbPress 2 code path. Additionally, in some cases bbPress 2 has a better hook available, so we can avoid needing to code conditionals into the new plugins by choosing a more precise hook. ​ I’m currently working through and committing the backlog of converted plugins. These are being updated to use common meta.trac.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/](https://wordpress.org/) code structures and the ‘wporg’ text domain for translations. Generally speaking, simple filtering plugins are being committed as classes, while more complex plugins that require an admin or user interface use namespaces. All of these plugins are 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. (GPL2+), and can be used in other bbPress installations. All are also easily testable with a local installation of bbPress 2 or the meta environment. ​ Some plugins which are integral to all of the forums are: * [Topic Resolution](https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-bbp-topic-resolution)— this allows topics to be set to ‘unresolved’, ‘resolved’, and ‘not a support question’ (formerly known as Support Forums) * [Version Dropdown](https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-bbp-version-dropdown)— this allows the user to set the WordPress version relevant to a given topic * Subscribe to Tags — this allows the user to subscribe to a given tag and will play an important part in the 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. for plugins and themes * [User Moderation](https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-bbp-user-moderation)— this sets a user’s posts to be automatically moderated ​ Because all of the above plugins actually create and store data, rather than just filtering it, it is important that they be ported prior to forum upgrade. I’d rather spend the time to get all the moving pieces in place rather than convert a forum and then discover later on that I’ve left something important behind, like tag subscriptions. It is far easier to run the complete conversion once rather than trying to backfill unported data from the old tables, especially when it involves user metadata. ​ Props go to everyone who has contributed code 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. overhauls, including [@nullbyte](https://profiles.wordpress.org/nullbyte/),@ justingreerbbl, [@Clorith](https://profiles.wordpress.org/clorith/), [@coffee2code](https://profiles.wordpress.org/coffee2code/), [@Kenshino](https://profiles.wordpress.org/kenshino/), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/), and [@netweb](https://profiles.wordpress.org/netweb/). ​ **URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress. org redirects** I’ve written a bbPress 1 plugin to handle requests to the original forum location; this will allow me to incrementally convert *.forums.wordpress.org to *.wordpress.org/support without needing to constantly update the nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. [https://www.nginx.com/](https://www.nginx.com/). rewrite rules. Once all the forums have been converted, then the nginx rewrite rules can be updated once and plugin removed. ​ **Conversion script** In my first pass, I took care of most of the topic meta and user options that were plugin related, but missed the tag subscriptions and user favorites. I’ve had to go back and code some parts of the conversion script to handle this data, as well as dealing with iterating over the usermeta table. ​ I’ll be committing the required plugins all week so that I can start running the conversion script. Plugin testing is welcome; please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) on [#meta](https://make.wordpress.org/meta/tag/meta/) if you have any questions or suggestions regarding the ported plugins. [#forums](https://make.wordpress.org/meta/tag/forums/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F12%2Fforum-upgrade-update%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/obenland/) [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 3:26 pm _on_ July 12, 2016 Tags: [plugin directory ( 45 )](https://make.wordpress.org/meta/tag/plugin-directory/) # 󠀁[Plugin Directory v3 Open Beta](https://make.wordpress.org/meta/2016/07/12/plugin-directory-v3-open-beta/)󠁿 We’ve been working on [the new, WordPress-based version of the Plugin Directory](https://wordpress.org/plugins-wp/) and it’s at a point where 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. team would like to open it up to the community to foster participation and receive feedback. You can find the latest iteration of it under the temporary URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: https://wordpress.org/plugins-wp/ If you have commit access to a 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. in the existing directory and are logged in to your 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/](https://wordpress.org/) account, you also have access to [the provisional developer interface](https://wordpress.org/plugins-wp/wp-admin). Please keep in mind that it is by far not a finished product. There is still a lot of work to be done, mainly around front-end technology, search, and developer facing interfaces. Every decision that has been made so far is up for discussion, which is the purpose of this post. You can find a history of all previous discussions at [#plugin-directory](https://make.wordpress.org/meta/tag/plugin-directory/). We’ve already received a good amount of feedback after [my WCEU session](http://wordpress.tv/2016/06/30/konstantin-obenland-the-2016-plugin-directory/) on [meta trac](https://meta.trac.wordpress.org/query?status=!closed&component=Plugin+Directory), the [summary post](https://make.wordpress.org/meta/2016/06/08/plugin-directory-v3-chat-summary-61/) of our last chat, and in blog posts throughout the community. But we’re looking for more! 🙂 Please feel free to leave general feedback as comments on this post, and specific bug reports as [new tickets on meta Trac](https://meta.trac.wordpress.org/newticket?component=Plugin%20Directory)( [but make sure it doesn’t exist yet](https://meta.trac.wordpress.org/query?status=!closed&component=Plugin%20Directory)). The meta team will go through all feedback, derive a prioritized list of suggestions from it, and work it into the iteration schedule. Thank you for your participation! * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F12%2Fplugin-directory-v3-open-beta%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/mapk/) [Mark Uraine](https://profiles.wordpress.org/mapk/) 9:32 pm _on_ July 11, 2016 Tags: [design ( 20 )](https://make.wordpress.org/meta/tag/design/), [forums ( 18 )](https://make.wordpress.org/meta/tag/forums/)    # 󠀁[Forum Design Research](https://make.wordpress.org/meta/2016/07/11/forum-design-research/)󠁿 As some may have noticed there are efforts to [improve the support forums](https://make.wordpress.org/meta/2016/06/06/wordpress-org-forums-user-meta/) 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/](https://wordpress.org/). In addition to the backend changes, this seems like a good time to make some design upgrades as well. To kick things off, I’ve done a bit of research into various forum designs in use online (similar to the [web store explorations for the plugin directory](https://make.wordpress.org/design/2016/03/15/various-web-store-flow-explorations/)). If you’re interested in the forums, please take some time to review the research here and leave your feedback. What stands out from these examples as something you’d like to see implemented on WordPress.org? Which design feature is your favorite and why? [⌊Feature comparison⌉⌊Feature comparison⌉[ Feature comparison Below are some screenshots from each of the forums reviewed. ### **Non-bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. 󠀁[https://bbpress.org](https://bbpress.org)󠁿 Support Forums** * Apple: [https://cloudup.com/c1g4kOG19vz](https://cloudup.com/c1g4kOG19vz) * Blizzard: [https://cloudup.com/cb6CQY8gcJ4](https://cloudup.com/cb6CQY8gcJ4) * Microsoft: [https://cloudup.com/cLW_W21tbxl](https://cloudup.com/cLW_W21tbxl) * Playstation: [https://cloudup.com/cOeN4SGlP-t](https://cloudup.com/cOeN4SGlP-t) * Wix: [https://cloudup.com/cAWRVRStBID](https://cloudup.com/cAWRVRStBID) * Weebly: [https://cloudup.com/cMRmBbqk7kp](https://cloudup.com/cMRmBbqk7kp) * Squarespace: [https://answers.squarespace.com/](https://answers.squarespace.com/) * Zendesk: [https://support.zendesk.com](https://support.zendesk.com/) ### bbPress Support Forums * WordPress.org: [https://cloudup.com/cqwGcvwfm7h](https://cloudup.com/cqwGcvwfm7h) * ACF: [https://cloudup.com/c77XOj42RiN](https://cloudup.com/c77XOj42RiN) * Cycling 74: [https://cloudup.com/cwiyHn0UhTu](https://cloudup.com/cwiyHn0UhTu) * Makeup Geek: [https://cloudup.com/cf3A7hZ4_bg](https://cloudup.com/cf3A7hZ4_bg) * Mojo Themes: [https://cloudup.com/cXBAJZ26hmh](https://cloudup.com/cXBAJZ26hmh) * One More Thing: [https://cloudup.com/csZWalYf5R7](https://cloudup.com/csZWalYf5R7) * Wonderful Mama: [https://cloudup.com/c8hoUqOBgQt](https://cloudup.com/c8hoUqOBgQt) * WPML: [https://cloudup.com/cpYhubKse0O](https://cloudup.com/cpYhubKse0O) ### Thank You Thank you for your feedback! If there are other forums designs you’ve seen on the internet that should be reviewed, leave a comment here, along with any other feedback you have. [#design](https://make.wordpress.org/meta/tag/design/), [#forums](https://make.wordpress.org/meta/tag/forums/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F11%2Fforum-design-research%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/drewapicture/) [Drew Jaynes](https://profiles.wordpress.org/drewapicture/) 12:20 am _on_ July 11, 2016 Tags: [meta-devhub ( 2 )](https://make.wordpress.org/meta/tag/meta-devhub/) # 󠀁[DevHub Weekly Chats are restarting](https://make.wordpress.org/meta/2016/07/11/devhub-weekly-chats-are-restarting/)󠁿 Beginning [Tuesday, July 12, 2016 18:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160712T1800), we’ll be restarting weekly DevHub chats in the [#meta-devhub](https://make.wordpress.org/meta/tag/meta-devhub/) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). For the uninitiated, the [Developer Hub](https://developer.wordpress.org), or “DevHub”, largely serves as the new official source for developer documentation 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/](https://wordpress.org/). The DevHub team’s responsibilities cover the [phpdoc-parser](https://github.com/WordPress/phpdoc-parser) project, as well as infrastructure behind the [Code Reference](https://developer.wordpress.org/reference/), Theme and [Plugin](https://developer.wordpress.org/plugins/) and Developer handbooks, resources pages, and more. Getting weekly chats restarted should allow us to gather more regularly as a team and get group feedback, as well as set direction for new features or improvements. See you on Tuesday! * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F07%2F11%2Fdevhub-weekly-chats-are-restarting%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/obenland/) [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 6:56 pm _on_ June 8, 2016 Tags: [plugin directory ( 45 )](https://make.wordpress.org/meta/tag/plugin-directory/) # 󠀁[Plugin Directory v3 Chat Summary (6/1)](https://make.wordpress.org/meta/2016/06/08/plugin-directory-v3-chat-summary-61/)󠁿 This is a summary of 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Directory chat from June 1. ([Slack log](https://wordpress.slack.com/archives/meta/p1464825603002226)) **Attendees**: [@dd32](https://profiles.wordpress.org/dd32/), [@samuelsidler](https://profiles.wordpress.org/samuelsidler/),@ mapk, [@pento](https://profiles.wordpress.org/pento/), [@tellyworth](https://profiles.wordpress.org/tellyworth/), [@obenland](https://profiles.wordpress.org/obenland/) ### Topics: * **Review M4** [M4](https://meta.trac.wordpress.org/query?group=status&milestone=Plugin+Directory+v3+-+M4) had eight tickets assigned to it, four were fixed by the time of the meeting. [#1575](https://meta.trac.wordpress.org/ticket/1575) had a patch for the non- open-sourced part that was committed a day later and fixed the ticket. There was some follow-up work that re-instated using the old directory as the data source but largely satisfied the requirements. [#1579](https://meta.trac.wordpress.org/ticket/1579) was waiting for a commit. [#1722](https://meta.trac.wordpress.org/ticket/1722) was moved into M5, waiting for a final commit later that week. [#1692](https://meta.trac.wordpress.org/ticket/1692) was also moved into M5, waiting for more updates. * **Plan M5** After our [prioritization pow wow](https://wordpress.slack.com/archives/meta/p1464314732002065) the week before, [M5](https://meta.trac.wordpress.org/query?group=status&milestone=Plugin+Directory+v3+-+M5) almost planned itself. [#1720](https://meta.trac.wordpress.org/ticket/1720), [#1573](https://meta.trac.wordpress.org/ticket/1573), [#1578](https://meta.trac.wordpress.org/ticket/1578), and [#1691](https://meta.trac.wordpress.org/ticket/1691) sat atop of the list and need most attention. [#1742](https://meta.trac.wordpress.org/ticket/1742) was also added to the milestone, as a left-over task from [#1575](https://meta.trac.wordpress.org/ticket/1575). The next meeting is on [Thursday June 9, 00:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160609T0000). [#plugin-directory](https://make.wordpress.org/meta/tag/plugin-directory/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2016%2F06%2F08%2Fplugin-directory-v3-chat-summary-61%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/meta/page/34/?output_format=md) [Newer posts →](https://make.wordpress.org/meta/page/32/?output_format=md)