Thank you to everyone who came. For anyone unable to attend, you can read the logs here.
The following is a summary of the topics that were discussed.
1. DevHub: There’s been a lot of activity on the developer.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets this past week, primarily by @Rarst and @nlarnold1. Good progress is being made on the design change tickets.
2. Docs Issue Tracker: Per @samuelsidler, @Otto42 is still working on it, and making progress.
During our initial discussions about what we would like to see in the issue tracker, several things were mentioned that aren’t included in initial development. I’ll be working through those posts, gathering a list of those items and posting that list, most likely in a Meta Trac ticket. We can review the list after development is complete, and we’ve been using the tracker for awhile to see what items we may still want to add.
3. AH-O2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: Per @jazzs3quence, the team has removed the use of title attributes from the plugin 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, based on @grahamarmfield‘s extensive accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) review of the plugin, and the fact that those attributes are being removed from core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Version 0.6 of the plugin has been released, incorporating those recommendations, and is available in the repo. Please download the plugin, test, and provide feedback to the team. (2/10/2014 team meeting summary)
4. Handbooks: @hanni provided an extensive update on the status of the handbooks, and the plans now being put in place to move the effort forward at a much faster pace. @hanni will be posting the details of these plans early next week.
We also discussed the status of handbooks being produced by the other teams. @netweb brought up a post on Make/Polyglots regarding their Handbook. If you are interested in helping write the Polyglots handbook, @samuelsidler will be posting on Make/Polyglots asking for volunteers.
5. First Steps for Docs Contributors: We received some very helpful feedback from the comments, and changes have been made to incorporate that feedback. If you have not had the chance to review it, please take the time to do so, and leave your feedback so we can get this completed. (original post | draft page)
6. Docs Project Landing Pages: I’ll be creating the landing pages for each of the listed projects this weekend so that each team can begin adding the information about their respective projects. The Inline Docs landing page is a good example to follow. We would like to have these completed by February 28th.
We would also like to thank our outgoing team rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts., @sewmyheadon, for all of his hard work. We look forward to your continued contributions. 🙂
#chat-recap
