Dev Chat Agenda, January 28, 2015

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.

Here’s the agenda for Wednesday’s Dev Chat in the #core channel on Slack.

Time/Date: January 28 2015 21:00 UTC:

Kickoff Part II – Let’s talk a little bit about how we’re going to structure this release from week to week:
- Monday Jumpstart posts
- Bug scrubs
- Ticketticket Created for both bug reports and feature development on the bug tracker. management
- Mentoring
#5809 – Term splitting update (@boonebgorges)
Feature Plugins – Status updates from the three feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. leads:
1. CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. Theme Switcher – @celloexpressions
2. Press This revamp – @michael-arestad
3. Shiny Updates – @pento
WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Weekly – @dh-shredder is looking for help with compiling the weekly activity roundup
AccessibilityAccessibility 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) – Introduce the weekly hitlist and talk about accessibility priorities for 4.2
Mobile – make-flow tickets from @boren:
- #29906 – Submenus can’t be dismissed on mobile.
- #29989 – Hide Media Buttons on small screens
Open Floor – If you have something you’d like to bring to the table to discuss, leave a note in the comments
- #30937 – Customizer transactions (@westonruter) [proposal]
- Fast-tracking unit tests – @pbearne would like to discuss fast-track committing test for existing code

#4-2, #agenda

Weston Ruter 7:13 am on January 28, 2015

I’d love more thoughts and feedback for CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. transactions: https://make.wordpress.org/core/2015/01/26/customizer-transactions-proposal/

If not concerns, then more green lights and thumbs up.
- Drew Jaynes (DrewAPicture) 7:22 am on January 28, 2015
  
  Added.
Nick Halsey 7:54 am on January 28, 2015

I can’t make the meeting most weeks this semester due to class, but current status is that @sheri and @mikelking are both working on user testing and we’re fixing a few minor issues as they come up. I’m planning on tackling the remaining issues listed in my update post this weekend, and posting another update before our next meeting next Tuesday.

I do read the logs, so I’d appreciate any general feedback that comes up during the meeting, as well as feedback submitted through other mediums.

I’d also like to add to the agenda under Mobile to bring up #28784. Especially as we add more things to the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., we really need to make it more usable on smaller devices. Shouldn’t take nearly as much effort as places like the media modal to make improvements here in 4.2, but we need eyes and patches there. The controls UIUI User interface is already mobile-first, it’s really just a matter of making the controls/preview toggle more intuitive as a toggle here.
Paal Joachim Romdahl 1:16 pm on January 28, 2015

A few open questions that come to mind.

What happened to beginning talks on revamping Settings?

Further along a similar thread…..Any plans on discussions about which areas of priority in the WordPress backend need updating? (Of course this would be a huge discussion but one that is needed.)
Boone Gorges 2:03 pm on January 28, 2015

Splitting shared terms #5809. We’ve got some dev-facing documentation drafted, and will be soliciting feedback in the next few days.
- Scott Kingsley Clark 7:44 pm on January 28, 2015
  
  +1
Paul Bearne 2:11 pm on January 28, 2015

Can we look at workflow where unit tests for existing (working) code can get committed quickly so that we can encourage increasing the test coverage.

I started to write tests for functions.php but have got discouraged as there is no clear way to get a pure unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. commented. I would thought that we should be able to these committed quickly.

Here is couple tickets with mostly test patches but in both cases I found issues and this why I want to see this work done.

https://core.trac.wordpress.org/ticket/28559
https://core.trac.wordpress.org/ticket/29063

We had a big project to get comments for actions / filters doing the same for Unit tests would be good
- Boone Gorges 6:30 pm on January 28, 2015
  
  Paul – Of note, we are no longer committing failing tests; see #30284. So, when creating a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that contains tests, it’s wise to separate out those tests that are currently passing, since only *they* can be committed immediately (and be sure to note this point in your comment when posting the patch).
tohit 4:47 am on February 4, 2015

Hi Drew Jaynes,

How can i join this meeting agendas ?
Please help me to get participate in this.

Thanks
Tohit

Comments are closed.

Welcome!

Communication

Share this:

Site resources