Summit2013/FAQ: Difference between revisions

No edit summary
Line 47: Line 47:


We considered it.  And, there are pros and cons to both approaches.  2,000+ people in one space in no way guarantees you will see everyone. Intimacy suffers. Spaces to accommodate such a big group are difficult to find, etc. We are committed to trying the multi-city approach this year and will learn from it.
We considered it.  And, there are pros and cons to both approaches.  2,000+ people in one space in no way guarantees you will see everyone. Intimacy suffers. Spaces to accommodate such a big group are difficult to find, etc. We are committed to trying the multi-city approach this year and will learn from it.
== Why are we have three events instead of one? ==


Having  three different locations rather than gathering  2,000 people in one  place is something new we will try this year.  This means this Summit will  be different than 2010. Mozilla is not like we were in 2010, the world is not like it was 2010, and innovation is at the heart of who we are. The idea is that with three locations, each has the intimacy of 600 or 700 people, some shared content and some innovative ways to join the three locales. We will  learn from this and use what we learn to design our future events.
Having  three different locations rather than gathering  2,000 people in one  place is something new we will try this year.  This means this Summit will  be different than 2010. Mozilla is not like we were in 2010, the world is not like it was 2010, and innovation is at the heart of who we are. The idea is that with three locations, each has the intimacy of 600 or 700 people, some shared content and some innovative ways to join the three locales. We will  learn from this and use what we learn to design our future events.


The  multiple locations also means that the Summit will be different than a geo-located “work week.” It’s unlikely that everyone who you want to see face to face will all be in the same place. On the other hand, an organization our size needs trusted connections across groups, and good relationships between people you would never have thought to get to know.
The  multiple locations also means that the Summit will be different than a geo-located “work week.” It’s unlikely that everyone who you want to see face to face will all be in the same place. On the other hand, an organization our size needs trusted connections across groups, and good relationships between people you would never have thought to get to know.
== Will each location interact with each other? How? ==
Yes. This is a huge part of the experience. We will have a large working group dedicated to figuring this out.
==We're going for a decentralized and distributed approach per [https://blog.lizardwrangler.com/2013/03/31/mozilla-summit/ Mitchell], so why not more locations, such as LATAM?==
Perhaps. Our thinking is that it's less about the locations themselves - since  we are all distributed.  The focus here is on how we work together. Unlike MozCamp, where there is a regional focus for the event, the  Summit is about Mozilla as a whole.
After much consideration we landed on three with MozSpaces.  We'd like to be able to leverage our Mozilla Spaces for the Summit for local open houses or other local celebrations.  In addition, we chose locations that would allow for a least a few hours of timezone overlap.


== Why did we not target the summer? ==
== Why did we not target the summer? ==
Line 62: Line 70:


Likely, since we like technology so much. Decisions about Summit content will be  determined for the most part,  during the [[SummitPlanningAssembly | Summit Planning Assembly]] in June. Until then, the team is mostly focused on logistics.
Likely, since we like technology so much. Decisions about Summit content will be  determined for the most part,  during the [[SummitPlanningAssembly | Summit Planning Assembly]] in June. Until then, the team is mostly focused on logistics.
== Why not have Latin America (LATAM) as a location? ==
We  considered many locations and landed on three with MozSpaces.  We'd like to be able to leverage our Mozilla Spaces for the Summit for local open houses or other local celebrations.  In addition, we chose locations that would allow for a least a few hours of timezone overlap.
== Will each location interact with each other? How? ==
Yes. This is a huge part of the experience. We will have a large working group dedicated to figuring this out.


== Why  weren't visa-friendly cities chosen for the Summit? (eg. Hong Kong or  Singapore which don't require visas for visitors from Africa or Latin America) ==
== Why  weren't visa-friendly cities chosen for the Summit? (eg. Hong Kong or  Singapore which don't require visas for visitors from Africa or Latin America) ==


A  country's friendliness really depends on the country from which you are traveling. We reviewed the visa requirements for these locations and determined they were relatively reasonable.
A  country's friendliness really depends on the country from which you are traveling. We reviewed the visa requirements for these locations and determined they were relatively reasonable.
== [https://blog.lizardwrangler.com/2013/03/31/mozilla-summit/ Mitchell] talks about our distributed and decentralized participation structure  and how  it represents the web. Wouldn't it make more sense to have  Summit locations reflect that, rather than have a  North-American/European focus? ==
Perhaps. Our thinking is that it's less about the locations themselves - since  we are all distributed.  The focus here is on how we work together. Unlike MozCamp, where there is a regional focus for the event, the  Summit is about Mozilla as a whole.
    
    
== Wouldn't it have been cheaper to have one Summit in one location? ==
== Wouldn't it have been cheaper to have one Summit in one location? ==
Confirmed users, Bureaucrats and Sysops emeriti
1,168

edits