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


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 — Enable install in subdirectory so you can use externals.

#core-team-meetup, #multisite

Core Team Meetup Recap – Part II

#wptybee, #core-team-meetup