Welcome to the planning page for IndieWeb Summit 2018.
We will be running IndieWeb Summit as part of Open Source Bridge this year.
- Confirmed! to be announced with osbridge later
OSBridge is changing their format for their 10th year, and instead of a full week of talks, the first two days they're hosting other community events. This will have some implications on our event, but everything seems doable.
We may try to organize a large closing session Wednesday night across all the community events. In that case, we could have our demos take place along with everyone else, which could be fun to present to a larger audience in a proper event space.
Anyone coming for IndieWeb Summit is encouraged to submit a talk proposal to OSBridge as well.
- Start writing your talk proposal - OSBridge 2018 CFP has yet to go out.
- IndieWeb Summit: June 26-27th
- OSBridge Talks: June 28-29th
- (Leaders Summit June 25th, see Leaders if you want to participate!)
- Venue: Eliot Center
- I asked for a large space at the beginning of day 1 and end of day 2 for our keynotes and demos
- We'll have 3 breakout rooms the rest of the time
- Awaiting confirmation on rooms
- Can Mozilla host the Leaders summit?
- food - vegetarian default
- osbridge is not bringing in full meals, but they will be providing snacks and beverages throughout the event
- we can order food in for day 2 if we want
- on-site childcare (was asked about the week before 2016, so we should look into options, costs, possible sponsorship thereof etc.) note: we did not put this together in time for 2017 so will have to try again for 2018.
- Can or is Open Source Bridge / Eliot Center providing on-site childcare?
Tickets and Registration
- People who register for osbridge will be able to select IndieWeb Summit as a community event option
- We can set the price for our tickets if someone wants to register for only IndieWeb Summit
- We can still have the free indie rsvp option by somehow providing a coupon code after you send an RSVP webmention
- Awaiting details for registration
moved to 2018#Organizers
What keynotes shall we have? Brainstorm below (subjects, and speaker suggestions optional but also ok)
- What is the IndieWeb?
- State of the IndieWeb
Similar to 2016/Leaders & 2017/Leaders, the Leaders Summit sessions are open to everyone who has co-organized an IndieWebCamp from 2015-2017 or at least two Homebrew Website Club meetups during those years, and posted at least one meetup photo. If you're not sure, ask an organizer.
Possible dates (Saturday+Sunday unless otherwise indicated)
- June 23-24 (plan B, far more popular than other weekend dates)
- June 30-July 1
We may run the event as part of Open Source Bridge 2018. The dates for that will be the week of June 25-29.
- June 26-27 (Tuesday-Wednesday) (with half-day Leaders summit June 25th)
- June 28-29 (Thursday-Friday)
Rejected dates (all well below candidate dates above)
Vague date related thoughts:
- 2.5 days again (half day leaders summit, 1 day intro/brainstorming, 1 day hackday)
Other events with similar audiences:
- ? Open Source Bridge, Portland, OR
Other events / possible conflicts:
- 2018-06-11..15 Mozilla All Hands SF
- 2018-07-02..05 CSSWG meeting
- requires flying out of SFO/Westcoast 2018-06-29 due to intl dateline + travel time.
- 2018-07-14..20 IETF 102 Montreal https://ietf.org/meeting/upcoming.html
Notes from previous years
Notes from after 2017 IndieWeb Summit to keep in mind for this year
- In 2017 we had 50 registrations, and ordered food for 40.
- 31 people attended on day 1, and 21 attended on day 2.
- Hot breakfast on day 1 was great, and many people ate the leftovers for lunch that day. We still had too much left over though.
- We consistently have people drop out the second day, so we can likely order less food for the second day than the first.
- We had way too many bagels for day 2 breakfast. We can probably order 1 bagel for every 2 people.
- The afternoon coffee refresh was a good idea, but it should have come around 2pm instead of 3pm. Also we didn't need as much as was ordered. The 4 coffees in the morning was a good amount, and probably needed only 2 more in the afternoon.
- An external sign out on the street would have made it easier to find.
- Several remote attendees filled out the ti.to registration, so we should make sure it's clear that the ti.to registration is just for in-person attendance.
- Some people registered on ti.to twice, a month apart. Not sure what the problem there was or how to fix it.
- We lost the beginning of the demos because Wirecast on the computer that was recording/streaming to youtube crashed. In the future, we should record the Vidyo stream in the main room as well as a backup.
- We forgot to take a group photo on day 2.
- Designate a camera-free area (like a conference room without a Vidyo setup) for people to use to type in passwords when they want to make sure they aren't being livestreamed and filmed at multiple angles