Planning for the 2015 Summit

Hey everyone, the Summit is next week, and there are a few things we need to decide on before we get there.

Wednesday – Unconference Discussions

The first day is unconference-style conversations. We need to think about what topics we’d like to discuss, and post them to the forums.

There’s a few there already:

Those are mostly about vision and policy, though, rather than technical implementation. Are there things that are more specific to MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. that we could discussion on Wednesday? Ideas to improve our workflow and tools? Ways to get more contributors involved, and to make the process easier for them? Are there any projects that are stalled and could use a discussion to jumpstart them? etc. Please post your ideas to the forums and +1 the ones you think should be discussed.

Thursday – Work Day

The second day is for working on projects. We need to create an agenda so that we don’t waste time at the Summit, and also figure out what kind of space we’ll need at the venue.


We’ve got two large blocks of time to divide up and fill however we want: 9:15 am – 12:00 pm, and 1:30 pm – 4:40 pm.

What projects do you want to work on? How much time should be devoted to them?

I’m guessing not everyone will want/need to work on each project, so we can have multiple smaller groups working simultaneously if we want.


There’ll be lots of open space where teams will be working most of the time, but there are also a few small, private rooms that we can reserve slots for, if we think we’ll need them.

Does anyone think we’ll need a small private room? If so, for how many people and for how long?


CC’ing everyone who marked Meta on their Summit registration…

@drewapicture, @otto42, @nacin, @atimmer, @chriscct7, @dd32, @pento, @jenmylo, @joedolson, @johnjamesjacoby, @jorbin, @ryelle, @kovshenin, @obenland, @BrashRebel, @clorith, @markjaquith, @coffee2code, @stephdau, @samuelsidler