In the better late than never category notes…

In the better late than never category: notes about plugins from core team meetup in December! https://make.wordpress.org/plugins/2012/08/18/93/

#wptybee, #meetup, #plugins

Core Team Meetup Recap – Part II

Picking up where we left off….

Friday

We kicked off Friday with a discussion about the high-level roadmap for 2012. Using our earlier talk about process and scope, we identified areas/userflows that we could use to focus a release. Areas of interest included changing themes/customizing your site, uploading a bunch of photos, interacting with audience/feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.. (There were more, but let’s face it, there are too many things we’d like to improve to do them all at once.)

We all donned WordPress gear so that people would recognize us at the happy hour later.

Dion

Dion (dd32) modeling the latest swag

Dion and Andrew

Dion and Andrew Ozz before lunch

Lunch: Went to The Sentient Bean in Savannah.

The Sentient Bean

The Sentient Bean

Back patio at the Sentient Bean

Back patio at the Sentient Bean

Koop and Mark, Dion and Ozz in the background

Koop and Mark, Dion and Ozz in the background

Next we went to ThincSavannah, my coworking space in downtown Savannah. We did the livestreamed Town Hall/Q&A (recording coming soon), answering questions from that forum thread I put up last week and a few that came in live from 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..

Core team town hall video screen cap

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team town hall

After that was happy hour at Jazz’d. Only two people came to hang out with us (and to think we dressed up especially!), but they were two great people, so we were fine. Some drinks and appetizers later, we departed for WordPress on Ice, in which we went ice skating at the Civic Center.

Nacin and Koop on skates

Nacin and Koop on skates

Nacin, Mark, Jane, Matt, Jon, Daryl

WordPress on Ice! Nacin, Mark, Jane, Matt, Jon, Daryl

Then a stop at Huc-a-Poo’s, then home.

Saturday

We spent the morning talking about mobile apps and their place in the WordPress ecosystem, as well as making the dashboard a better experience when viewed in a mobile browser.

Lunch: Went to AJ’s and ate on the deck. Continued talking about mobile. This eventually morphed a bit into a discussion about the lines between .org/.com.

Core team at lunch at AJ's Dockside

Core team at lunch at AJ's Dockside

After lunch we talked about the default theme for 2012, including what it should do/be that our current themes don’t already accomplish, and the process for its creation. Breakouts followed. One was focused on 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, while the other was focused on hosting/diagnostics/health check. We tested doing a Google Hangout with screensharing as a way to collaborate more effectively throughout the year, and agreed we would try to do them once a month. For dinner we got takeout BBQ from Gerald’s Pig & Shrimp. We pretended @ryan was with us by playing a video of him from last year’s 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.. Afterward, Koop gave a primer on 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/..

Sunday

When we started this morning, we tried to at least quickly hit the things we hadn’t gotten to yet, since today was the last day. These included: Google stuff, core plugins, how leadership in core does/does not translate to leadership of the whole project, 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/ site, pairs (creating process to make collaborative/non-solo development the norm), and CMS stuff.

Since a lot of us were pretty interested in making the theme customization process a focus of the next release, we starting identifying what the chunks of that might look like under the new process and with people working in pairs/teams. We continued talking about this over brunch at the Tybee Island Social Club, where @nacin and @dkoopersmith drank bacon bloody marys.

Bacon Bloody Mary

Bacon Bloody Mary

Nacin attempting to consume a bacon bloody mary

Should Nacin eat the bacon or drink the bloody mary? He can't decide.

After brunch, @markjaquith and @dd32 left for the airport, and @joncave and @azaozz left two hours later. Bye bye, core team!

Now we begin a 2nd mini meetup. Matt, Nacin, Koop, and I are staying, and have been joined by @otto42 and @chexee. The next couple of days we’ll be doing some planning and starting projects to make visiting wordpress.org a better, more useful experience. Â Tonight, though, everyone is catching up on some individual work after a week of long days.

We’ll post summaries of the specific core meetup discussions over the coming week.

#wptybee, #core-team-meetup

Core Team Meetup Recap – Part I

As most people know, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team (leads, primary committers, Matt) is having its annual 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. this week, packed into a house in Tybee Island, GA with an hour by hour schedule to try to get through as many things as we can. We’ll try to do recaps of everything we talk about to keep everyone in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. (feel free to ask questions in the comments).

Monday/Tuesday

Matt, Mark Jaquith, Westi and I arrived (well, they arrived; I live here) on Monday and had a day to plan out the agenda topics and work out how we wanted to schedule the week. Â Rather than plot out a unique schedule every day, we put together a repeatable pattern for morning and afternoon that looked like this:

Schedule chart

For the record, “Break” means “Check email, catch up on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets, etc,” not, “Hang out on the couch watching Hulu.”

On Tuesday we also took a field trip to buy a cable modem capable of handling the bandwidth increase we’d ordered. That night, everyone else arrived: Nacin, Koop, Dion (dd32), Andrew (azaozz), and Jon (duck_). We had dinner at the Crab Shack and planned an early start on Wednesday.

