The core team meetup (affectionately ref…

The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. (affectionately referred to as #wptybee) began Sunday night with the arrival of Westi and Otto. Many flight cancellations, re-bookings, and delays on Monday saw the arrival of Mark Jaquith, Pete Mall, Andrew Nacin, Matt, Ryan Boren, J-trip, and Daryl. Tuesday brought Mike Adams and John Ford, and Dion Hulse arrived in a horse-drawn carriage (read: rental car) driven by Lance Willett. Austin Matzko arrived Wednesday.

• Monday was a travel day. Tacos for dinner, greetings, but not much work on core.
• Tuesday was spent by the lead team trying to figure out wtf was wrong with 3.1 bulk actions so we could put out RC3. It’s still going on. In the evening we had Matt’s surprise party.
• Wednesday was the first real “summit” type day, as Tuesday’s work was very similar to what we do remotely, just with some talking out loud. On Wednesday the 3.1 angst continued, but we also discussed some possibilities for 3.2 (keeping the release small, focusing on easier/better updates, PHP5, etc) and the 2011 theme (build on what is awesome about 2010, possibly add a template or two to make it more attractive for CMS use, maybe rotating headers?), and there was a group Tracfest at night over pizza and beer. This included discussion of how we might better section off tickets for: 1. Things we already know we want in the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., 2. Things we like the idea of, but won’t target for a specific release until there’s a good 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 it (as opposed to deciding we want it in the next release before writing the patch), 3. Things we’re interested in personally, but would like to see as 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 first to evaluate and/or test if it’s really necessary for core (we want to start doing this a lot more). More discussion likely to ensue on that 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..
• Today we’ll be having a chat with the mobile team to discuss how the two groups can collaborate so there’s more continuity in the WordPress experience, how to leverage the quite-big WP community to increase participation in the quite-small mobile apps project communities, and in general how to make the mobile apps an integral part of the WordPress experience and community. No more red-headed stepchildren!

Hoping for more TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. today — the goal is to empty awaiting review and future release by end of meetup (possibly not realistic given late arrivals, birthday time-out, hangovers, etc) and get everything looked at and put into a more specific milestone — and some of the higher-level vision talk we originally intended for the meetup when we planned it (thinking it would be 3 weeks after the release of 3.1). Will post additional updates as we continue.