WordPress 3.7 organization

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.

With WordPress 3.7 and 3.8, we’re a project in major transition. Version 3.7 aims to solve for a lot of things that are weighing us down. (See the initial kickoff post.) What do you want to do? In terms of process, here is what is being worked on for 3.7:

Processes, Tools, Workflows

New development tools — develop.svn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ — run by @koop. If you are interested in Grunt, unit testing (including JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. testing), and how we can streamline and modernize our workflows, this is for you.
Code reference — inline documentation efforts — run by @rzen, @ericlewis, and @drewapicture. If you are interested in inline documentation, this is for you. See this post to get started.
Process changes (including improvements to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and how we organize around components). If you want to write some Python for Trac, this is for you. If you’re just interested in helping with component reorganization, stay tuned here — there will be a post soon outlining a new component tree.

Security, Stability, and Updates

We have a few other focuses that all deal with a general theme of security and stability.

Passwords. We are aiming to improve the adoption of best security practices by assisting with password generation. #24633. @duck_ is also working on some changes to strengthen cookies. #20276. If you are interested in security, this is for you.
Updates. @dd32 and @pento will be heading up automatic updates for minor releases, as well as improving the trustworthiness of our upgrader. If you love updates and stability, this is for you.
Language packs. We need to separate language files from plugins, themes, and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., allowing them to be maintained and updated independently (and, ideally, automatically). #18200. If you want to help WordPress’ global reach, hook up with me, @dd32, and @markoheijnen.

General Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

Finally, we have ~~3,800~~ (already only 3,600) open tickets on Trac. There are dozens of components with many, many tickets. Already, there have been a few components with a strong base of contributors working on them, including:

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, currently being smashed by @jeremyfelt and others. If you like multisite and want to make it better and more stable, this is for you. There are currently 122 open tickets.
JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.. A number of you have expressed interest on working on JavaScript in core. Whether that is shoring up the stability of existing features, improving existing JS, or working on a JS testing framework, this should be a great working group. @carldanley, @adamsilverstein, @nbachiyski, @kadamwhite, and others expressed interest.
Query and TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.. These two advanced areas of core kind of go hand-in-hand, not in the least because @wonderboymusic smashes query tickets with his left hand and taxonomy tickets with his right. If you’re interested in bringing down these tickets (68 and 93 open), this is for you.
General triage. Folks like @c3mdigital and @avryl have been already going through old tickets either closing them out or finding diamonds in the rough. Or maybe you find that one of the many open components catches your interest. (Go here and choose any component from the drop-down to see all open tickets.) We’ll be coordinating efforts to work together both 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. (especially during the weekly meetings) and here on make/core.
Components with a lot of open tickets: General (376 tickets), Administration (302 tickets), Media (221 tickets), Template (161 tickets), Comments (135 tickets), Users (107 tickets), Themes (105 tickets), Formatting (98 tickets), Menus (96 tickets), Widgets (90 tickets), Plugins (90 tickets), Editor (85 tickets), Upgrade/Install (84 tickets), Import (70 tickets). If you want to do general triage, General and Administration in particular need a lot of work!

Today during the weekly meeting, we’ll be talking about ongoing efforts, rallying the troops and helping to assemble working groups, and setting up some times for regular triage meetings.

So, what do you want to work on? Let’s start coordinating in the comments.

#3-7

WraithKenny 7:49 pm on August 14, 2013

I’m interested in “New Development Tools” and JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. I’ll help as much as time permits and see if I can get a coworker to help out too.
MartyThornley 7:51 pm on August 14, 2013

I’m always up for 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. Just submitted a revised 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. for https://core.trac.wordpress.org/ticket/20774, based on feedback and taking a look now to see what else I might be able to jump on.
George Stephanis 8:00 pm on August 14, 2013

I take it coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. won’t be getting two-factor authentication in 3.7, then?
- Bryan Petty 9:23 pm on August 14, 2013
  
  I don’t think this was ever even being considered for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. regardless of version.
nofearinc 8:07 pm on August 14, 2013

I would like to work in “Updates” and help in General and Administration.
Konstantin Obenland 8:10 pm on August 14, 2013

I’d like to help clean up the themes component. I started with pushing some tickets to the 3.7 milestone and I think there are some quick wins there.
- Andrew Nacin 3:03 am on August 15, 2013
  
  Let’s also close out as many tickets as possible. 🙂
K.Adam White 8:30 pm on August 14, 2013

I’m guilty as charged: JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.! I’d love to have a conversation in #wordpress-dev to discuss the JavaScript changes. I know @carldanley has begun to work on some proposals; it should be a lively conversation!
Mike Schroder 10:01 pm on August 14, 2013

I’d like to help with “Updates”!

Otherwise, I’m likely just to spend some time triaging tickets, likely mostly in the ‘media’ component. Another project needs assistance? Let me know!
lucasstark 10:16 pm on August 14, 2013

Regarding Process. Is there any way we could flag and filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. tickets that are “pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party territory”.
- Andrew Nacin 3:00 am on August 15, 2013
  
  Good question. I think we’d hesitate to add yet another resolution. We have pretty much always used “wontfixwontfix A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion.” for this — as in, we are acknowledging the ticketticket Created for both bug reports and feature development on the bug tracker. is valid, but we’re declining to address it.
  
  By all means, feel free to close ‘pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party territory’ tickets with a comment stating such!
Ryan McCue 3:57 am on August 15, 2013

Development tools, process, passwords and updates sound good to me (and of course, background work on the code reference as needed). Process and tooling will probably be the main ones for me given time constraints (Python’s always fun).
Travis Northcutt 12:47 pm on August 15, 2013

Is there any reason to think that a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party that prevents WP from sending passwords in plaintext, and instead requires a new user to set their own password, would be a good idea?

I don’t know enough to know the specifics of how that would work internally, but it’s something that interests me.
- MartyThornley 5:04 pm on August 15, 2013
  
  There is one out there – http://premium.wpmudev.org/project/set-password-on-wordpress-mu-blog-creation/ I have it if you want to take a look.
Nashwan Doaqan 5:31 pm on August 15, 2013

I am really want to help with Language packs, this will save my life !
Mustafa Uysal 12:45 pm on August 16, 2013

I’d like to help language packs.
doughamlin 4:00 pm on August 19, 2013

Are the two items listed above for passwords the only things being worked on? I think it’d be smart to see both limited login attempts (probably not technically password-related) and strong password enforcement built into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..