Wednesday

Wednesday was our first day as a full group. We followed the schedule fairly well, though as always with us, some things took longer than expected. 🙂

Breakfast: We went to eat at the Breakfast Club, where a bunch of the guys had Blackhawk burritos in honor of our absent member, Ryan Boren.

Our first main topic was a 3.3 debrief to discuss for about 45 minutes how the 3.3 development cycle went. (Going to split out the notes from these sessions into separate posts, or this post will be a mile long.)

After that we had breakout sessions, where the intention was for smaller groups to brainstorm/discuss an issue, then come up with a proposal/recommendation to present to the group. The two topics were QA and Updates (specifically the road to auto-updating and how we could get there). Mark assigned people to each session and half the group went upstairs. Coincidentally, that was the UPdates group. (sorry) Afterward, we regrouped and caught each other up on our proposals.

Lunch: Blackhawk burritos keep you full for days, so people just made sandwiches.

Round 2 started bringing in @ryan via Skype video from his home in Texas. The main discussion centered on our development cycle/release process/scoping/timelines. We discussed a number of things we could try to keep the cycles more consistent, reduce bottlenecks, and improve accountability.

Dinner: It was my birthday, so we all went to the Tybee Island Social Club for “Winesday” and continued our talks about everything from the 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/ site to growing local developer and user communities. There may be a picture of Koop and/or Nacin wearing a child’s birthday hat. Mark Jaquith has the footage.

Thursday

Breakfast: Miscellaneous breakfast stuff at the house. Pretty sure there was a bunch of bacon involved.

Morning session: Plugins, plugins, plugins. You name it, we talked about it. Findability in the directory, improving the repo and developer experience, 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 review, encouraging collaboration, 3rd party repos, communication with authors, and more.

Both breakout sessions were plugin-centric. In addition to general recommendations, each subteam was required to identify two discrete action items to help us move forward in their assigned area. One subteam (Me, Westi, Jon Cave, Andrew Ozz) was focused on planning upcoming wordpress.org sites in the Make and Learn areas, while the other (Matt, Nacin, Koop, Dion, Mark) focused on improving the directory.

This day we did an actual fun outing to get us out of our chairs and away from the laptops for a bit, and went out on a boat for an hour so the guys could get a tour of the river/marsh and hit the ocean as we looped past the Cockspur Lighthouse.

Core team, on a boat

Dion (dd32) and Matt

Mark and his lens

Koop

Matt and Cockspur Lighthouse, Tybee Island

After the boat, we went to lunch at North Beach Grill. There were conversations about infrastructure, performance, automated testing, and crawfish poppers. Before going back to the house, we did a 5-minute walk down to the water.

Westi on the beach

In the afternoon, rather than doing another blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. of heavy discussions, everyone worked on their computers. Some of you may have had some issues accessing svn etc last night, and so did we. So that took a while. After that it was general hackery and miscellaneous discussions about functions, bugs, and the usual things wp devs talk about when they are together. This lasted into the evening, so instead of going out to dinner we ordered pizza from Huc-a-Poo’s and kept working.

Friday

Today we’re having a modified schedule because Westi leaves to go home this evening, so we’re trying to get certain things finished before he leaves. We’ll be working this afternoon from a coworking space in downtown Savannah, and will be recording video responses to some of the questions on the forum thread I posted last week. If bandwidth supports it, we’ll livestream this while we record, and could possibly take more questions from people in #wordpress-dev. If we do it, we’ll use the Ustream “WordPress” user channel, and it will be mid-afternoon eastern time (maybe around 3pm?). Once we get there after lunch and can tell if the livestreaming will work, I’ll post on this blogblog (versus network, site) with the verdict.

Off to Friday’s sessions! We’ll start posting the session writeups as time allows, but will get them all up there no later than the end of next week (there are a lot of notes).

#wptybee, #meetup, #planning

#wptybee update! Thursday – The core com…

#wptybee update!

Thursday

  • The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. commit team (+me) talked with the people working on the WordPress mobile apps via audio skype chat after several attempts at video were an utter failure due to bandwidth issues. All agreed that we needed to build a stronger tie between the web app and the mobile apps. To that end, the mobile app devs will start attending our weekly dev chats to stay up to date with new developments (heh), and will occasionally post updates here on this blogblog (versus network, site) to keep everyone aware of mobile app news. We’ll also get the UIUI User interface group involved in mobile app UI/usability testing where appropriate. A link has been added to the Extend submenu on .org that goes to a page listing all the mobile apps and their sites, to raise visibility.
  • Huge Tracfest. Sifted through awaiting review and future release tickets, talked about ways that we could improve the triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./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. gardening process. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.-ity Trac-ity Trac-ity.
  • BBQ dinner brought over by Gerald of Gerald’s Pig and Shrimp BBQ (though there was no shrimp). His business is closed for the season and he doesn’t usually cook for such small groups in the off-season, but he let himself be sweet-talked into it because he has a WordPress blog. Running Kubrick! He came over with a truck full of meat, black eyed peas, lima beans, rice, and fried okra. It fortified the guys for…
  • All-night continuation of Tracfest.

