From IndieWeb
Jump to: navigation, search

The Leaders Meetup is a half-day of activities and sessions the day (2018-09-26) before IndieWebCamp NYC 2018, for everyone who has co-organized an IndieWebCamp in the past two years or at least two Homebrew Website Club meetups with at least one meetup photo.


Similar to 2018/Leaders, the Leaders Meetup sessions are open to everyone who has co-organized an IndieWebCamp from 2015-2018, planning an IndieWebCamp later this year, or co-organized 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.


RSVP here on this page ( https://indieweb.org/2018/NYC/Leaders if you will be participating in the Leaders Meetup:

Remote Participation

If you can't make it in person but you're available to participate remotely, please add yourself below. Please note that we'll likely make use of the Video Conference room remote conference setup at Pace University.


Sorry to miss you, let us know if you can't make it and we'll try to reach out with specifics that may apply to your city.


Remote participants in other zones:

  • PDT: 06:30-11:30 (UTC-7)
  • UTC: 13:30-18:30
  • BST: 14:30-19:30 (UTC+1)
  • CEST: 15:30-20:30 (UTC+2)


Times are EDT (UTC-4) unless noted otherwise

  • 09:30 Leaders breakfast TBD
  • 10:30 Leaders Summit
  • 14:00 Leaders Summit Wrap-up & Next Steps
  • 14:30 Leaders Summit closes and
  • 14:45 Lunch/Dinner Gao Taco
  •  ??:?? Optional: Walk across Brooklyn Bridge
  • 20:00 Meetup Dead Rabbit Grocery and Grog

Other Leaders related activities (just FYI, unless you want to help)

  • ...


  • breakfast TBD
  • Seidenberg School of Computer Science and Information Systems
    163 William Street, 2nd Floor, New York, NY 10038. VC Conference Room. (map)
  • lunch TBD
  • offsite / group activity TBD
  • dinner after TBD


  • When/where? More specifics!
    • figure out all TBDs in previous section
    • morning = remote participation with US leaders?
    • break for dinner / random leader bonding activity


Specific, timely suggestions for this Leaders meetup by folks who will be there (otherwise please add to: Leaders#next).

Meta: this list is

  • Unordered
  • To be prioritized by Leaders in-person at the meetup
  • Inevitably incomplete (feel free to bring up more topics in https://chat.indieweb.org/meta)
  • May have some items pre-empted by existing/longer-term Leaders#Issues (and that's ok).


  • Tantek Çelik suggestion reading/viewing BEFORE the meetup:
    • everything linked from this section "Why to avoid negative behaviors" from the microformats wiki
      • especially Kathy Sierra article and Google Videos about dealing with poisonous people
  • Tantek Çelik meta on Leaders Summit / Meetup
    • What did we think we did right / better / worse compared to last year?
    • What did we leave open / unresolved from 2018/Leaders#Next_Time?
    • What new community challenges have we encountered since?
    • What are the most important things we can do to improve the community in the coming uyear?
    • Which of those are the easiest / most scalable?
  • Aaron Parecki: Slack/IRC admin help - mods, permissions, deleting spam
  • gRegor Morrill Decide on workflow for Leaders Issues proposed 2018-09-11
    • tl;dr: Where do new issues go and how do we track them through next steps/did-not-finish/completion?
    • Leading up to 2018/Leaders there was confusion because that page was originally copy-pasta from 2017/Leaders, including the sessions. People started adding comments to those sessions as if they were new. On top of that, Leaders had a list of actually-new issues. In chat, before 2018/Leaders, Tantek Çelik said we should keep new issues to Leaders. I took some time to split out new-for-2018 comments and merged them into Leaders. Day-of 2018 Leaders, we prioritized sessions in etherpad and they ended up in one of three sections based on whether there were totally done, had todo items, or we did not get to discuss them.
    • Here's my proposal for the workflow: User:Gregorlove.com/sandbox
    • +1 Tantek Çelik
  • Tantek Çelik: Homepage update (and principles update, complete work from 2018/Leaders). We did major updates in 2014 (the three icons/points), 2016 (new skin, lots of wording updates). It's reasonable to do another update of the home page this year (2018) with everything we've learned as well as the growth of the community and new services like micro.blog, consider feedback like ”remove all the nerdiness“, and reconsider remaining 2016 ideas. I'd like to do at least a draft of this (homepage update) during IWC NYC at a minimum as a 2018/NYC/Leaders session to start with, and possibly a session on IWC NYC day 1.
  • Tantek Çelik: Homepage update: three paths - a specific brainstorm for the above.
    • We might benefit from a 2-3 track home page - address the "only for self-coders" misimpression/misframing
    • I think we roughly need three tracks for three generations at this point (I think we are that spread out)
    • 1. (gen 3, savvy users, no/low admin) Want to switch to IndieWeb? Here's how (micro.blog etc.)
    • 2. (gen 2, WordPress users who are familiar adminning their own install, use plugins etc.) Want to use your WordPress on the IndieWeb? Here's how (step by step tutorial for plugins, configuring them, testing posting+POSSE+backfeed)
    • 3. (devs, gen 1) Want to make your own indieweb site? Here's how (existing Getting Started docs)
      • make it clear this is also for you if you are building software for other people, like micro.blog
      • whether you're building a site for one or for thousands, here's how you can do it (to address misconception/misframing of "build things that only you will use")
      • at the same time, there is a lot of value in the principle of building for yourself, just in this case it means make sure the thing you're building for other people you also use yourself
    • we order it in that way because better to appeal to the gen 3 folks first (there are more of them), and quickly help them before they get confused / overloaded. the WordPress crowd will find the WordPress path, IF it is labeled as such for them. and the homegrown / coder crowd will find read everything til they find the github links etc. and keep going
    • I think if we look at rethinking the home page for these three "tracks", it will help illuminate how we need to update other pages linked from the home page like /principles
    • we could literally have three equal width columns, each roughly the width of a typical mobile portrait display, different background colors, maybe even different font choices
    • scroll down with different "bands" of background brightness for different "topics"
    • e.g. join the discussion: #indieweb #indieweb-wordpress #indieweb-dev
    • column layouts like that become tabs on mobile with the bright backgrounds of each in each tab, with summaries
      • | Join the IndieWeb | WordPress users | Developers |
      • defaulting to Join the IndieWeb, expecting Wordpress / Developers to self-select
    • so it looks good both on desktop and mobile
  • Tantek Çelik Move IndieWeb/IndieWebCamp tweets to meta (also include typo IndiWeb)
    • From reviewing the past 5+ days of tweets (2018-09-06..11) going to the #indieweb channel and most of them are dev-related, some are -meta related, and a few (very few) are higher level indieweb user-centric related
    • We already have some dev-related keywords going to #indieweb-dev (like Webmention)
    • I'd be up for switching whatever tweets currently make it to #indieweb to instead go to #indieweb-meta
    • For *tweets* only in particular, that is:
      • I still think we should surface indieweb #indieweb posts to the main channel (from WebSub / Superfeedr)
      • Twitter has also become more negative (regardless of topic), thus meta is better than main for that because we can discuss the meta aspect of such negativity if necessary rather than having them pollute and "bring down" the main channel (recent indieweb tweets seem fairly positive, though we've seen negative attacks before which typically are about some meta issue, not anything actually directly indieweb applicable to someone's personal site)
    • See also: 2018/Leaders#reduce_chat_noise and 2018/Leaders#Task_List
    • Thoughts?
  • ...


Please review 2018/Leaders#Next_Time and propose new topics on Leaders#Issues.

At the Leaders Meetup, notes will be taken in etherpad and later archived here.

... Session Name ...

When: 2018-11-02 HH:MM

Proposer: {{proposer}]


Ideas from this page and from Leaders#Issues were listed in the etherpad and then sessions were put in a rough priority, or given an explicit time slot.

Proposed from this page

Proposed from Leaders

  • ...

Task List

Note the tasks coming out of sessions.

  • ...

Next Time

These topics were suggested but did not get discussed at this Leaders Meetup.

  • ...



The Leaders on call (not all pictured)

Out for lunch

See Also