Dev Chat Summary: March 29th (4.7.4 week 4)

This post summarizes the dev chat meeting from March 29th (agendaSlack archive).

4.7.4 Planning

  • There were only 35 open tickets in the milestone at the time of the meeting.
  • 2 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs over the last 2 weeks helped close a lot of those open tickets.
  • The releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. is still on schedule for the first week of May, but a few more bug scrubs are necessary.
  • If you have owned a ticketticket Created for both bug reports and feature development on the bug tracker., please help test it!
  • Next bug scrub will take place on April 3, 2017 at 17:00 UTC. @stevenkword offered to help.

Editor Team

  • Nothing in particular to discuss this week.
  • Work continues on the editor feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..
  • Day to day discussion and work happens in the #core-editor 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/. channel, and the Gutenberg GitHub project.
  • Help testing, feedback, and contributions are welcome in both places.

REST API Team

  • No updates this week.
  • Work continues in the #core-restapi Slack channel.
  • There are some component tickets in the 4.7.4 milestone that will hopefully be closer to merge this week.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps

  • @desrosj, @stevenkword, and @adamsilverstein all volunteered to help @logankipp as a Core team repTeam 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..
  • All three are attending WCEU and the Community Summit.

Open Floor Items

  • @dlh brought up #36188
  • @stevenkword brought up #20899
  • Both requested additional eyes, and people to test the fixes. Both offered to trade tickets and test.

#4-7, #4-7-4, #community-summit, #core-editor, #core-restapi, #dev-chat, #summary

Planning for Community Summit 2017

In preparation for the 2017 WordPress Community Summit (“CS”) on June 13th-14th before 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. Europe in Paris, France we’ve been asked to provide the following (in summary):

  1. A list of topics for the CS
  2. A list of representatives to attend the CS
  3. One or two contributors who are willing to help with the organization of the CS

This post serves as a request for input for the above three areas. Note that these three requests are detailed further with some clarifying notes on Make/Summit.

I will capture and summarize comments on this post ahead of next week’s CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat, will present them for review in next week’s Core dev chat, and then send our responses back to the Community Summit team by next Friday, March 3rd.

#community-summit

Coming up: 2015 Community Summit

The 2015 community summit is next Wednesday and Thursday, December 2–3. There were a lot of great discussions last year, and I look forward to more this year and planning next steps for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Ahead of the community summit, the lead developers and committers are getting together to discuss a few overarching ideas, including project vision, core features (existing and future), code and contributor infrastructures, and the competitive landscape. The goal isn’t to dictate what comes next for WordPress. It’s unlikely that 20 fiercely independent and stubborn minds would come to a deep agreement in just two days, anyway. 😄 Rather, this initial smaller meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. will aim to bring some specific ideas to the community summit to encourage productive, focused workshopping and tangible outcomes.

Unconference Day

The first day of the community summit is an “unconference” day, where topics are proposed and discussed by groups. This day is meant for in-person interaction and a chance to talk through things that may be more sensitive or controversial. Like previous community summits, only session note takers should be using electronics. We all need to be able to feel comfortable having frank discussions without worrying about quotes or other snippets being posted publicly without context.

Topics will be wide-ranging and not necessarily focused on core; any attendee can participate in any topic. If you’re an attendee, you can suggest topics ahead of time in the community summit forum. Some additional topics may be collated from the committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. meetup. Here are the notes from the 2012 summit and the CSS roadmap that came from the 2014 summit as examples.

There will be four 50-minute session slots and 8 group seating areas, with the possibility of doing smaller breakout groups on a related topic (e.g. component roadmaps) during a session. Each unconference session should produce notes and at least one action item. At least a few of those action items should be things that can be worked on the next day. Notes for core-related conversations will then be edited and posted here on Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./Core in the weeks that follow.

Work Day

The second day of the community summit is a work day. Here, we have two blocks totaling about six hours to fill, from 9:15 a.m. to 12:00 noon and from 1:30 p.m. to 4:40 p.m.

Action items for the work day may include:

What’s on your mind?

What things do you think we should discuss and work on at the community summit? Be sure to propose unconference topics on the community summit forum. Mention any potential work day items in the comments below, keeping in mind that it is six short hours with a limited number of people.

#community-summit

Core CSS: A potential roadmap to sanity

At the community summit, we discussed a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. roadmap, initially a discussion about preprocessors in regard to their role in WordPress, both in the adminadmin (and super admin) and in bundled themes. Recently, there has been significant discussion about the initial use of a preprocessor in the development of Twenty Fifteen that was not included when it landed in core. We discussed what role preprocessors may play with our default theme development and core WordPress for the long term.

In this post, you will find some history, some observations, and an outline of where we can go next to bring some sanity to our admin CSS as well as move into the future.

Continue reading

#community-summit, #css, #roadmaps, #ui

Apparently not all contributors follow the official wordpress…

Apparently not all contributors follow the official wordpress.org announcement blog. A) That’s crazy. B) If you’re one of those people you missed https://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/ and should go read it now. I’m leaving open the nomination/application form an extra day for the people who missed it.

#community-summit