Friday

  • We started out the day by talking about ways to improve the 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 repo submission experience, possible ways to promote good/safe plugins and de-emphasize abandoned ones that no longer work with current version, and infrastructure that could help with these goals. We also had a knock-down, drag-out fight over the best way to deal with plugins whose authors have abandoned them if someone else wants to step up to take over. I say this not to imply there is dissension in the ranks of the core leadership, but to show that this is a group of passionate people with strong opinions about the best way to do things to further the WP project. If you’ve ever been bummed because half the core team didn’t agree with you and shot down your idea, at least take heart that we’re all in the same boat! 🙂
  • Licensing. We committed to reviewed every licensing ticketticket Created for both bug reports and feature development on the bug tracker. opened by hakre or anyone else on Trac. We got through all of them, and wound up with a list of what to do about them/assigning people to make whatever patches were deemed necessary. Also see Mark’s post from last night, related to one of them.
  • Improving updates. Talked about things like partial updates, language packs, compatibility checks, notifications, memory leaks, etc.
  • Unit tests. We need more stuff. Also, Peter is going to write up Mac and Windows instructions for getting the test suite running.
  • Tracfest.
  • Lost time to tangents not directly related to either 3.1 release or the topics on the agenda for 2011 vision due to vocal minority/people who are convinced that their needs are more important than anyone else’s. I’m supposed to be savvy enough not to come right out and say things like that, but it’s been a long week, and lets face it: if half the core team didn’t lose so much time to the handful of people who loudly demand attention on wp-hackers, twitter, etc, we probably could have had 3.1 launched by now.
  • Regained better humor (lowered due to said time suck of tangents) by invading ##wpchat and being silly. Sorry guys, for the interruption. At least our bandwidth was bad enough that we weren’t there for long! 🙂

Saturday

We have a long list of things to get through today. May try to enforce a period of social media silence and make everyone close twitter etc so we can’t be distracted as outlined above. If we don’t answer you about something today, please don’t be offended — we just really need to get a lot of work done, and we only have one day left to do it.

In the meantime, since the internet connection has made doing a live town hall impossible, we could at least try to record one and post it. Feel free to post questions you’d like us to answer on video in the comments. You can ask of the general team, or ask someone specifically (people here include Matt M, Ryan Boren, Mark Jaquith, Peter Westwood, Dion Hulse (dd32), Andrew Nacin, Daryl Koopersmith, Pete Mall, Austin Matzko (filosofo), Mike Adams (mdawaffe), John Ford (aldenta), John James Jacoby (jjj) and me).

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.

Bulk action issues are somewhat outlined…

Bulk action issues are somewhat outlined in #16166 #16031 #16187. We’ve been able to group the issues into four problems.

Four problems needing solving:

Problem 1. 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 3.1. Custom Bulk Actions don’t have action handlers. Even if they existed, developers would need to know that they need to call WP_List_Table::add_query_args() before wp_redirect. We need a way for this to be pluggable without burdening developers on redirecting (plus with their own query args).

Problem 2. Fixed. We need a sanity check for max pages. This is #16187. Basically, this needs to be applied to any other appropriate list tables. Most major ones (posts, comments, media) are handled though.

Problem 3. Bulk Actions reset the sorting and paging. This is fixed in #16166 (posts, terms, comments, media) but we need to apply this to the other list tables.

Problem 4. Post restriction filters — categories and dates, for example, but really anything added through restrict_manage_posts — are reset after a bulk action the same way sorting and paging are. This can be added into add_query_args().

The plan at the 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. here is to break on all of this, and revisit later.

#wptybee, #trac

We talked about doing a town hall/q&a du…

We talked about doing a town hall/q&a during dev chat time this week since most of the permanent coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team are at the 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. in Tybee. However, we said that with the assumption that 3.1 would be in RC3 already, and that we’d have had 3 days together to begin talking about 2011 and the goals for WP. Instead, weather-related travel delays meant that people were arriving right up until tonight, and Austin still hasn’t arrived. RC3 hasn’t happened yet, and we haven’t started talking vision because we need to get 3.1 out the door. So!

We’ll still give the live stream a shot (barring technical difficulties), but it will instead simply be “dev chat live” — only of interest to people who normally attend the dev chat. We’ll plan something in the town hall/q&a line later in the week.

To get to the live dev chat, go to http://www.ustream.tv/channel/dev-chat-live at the appropriate time and you’ll get the chance to see the lead devs and friends in action. And yes, by friends I mean their beards. 🙂

Agenda: 3.1, 3.1, 3.1, 3.1, 3.1.

#wptybee, #agenda, #dev-chat