WCSF Tickets, Meetup Info

Anyone planning to attend WCSF this year from the core team, please read the post at https://make.wordpress.org/updates/2014/09/08/wcsf-tickets-and-stuff/ for information about WCSF ticket sales and the contributor days following the main conference. Thanks!

P.S. If you are planning to attend the core team meetup but I have not been in touch with you regarding hotels, please ping me in IRC (jenmylo) or shoot me an email (same username @wordpress.org) so I can include you in the planning. If we have talked in general but you haven’t actually booked anything, don’t freak out — we have a spot on hold for you and you’ll be able to book it this week when we send out the booking codes.

#core-team-meetup, #wcsf2014

WCSF 2014: Are You Coming?

Heads up, core team! We’re getting ready to publish details about the plans for WordCamp this October (which includes a mini team meetup), so if you’re thinking of attending, please read the post at https://make.wordpress.org/updates/2014/06/12/wordcamp-san-francisco-travel-contributor-days/ and take the short survey linked at the end of it so I’ll know how many team members to plan for (don’t worry, this isn’t a commitment or anything, I just need to get some rough numbers for budgeting purposes). Thanks!

#core-team-meetup, #wcsf, #wcsf2014

Core Team Meetup Recap: Multisite

These are the notes from a breakout discussion on multisite at the core meetup with me, @markjaquith, and @nacin. As with all of these discussion summaries, please remember that they’re just discussions. I’m posting the notes for transparency purposes, not to say that these are the only things discussed or decided. I’m working from notes, and sometimes you don’t get everything down when you’re taking notes (next year I’ll record these things instead).

Multisite!

Who can lead this joint? Since the merge and Donncha moving on to other things, we had Ron for a cycle, Pete for a cycle, then no one. It would be good to have someone act as component owner.

Multisite needs parity with the single site experience. Includes UI, UX, copy/strings, install flexibility (subdomain etc), installation ease (add a site).

First we need to improve the manage/use experience, then fix install stuff and get it into the dashboard to turn on multisite.

We need a useful global dashboard.

We need to have flexibility in where sites and networks live — should be able to live wherever you want on one network. Subdomains/subdirectories/mapping/whatever you want, mixed subdomain/subdirectory, custom domains, global permalink consumer/router.

Need to fix different workflows: adding users to network, adding users to site, invitations. User signup, creation, assignment, invitation all need new flow

We need parity between plugins and themes. Enable vs activation is confusing, need to improve language, indicators. Need ability to network enable but disable for individual sites. Need to standardize network enable/activate etc for plugins/themes. Network activated plugins don’t show in individual site’s plugin list, which is confusing.

UX Action Items:

UX ACTION ITEM — Include network activated plugins in the plugins menu and give message that it is automatically on for the whole network (if admin/have rights to see plugins screen).

UX ACTION ITEM — Autocomplete usernames or site names for network admin and for superadmin everywhere.

UX ACTION ITEM — Get multisite tag/indicator on plugins in directory, add multisite specific/required indicator.

Under the Hood Action Items:

ACTION ITEM — Get rid of MS-FILES.

ACTION ITEM — Enable install in subdirectory so you can use externals.

#core-team-meetup, #multisite

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 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 IRC.

Core team town hall video screen cap

Core 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 multisite, 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 meetup. Afterward, Koop gave a primer on JavaScript.

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.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