Please suggest agenda items for the weekly developer…

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.

Please suggest agenda items for the weekly developer meeting, Wednesday, February 5, 21:00 UTC.

If there’s a task or ticketticket Created for both bug reports and feature development on the bug tracker. we need to work through, or need volunteers for, let’s get those spelled out now. Maybe we can even work through some of them pre-meeting.

I’ll again be asking for a sentence or two (or more, if necessary of course) from each person/team working on a 3.9 task. You can also post those here if you’d like — please cross-reference any relevant tickets or discussions. Worked out great last week. For the state of things as of last week, see Mike’s weekly roundup.

#3-9, #agenda

Pippin Williamson 4:05 am on February 5, 2014

Not sure if there’s much discussion needed on them, but I’d love to see the remove/has_image_size() tickets shored up:

https://core.trac.wordpress.org/ticket/26768
https://core.trac.wordpress.org/ticket/26951
- Pippin Williamson 4:07 am on February 5, 2014
  
  Not to push more of my own tickets/patches, but it’d be great to get another set of eyes on the new password generation flow (originally slated for 3.8): https://core.trac.wordpress.org/ticket/24633
- Andrew Nacin 8:55 pm on February 5, 2014
  
  Will commit the first two for sure. Would be good to mention the third one, passwords. I can touch on it at the meeting — really what I need to do is type up some notes from when @markjaquith and I discussed it last. I can do that this week.
Jeremy Felt 4:19 am on February 5, 2014

I’d like to chat a bit about the direction of domain routing. I’ll be around pre-meeting as well.

I opened #27003 last night with 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 introduces `wp_get_network()` as a way to retrieve a networknetwork (versus site, blog) by it’s domain and path. This isn’t an absolutely necessary abstraction from `wpmu_current_site()`, but it does remove the functionality away from the `$current_site` global and focuses on retrieving just the requested information. In the process, `wpmu_current_site()` gets cleaned up quite a bit. It should be pretty straight forward to write unit tests that cover `wp_get_network()`.

IMO, this is a first step toward cleaning up a bit of the load process. If we’re good with this direction, the next step will be to do the same thing for site discovery ($wpdb->blogs). I have more notes written up here on the multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site load process in general for anyone that wants an overview of how things are working.
Pippin Williamson 5:17 am on February 5, 2014

I’ll throw out another one. I’d LOVE to see further discussion on better custom comment types, per https://core.trac.wordpress.org/ticket/12668
Weston Ruter 8:14 am on February 5, 2014

There was a really good discussion today on #wordpress-dev regarding feedback for WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. 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.. So I think we have a path forward for important issues to address. I’ve created a milestone on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ to track these issues: https://github.com/x-team/wp-widget-customizer/issues?milestone=4&state=open
Robert Chapin 11:27 am on February 5, 2014

3.9-early tickets, please
Manuel Schmalstieg 12:49 pm on February 5, 2014

For international users, improving the handling of accents/diacritics in file attachments would be a big win: https://core.trac.wordpress.org/ticket/22363 – the ticketticket Created for both bug reports and feature development on the bug tracker. has patches, and @markoheijnen has proposed it for 3.9 …
Tom Auger 7:59 pm on February 5, 2014

I’d like to discuss https://core.trac.wordpress.org/ticket/21811 and see if my 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. / suggestions are salvageable, given the much bigger development effort around the entire Media Modal. The feature I was working on (prior to the whole Media Modal overhaul) was a very small, targeted, incremental enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that was kinda “shoehorned” in under that tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., but really addresses something different and much smaller in scope.
Tom Auger 8:37 pm on February 5, 2014

Update: I see @gcorne has done some great work demonstrating how this could get integrated into Media Modal. I’ll continue this week and see if I can bring these things together. As for today’s meeting – we just got massively dumped on in Toronto, so I’ma head out of the office now and may not get back online in time to catch this week’s meeting.

Comments are closed.

Welcome!

Communication

Share this: