From IndieWeb
Jump to: navigation, search

Leaders Summits are half-day events for everyone who has co-organized an IndieWebCamp or was active organizing Homebrew Website Club meetups in the past two years. (Due to the spread-out nature of our community, many attend remotely).


The participants in the 2017 Leaders summit (before IWS) decided that more frequent (than yearly) Leaders Summits could be beneficial.

The next IndieWeb Summit will be mid-2018, and it's very likely we'll have a Leaders Summit the morning before the Summit.

If you're planning an IndieWebCamp between now and the next summit, and want to organize a Leaders Summit beforehand, drop a heads-up here linking to your IndieWebCamp's planning page with details about a proposed Leaders Summit.


collect issues here until a specific agenda page for the event is created

  • Code of Conduct One of the pieces missing from it is an ombudsmanish contact/enforcement mechanism or a means of helping to resolve issues. Usually at Camps we mention up front who to contact or converse with privately if someone has an issue? How would that/could that be done in our online space? Or at least doing so in private if someone had difficulty in speaking up. I suspect Gen2+ folks may have even bigger issues for contacting leadership for resolution depending on their level of technical ability. Who would they contact and how? Privately at least?
  • What services are essential for running the IndieWeb community resources, and who has access to them?
    • Content
    • Domain name(s)
      • Who has access to indieweb.org, can configure the DNS, etc?
      • How can access to these be split amongst several people?
    • Communication
      • Who can manage the Slack server / channels?
      • Who can manage the IRC channels?
        • It looks like we have several +o people. Are they all listed as Founders or equal on ChanServ?
        • all ops are in US timezones and thus not available on EU mornings (discussed 2017-12-17 due to small spam-wave on Freenode)
        • Is there anything to gain from registering with Freenode? (or has this been done already?)
      • Is there any managing we have to do for the Matrix bridge?
      • How quickly could a new Slack bridge be created if Loqi goes down? The bridge code is available on GitHub.
    • Official channels
    • For projects we depend on, e.g. the Slack bridge, should they be mirrored to the indieweb GitHub account? That way the community has them even if the original author decides the remove their repository.
    • Third parties we depend on? Can more of these be self-hosted?
  • For IWC organising, is it interesting to state kid friendliness somewhere?
  • Redirect IRC People to something less about chat plumbing?
    • I like that we've moved away from linking "IRC" in pages and instead use "discuss". To go along with that, it seems like this page should follow suit. "Chat people" sounds hokey, but maybe something like "Chat community," "Discussion community," or similar. Possible issue: ensure the chat.indieweb.org logs follow the redirect. gRegor Morrill 15:11, 2 January 2018 (PST)
  • Plan a microformats2 parsing/issues breakout session during IWS day 1 afternoon

planning considerations

  • Location requires good internet for streaming
  • Some kind of conference room microphone or professional videoconference setup (Mozilla locations have Vidyo, which has worked well)
  • time: due to the international nature of the community, good times are mornings on the US west coast and evenings in Europe (e.g. 2017/Leaders was at 09:00 PDT (UTC-7) == 16:00 UTC == 18:00 CEST (UTC+2)




See Also