Title: Make WordPress.org – Page 42 – A self-referential site --- [ ](https://profiles.wordpress.org/isaackeyet/) [Isaac Keyet](https://profiles.wordpress.org/isaackeyet/) 11:30 pm _on_ November 4, 2013 Tags: [forums ( 18 )](https://make.wordpress.org/meta/tag/forums/), [mobile ( 3 )](https://make.wordpress.org/meta/tag/mobile/)    # 󠀁[Migrating & Merging Mobile App Forums](https://make.wordpress.org/meta/2013/11/04/migrating-merging-mobile-app-forums/)󠁿 Hey guys, this is something we’ve discussed many times in the past and.. what can I say. It’s close to our hearts. To recap, the plan of action was to… * Collect all threads and rooms within each of the apps forums (ex.: [ios.forums.wordpress.org](http://ios.forums.wordpress.org)). I know [@nacin](https://profiles.wordpress.org/nacin/) had made some progress on this. * Create a new subforum here 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/) titled “Mobile Apps” or similar. * Import each forum as a sub-forum of “Mobile Apps” * Mobile group to manually go through and add cross-platform threads (like FAQs, 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. blacklist, general how-tos). If I remember correctly we figured we could start with a forum that has extremely low traffic to see how that goes, say the Nokia app’s forum (an app that’s in hibernation). What do you think? Does this fit in on the road map? [#forums](https://make.wordpress.org/meta/tag/forums/), [#mobile](https://make.wordpress.org/meta/tag/mobile/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F11%2F04%2Fmigrating-merging-mobile-app-forums%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 7:26 pm _on_ October 25, 2013 Tags: [plugin ( 4 )](https://make.wordpress.org/meta/tag/plugin/) # 󠀁[Could we install the co authors plus plugin…](https://make.wordpress.org/meta/2013/10/25/could-we-install-the-co-authors-plus-plugin/)󠁿 Could we install the [co-authors plus plugin](https://wordpress.org/plugins/co-authors-plus/)? Thanks! [#plugin](https://make.wordpress.org/meta/tag/plugin/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F10%2F25%2Fcould-we-install-the-co-authors-plus-plugin%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 4:46 pm _on_ October 23, 2013 Tags: [community ( 2 )](https://make.wordpress.org/meta/tag/community/), events, [import ( 2 )](https://make.wordpress.org/meta/tag/import/), [make ( 14 )](https://make.wordpress.org/meta/tag/make/) # 󠀁[A while back on September 11 @andreamiddleton tried…](https://make.wordpress.org/meta/2013/10/23/a-while-back-on-september-11-andreamiddleton-tried/)󠁿 A while back on September 11, [@andreamiddleton](https://profiles.wordpress.org/andreamiddleton/) tried to import the /events blog into the /community blog since we were merging teams. She hit a bug/error/some kind of blocker in the import and [reported it](https://make.wordpress.org/meta/2013/09/11/today-i-imported-all-make-wordpress-org-events/). [@nacin](https://profiles.wordpress.org/nacin/) and [@otto42](https://profiles.wordpress.org/otto42/) said they’d look into the weird encoding issues. It wasn’t a priority, sure, but in the meantime we’re double-posting stuff and we still haven’t truly merged the groups. Could someone see if this can be figured out? Thanks! [#community](https://make.wordpress.org/meta/tag/community/), [#events](https://make.wordpress.org/meta/tag/events/), [#import](https://make.wordpress.org/meta/tag/import/), [#make](https://make.wordpress.org/meta/tag/make/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F10%2F23%2Fa-while-back-on-september-11-andreamiddleton-tried%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 4:11 pm _on_ October 23, 2013 Tags: [community ( 2 )](https://make.wordpress.org/meta/tag/community/), [make ( 14 )](https://make.wordpress.org/meta/tag/make/), [plugin ( 4 )](https://make.wordpress.org/meta/tag/plugin/) # 󠀁[@otto42 @iandunn posted a plugin on trac for…](https://make.wordpress.org/meta/2013/10/23/otto42-iandunn-posted-a-plugin-on-trac-for/)󠁿 [@otto42](https://profiles.wordpress.org/otto42/): [@iandunn](https://profiles.wordpress.org/iandunn/) [posted a plugin on trac](https://meta.trac.wordpress.org/ticket/187) for the /community team site 5 weeks ago. Could that get added, or if it’s not ready could you tell him what he needs to change? It’s a bottleneck for some stuff we want to do on our team site to make it easier for groups working on separate projects. Thanks! [#community](https://make.wordpress.org/meta/tag/community/), [#make](https://make.wordpress.org/meta/tag/make/), [#plugin](https://make.wordpress.org/meta/tag/plugin/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F10%2F23%2Fotto42-iandunn-posted-a-plugin-on-trac-for%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/aerych/) [Eric](https://profiles.wordpress.org/aerych/) 10:49 pm _on_ October 7, 2013 Tags: [design ( 20 )](https://make.wordpress.org/meta/tag/design/), [mobile ( 3 )](https://make.wordpress.org/meta/tag/mobile/)    # 󠀁[Digging the make blog redesign I notice that…](https://make.wordpress.org/meta/2013/10/07/digging-the-make-blog-redesign-i-notice-that/)󠁿 Digging the make blog redesign. I notice that the “learn more about mobile” link points back to the home page. Can this be updated to point to the mobile make blog? Thanks! [#design](https://make.wordpress.org/meta/tag/design/), [#mobile](https://make.wordpress.org/meta/tag/mobile/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F10%2F07%2Fdigging-the-make-blog-redesign-i-notice-that%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/merty/) [Mert Yazıcıoğlu](https://profiles.wordpress.org/merty/) 2:58 pm _on_ September 21, 2013 Tags: [gsoc ( 14 )](https://make.wordpress.org/meta/tag/gsoc/), [profiles ( 19 )](https://make.wordpress.org/meta/tag/profiles/)    # 󠀁[Profiles – Screencast](https://make.wordpress.org/meta/2013/09/21/profiles-screencast/)󠁿 As you know, I’m worked on enhancing profiles.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/) as a part of GSoC’13 and this is my final update. My last task was to prepare screencast to briefly explain the new design and here it is! It was a great summer and I would like to thank [@boonebgorges](https://profiles.wordpress.org/boonebgorges/), [@coffee2code](https://profiles.wordpress.org/coffee2code/), [@jenmylo](https://profiles.wordpress.org/jenmylo/) and everyone who supported me throughout the summer with their comments and feedbacks! Looking forward to the deployment of the new design! See you later! [#gsoc](https://make.wordpress.org/meta/tag/gsoc/), [#profiles](https://make.wordpress.org/meta/tag/profiles/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F21%2Fprofiles-screencast%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 2:40 pm _on_ September 21, 2013   # 󠀁[Added @krogsgard as an author here as he’s…](https://make.wordpress.org/meta/2013/09/21/added-krogsgard-as-an-author-here-as-hes/)󠁿 Added [@krogsgard](https://profiles.wordpress.org/krogsgard/) as an author here, as he’s getting started on the Make home site work. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F21%2Fadded-krogsgard-as-an-author-here-as-hes%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/merty/) [Mert Yazıcıoğlu](https://profiles.wordpress.org/merty/) 9:26 pm _on_ September 17, 2013 Tags: [gsoc ( 14 )](https://make.wordpress.org/meta/tag/gsoc/), [profiles ( 19 )](https://make.wordpress.org/meta/tag/profiles/), [weekly update ( 13 )](https://make.wordpress.org/meta/tag/weekly-update/) # 󠀁[Profiles – Weekly Update 13](https://make.wordpress.org/meta/2013/09/17/profiles-weekly-update-13/)󠁿 As you know, I’m working on enhancing profiles.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/) as a part of GSoC’13 and this is my thirteenth weekly update regarding how things are going. This past week, I fixed all the bugs [@coffee2code](https://profiles.wordpress.org/coffee2code/) reported and also wrote 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. for WordPress to install on blogs under the make subdomain so that we can track the publishing activities on these blogs as well. You can see the plugin here: [new-blog-post-notifier.php](https://gsoc.svn.wordpress.org/2013/merty/wp/wp-content/mu-plugins/new-blog-post-notifier.php). Also, updated the [documentation](https://gsoc.svn.wordpress.org/2013/merty/docs/) to reflect the addition. This week, as you know, is the final week so I’ll be wrapping things up and preparing a screencast. Also, Jen will probably be providing us some feedback regarding 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./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. of the new profile design. See you next week! [#gsoc](https://make.wordpress.org/meta/tag/gsoc/), [#profiles](https://make.wordpress.org/meta/tag/profiles/), [#weekly-update](https://make.wordpress.org/meta/tag/weekly-update/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F17%2Fprofiles-weekly-update-13%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 2:56 am _on_ September 17, 2013 Tags: [plugin directory ( 45 )](https://make.wordpress.org/meta/tag/plugin-directory/), plugin support    # 󠀁[Support Expectations for Meta Plugins in the WordPress.org Repository](https://make.wordpress.org/meta/2013/09/17/support-expectations-for-meta-plugins-in-the-wordpress-org-repository/)󠁿 For plugins that we release into 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/](https://wordpress.org/) repository (like CampTix and Tagregator), what should our support policy be? Since we have a lot of things we want to accomplish, and a limited set of resources, my opinion is that we should provide _product support_, but not _user support_. i.e., we should fix bugs and security vulnerabilities, but not help people who are having trouble using 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., or who want to customize it to fit their specific needs. The would ensure that the quality remains high, but would avoid us getting bogged down with doing other people’s work for them. We could manage expectations by having something like this in plugin description: > Support Expectations: > We created this plugin to scratch our own itch, and are happy to offer the code > to the community in the spirit of 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.. > We are only able to provide limited support, however. If you find a legitimate > bug or security vulnerability∗, please let us know; we take those seriously and > will fix them. > On the other hand, if you’re just having trouble using the plugin, or making it > fit your specific needs, then you’ll need to solve the problem yourself, hire > a developer, or get help from the community. > ∗ If you do find a security issue, please disclose it to us privately by sending > an e-mail to security@wordpress.org, so that we can release a fix for it before > you publish your findings. What are everyone’s thoughts on that? [#plugin-directory](https://make.wordpress.org/meta/tag/plugin-directory/), [#plugin-support](https://make.wordpress.org/meta/tag/plugin-support/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F17%2Fsupport-expectations-for-meta-plugins-in-the-wordpress-org-repository%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/samuelsidler/) [Samuel Sidler](https://profiles.wordpress.org/samuelsidler/) 12:37 am _on_ September 12, 2013 Tags: docs issue tracker, [projects ( 4 )](https://make.wordpress.org/meta/tag/projects/), [spec ( 3 )](https://make.wordpress.org/meta/tag/spec/)    # 󠀁[Documentation Issue Tracker Specification](https://make.wordpress.org/meta/2013/09/12/documentation-issue-tracker-specification/)󠁿 The Docs team tracks, modifies, and improves documentation across the WordPress project including in: CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the Codex, the upcoming Handbooks, and other parts of 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/) and related websites. Throughout the project, code and design issues get tracked in tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).( both the core and 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. tracs), but this method isn’t the most efficient for tracking documentation issues. Thus, a documentation issue tracker has been proposed by the Docs team. ## Goals The documentation issue tracker has two main goals: * easy reporting of issues throughout the project to Docs team * easy tracking of reported issues A successful documentation issue tracker ultimately will improve documentation throughout the project. ## Stakeholders The docs team is the major stakeholder for this project, given they will be primarily using the tracker. An owner is needed. [@samuelsidler](https://profiles.wordpress.org/samuelsidler/) will project manage and work with the docs team and owner. ## Solutions There are two major features to a documentation issue tracker: 1. reporting interface 2. tracking interface To ensure we complete our goals, we’ll use the following metrics: * user tests of end users reporting documentation issue (to ensure it’s easy) * feedback from Docs team for tracking ## Components As stated above, there are two components to the documentation issue tracker: Reporting and Tracking. #### Reporting The reporting interface will need to collect a bit of information automatically ( when possible) for submission to the tracker. Specifically, we’ll be collecting the username of the reporter, the date an issue was reported, an issue type (user selectable), link to page (using the referrer, when possible), and a custom, user- created description. Users will need to be logged into their wordpress.org account to file an issue. If they are not logged in, we’ll redirect them to the login page first. There may be interactions that break here, for example the referrer may get lost if a user has to log in before reporting an issue. We still need to determine where this reporting interface will exist (only on a specific page or a link everywhere?) Completed Steps: * determined more details about the what information to collect and when * [@karmatosed](https://profiles.wordpress.org/karmatosed/) designed reporting interface * [initial mockups posted](https://make.wordpress.org/docs/2013/11/04/docs-issue-tracker-mockups/) for feedback * final mockup created * [@Otto42](https://profiles.wordpress.org/otto42/) has agreed to develop the reporting interface Next Steps: * work with the Docs and Meta teams to determine where the interface will live #### Tracking The tracking interface will be used mostly by the Docs team to track incoming and active issues. Part of this interface involves viewing issues individually and changing their status. Editors (or Gardeners) will need specific permissions to make actions. More specifically, we will require users to have the “Editor” user role to resolve issues. On the tracking interface, we’ll want to display the following information: username of the reporter, the date an issue was reported, issue type, link to page, person assigned to an issue, a button that assigns an issue to you, and a resolve check box. A user-created description will exist and can be revealed with a “reveal arrow.” Completed Steps: * made decisions about specific information required and user roles that will be able to resolve issues * [@karmatosed](https://profiles.wordpress.org/karmatosed/) designed tracking interface * [initial mockups posted](https://make.wordpress.org/docs/2013/11/04/docs-issue-tracker-mockups/) for feedback * final mockup created * [@Otto42](https://profiles.wordpress.org/otto42/) has agreed to develop tracking interface (possibly using P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at [https://make.wordpress.org](https://make.wordpress.org/) with the resolved posts 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.) Next Steps: * determine where tracker will live Note: As it stands right now, this issue tracker will likely have a one-size-fits all tracking interface and not allow much customization as far as tracking. However, eventually we will want to allow sorting by “component.” [#docs-issue-tracker](https://make.wordpress.org/meta/tag/docs-issue-tracker/), [#projects](https://make.wordpress.org/meta/tag/projects/), [#spec](https://make.wordpress.org/meta/tag/spec/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F12%2Fdocumentation-issue-tracker-specification%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/meta/page/43/?output_format=md) [Newer posts →](https://make.wordpress.org/meta/page/41/?output_format=md)