Suggest agenda items for today’s developer chat

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.

TobiasBg 5:50 pm on August 22, 2012
- Is new jQuery 1.8 and UIUI User interface ready to go in?
- How can plugins already use and benefit from the new WP_Post class? (not really a chat agenda item, but more a suggestion for a small post here)
- Ryan Boren 6:31 pm on August 22, 2012
  
  https://core.trac.wordpress.org/ticket/21532 jQuery 1.8
  https://core.trac.wordpress.org/ticket/21309 WP_Post
Andrew Nacin 6:08 pm on August 22, 2012
- We need final testing and a green light on the two 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 tasks, #19235 and #19796.
- 3.5 status check.
- Review 3.4.x tickets.
https://core.trac.wordpress.org/ticketgraph?days=1011 — that’s starting at the first day I contributed. I’ve been talking to bpetty about things we can do to combat this. I’d like to revive some old ideas like people being responsible for specific components. Not default owners, but individuals and teams overseeing a component to allow for better triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of tickets. Also, we have not assigned new 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. gardeners in a while, so we should see if that list should be updated with some new names.

I may miss the very start of the meeting, in which case @koopersmith will kick it off.
Andrew Nacin 6:18 pm on August 22, 2012

Good overview of outstanding UIUI User interface/UXUX User experience/design tickets for 3.5: https://make.wordpress.org/ui/2012/08/22/ticket-scrub-notes-for-8-21-patch-needed/
Andrew Nacin 6:28 pm on August 22, 2012
- Discuss filters in _option() functions when switched. @ryan will lead this one.
- Ryan Boren 6:31 pm on August 22, 2012
  
  https://core.trac.wordpress.org/ticket/21459
camu 11:19 pm on August 22, 2012

Maybe https://core.trac.wordpress.org/ticket/18694 ?
GrahamArmfield 7:25 am on August 23, 2012

https://core.trac.wordpress.org/ticket/21289 – in my view another key 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) issue that doesn’t seem to be getting any attention at the moment.
- Andrew Nacin 5:21 pm on August 31, 2012
  
  @GrahamArmfield I agree — this might get the right attention it needs if it is discussed during a #wordpress-ui meeting or 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. scrub, https://make.wordpress.org/ui/.
ahmu83 2:05 am on August 24, 2012

I dont know if this is the right platform to say this. Is there any possibility for wordpress to introduces blocks feature and php input feature in upcoming version?
- Andrew Nacin 5:19 pm on August 31, 2012
  
  Hi there — not sure what you mean by either of these.
niklasbr 9:51 am on August 24, 2012

Can people from the outside suggest issues for dev chats?
- Andrew Nacin 5:17 pm on August 31, 2012
  Sure, though a few things to keep in mind:
  - If you’re going to suggest something to discuss, you should probably be there. 🙂
  - If you don’t regularly follow the dev chats, I would do this to get a hang for how they work, and propose the topic for a future chat (unless it is timely or time-sensitive).
  - Feel free to talk to any of us in IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. at any time. Not everything is worth talking about during a dev chat, but that doesn’t mean you can’t engage any of us. Individual 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. reports, for example, are worthy of discussion but unless there is a major disagreement among coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developers, or a big decision to make, we probably won’t put that on the agenda for a dev chat.
Tom Lynch 9:39 pm on August 26, 2012

Looking to see if anyone is interested on working on #18285 it’s a big’n but a good’n!
helloari 10:49 pm on August 26, 2012

not sure if this is the right place to put this: small feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged.: in the update page (/wp-adminadmin (and super admin)/update-core.php) make note of which plugins are active and which are inactive. that way a user can update the inactive ones and be confident it will not break their site.
- Andrew Nacin 5:29 pm on August 31, 2012
  
  You’re welcome to propose this on http://core.trac.wordpress.org. I think it has been discussed before as well. I think part of the problem is that a change like this might have the opposite effect. That a user doesn’t update the inactive ones because they’re inactive.

Comments are closed.

Welcome!

Communication

Share this: