Dev Chat Agenda: January 16th

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Do you like devchat? I like devchat. This is the agenda for the weekly devchat meeting on Wednesday, January 16 2019 at 2100 UTC:

WordPress Leadership is expanding! @chanthaboune and @joostdevalk are excellent people, wonderful contributors for whom I have immense respect, and it’s exciting to see WordPress maturing as an organisation. 🙂
5.1 updates:
- There’s a new schedule update.
- Call for triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.: there are two reports you can help work through: un-milestoned issues, and open bugs.
- Dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. status report.
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ documentation update.
Updates from focus leads and component maintainers.
Open floor.

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress 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/..

#5-1, #agenda, #core, #dev-chat

Andrea Fercia 11:54 am on January 16, 2019

I’d like to propose to briefly discuss during open floor the WordPress Post & Comment Guidelines, specifically to kindly remind everyone is invited to follow a few recommendations when posting on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site), including (the parts in bold are from the original post):
The make/core blog is the official voice of the core team. As a result, you should keep your personal thoughts out of the body of the post, leaving them for the comments. Furthermore, first person pronouns should be avoided.
Similarly, the word “we” should be avoided in posts, unless its made very clear which group is speaking.

Thank you.
- Josepha 7:40 pm on January 16, 2019
  
  Just to check my understanding, are you referring to the use of we in the post above in particular, or are you feeling that there is widespread disregard for that standard?
  - Andrea Fercia 8:09 pm on January 16, 2019
    
    I’m referring to a growing recent trend I’m seeing in the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. posts related to the use of first person “I”. The use of “We” without specifying the related group is relevant as well.
- Darren Ethier (nerrad) 4:03 pm on January 17, 2019
  
  Just as a followup to this comment by @afercia and in light of the related conversation that happened in the devchat, I think its super important to acknowledge that if there are documented guidelines/standards for a project, they should be applied consistently. If not, this can inadvertently communicate that there are different “tiers” of people in the project: those that can disregard guidelines/standards, and those who can’t. While I definitely don’t think that’s intended, perceptions are king, and right now WordPress suffers from (imo) too much avoidable perception problems.
  
  This does not mean that standards/guidelines shouldn’t be revisited or can’t change. In fact I personally agree with @pento‘s comments in devchat that the current standards can result in rather sterile posts on the “make” sites. But until they are changed they should be followed.
  
  While having guidelines/standards are useful, what we see happening here is a good example of the need to be careful of what is adopted unless there’s willingness to enforce or apply them. If there’s unwillingness to do so, then that’s probably a good indicator they shouldn’t have been in place to begin with (and that they need changed).
Josepha 3:28 pm on January 16, 2019

I think this update is probably worth a mention in chat today: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/releases/tag/2.0.0
Andrea Fercia 8:10 pm on January 16, 2019

I’d also like to propose, time permitting, to briefly discuss a proposal for a minor change to the CSSCSS Cascading Style Sheets. coding standard. It was quickly discussed with @netweb on 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/., see https://wordpress.slack.com/archives/C02RQBWTW/p1547204965120600

Comments are closed.

Welcome!

Communication

Share this: