to-do

From IndieWeb
(Redirected from To-do)
Jump to: navigation, search

Next steps for IndieWebCamp and IndieWeb efforts.

See something here you can help with? Jump in and help with incremental edits!

Questions? Ask in our discussion channels!

Roughly ordered by importance / oldest first.

Update How to Run an IndieWebCamp page/documentation

  • We need an easier/simpler/shorter "how to run an IndieWebCamp" page / documentation https://indieweb.org/IndieWebCamps
  • We need IndieWebCamp in a box prepared to send to new organizers https://indieweb.org/IndieWebCamp_kit
    • Things like "Hello my URL is" stickers, sticky notes for the grid, maybe masking tape. Or at least a list of things to order and have delivered to the venue
  • Questions to ask registrants like: food prefs, childcare needs etc
  • Decrease challenges like all the wiki pages, the nice pages at 2017.indieweb.org/ etc
    • Keeping the choice of which ticketing system to use, for regional prefs. E.g. Tito eventbrite brownpapertickets or even Meetup
  • Possible templates for typical camp pages and planning layout so it doesn't have to be reinvented
  • Add more detailed steps to documentation on what types of information should be gathered via a ticketing system
  • Add some specific tutorials regarding certain ticketing systems such as Tito in regards to best practices like copying an existing event as the beginning for a new event

Improve Getting Started

In progress of updating Getting Started steps to:

  • simplify steps (create subpages if necessary for longer explanations)
  • reduce steps to only those that are required and have direct benefits
    • i.e. are direct steps toward achieving IndieMark levels in various areas.
    • provide an explicit "Why?" quick and easily understandable explanation of the benefits, the motivating reasons for taking this step. What problems are solved? What new capabilities do you get by taking this step.
  • re-order steps in order of ease of implementation / dependency
  • move nice-to-haves, or simpler side options, to other pages.

I've updated Connect and Personal Domain accordingly (including subsuming short domain as a "bonus" subpart of personal domain) so far and will work on subsequent Getting Started steps accordingly. However, if you want to help with these updates, please go for it and edit accordingly! - Tantek 15:06, 7 May 2013 (PDT)

Currently working on:

  • ...

Improve Why Explanation

  • create subsections on why for frustration, fear, death
  • provide good photo/summary page links (e.g. lightboxes of screenshots) for all corp site failures on site-deaths and why pages.
  • copy each "why" citation for a silo to a Criticisms or Downtime section for that silo

Quoting Embedding Display

Quoting Embedding Display (QED) guidelines:

  • Write IndieWeb versions of embedding/quoting display guidelines for when other sites display indie web posts/content

See: quoting for details and see reply-context for some thinking/progress.

Tagboards

Create additional Tagboards (e.g. http://tagboard.com/indieweb ) for IndieWeb related things, and any tags used/mentioned by @indiewebcamp (or @indiewebcampuk) and link them to the respective wiki pages here.

Process Criticism

Blog Update to Call For A Distributed Web

(more than one person blogging about this would be good)

Bonus, also integrate the points / proposals / projects mentioned in https://www.oreilly.com/ideas/what-if-we-build-the-internet-we-always-wanted into the post such that the post responds to both at the same time (there's a lot of overlap).

Blog State of the Interoperable Decentralized Web

(more than one person blogging about this would be good)

Follow-up to previous blog post and http://dci.mit.edu/assets/papers/decentralized_web.pdf (PDF, sorry, academic source) with case studies on some projects from that blog post and the 2016 Decentralized Web Summit

Consider also explicitly citing and following-up to:

Document from most to least interoperably deployed decentralized web solutions.

Noting second to last anything mentioned in the MIT report that is deployed with real users but single-project monoculture with all the downsides of that, fragility etc.

Noting last anything mentioned in the MIT report that is either not deployed (e.g. academic / theory / hand-waving / hype), or experimentally deployed, but no real (even selfdogfood) users.

Blog on Open Standards for the Decentralized Web

(more than one person blogging about this would be good)

Follow-up to previous blog posts and Aaron Parecki’s OSBridge 2016 talk on the topic, focusing first and mostly on:

  • Well deployed interoperable web standards (10+ interop impls with real world daily users across systems)
  • Emerging interoperable web standards (3+ interop impls with real world daily users across systems)
    • WebSub
    • Maybe LDN? Double-check actual software/systems/sites in use.
  • Other standards being implemented (1+ impls, maybe interop, with real world daily users within systems)
  • Monoculture standards - "standards" only implemented (often driven by) a single implementation, summarize such monoculture problems etc.

IndieWeb Homepage Live Modules

Archive sessions and chat logs

Refer to Etherpad: Archiving IndieWebCamp notes.

Move YouTube archived content to archive.org

As we've moved to storing new sessions on archive.org, you can volunteer to move old sessions there that were recorded on YouTube...and maybe even watch them as well.

If each of us take a few when time permits...we can get through them easily.

Instructed parties can enquire in chat for the credentials for our archive.org account if you do not have them.

See Also

  • Create an issue on Coralproject / talk https://github.com/coralproject/talk/issues asking to "Support Micropub to keep a copy of your comments on your own blog", noting the use-case / real-world example that there are Coral users that created their own Tumblr to just to manually keep a copy of their comments!
  • write-up a "debunking" misconceptions entry for "No IndieWeb is not just people who program their own websites" per https://mastodon.social/@Gargron/100548246348444630
    • "@KevinMarks @cwebber @aaronpk I'm sorry but indieweb doesn't count, you're programming your own websites, you're not the general population. That method is not accessible for most people on here." @Gargron August 14, 2018
  • Document when/how to setup initial yyyy.indieweb(.)org/cityname page as part of IndieWebCamp_Organizing#Before
  • Document when/how to connect up tito registration to yyyy.indieweb(.)org/cityname page as part of IndieWebCamp_Organizing#Before, and be sure to uncomment / show Indie RSVPs!
  • needs clean-up, some sort of IA/organization at a minimum clustering of similar "levels" of building blocks for easier chunking / understanding, and most of all, a set of diagrams illustrating how they interrelate
  • do an iteration of updating IndieMark per recent tweet about it: https://twitter.com/eldelacajita/status/1091036825102307328
    • "I found their IndieMark very interesting and useful for understanding the "how" part: https://indieweb.org/IndieMark

      It "a set of metrics for measuring the indieweb-ness of a site, and a step-by-step approach to incrementally adopting indieweb features on your site"." @eldelacajita January 31, 2019
  • submit patches to add microformats2 support to the HTML output from MHonArc
  • ^^^ start here: https://github.com/Conservatory/MHonArc/blob/master/lib/mhamain.pl
  • Good example of a series of diagrams to explain the progression of a technology, could be useful to do an IndieWeb building blocks version: https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future/
  • fix the home page markup/styling in Template:Main_Page.css to be properly responsive for mobile widths so as to NOT overlap text (e.g. Discuss Events currently overlap the logo in mobile browsers, or narrow window on desktop), and to *not* use "position:absolute" on the nav UL as a horrible hack to "pull it up" to the top of the page.
  • Incrementally update Getting Started on WordPress for accuracy and user-friendliness, see Chris Aldrich's work in progress on a rewrite: User:Boffosocko.com/wordpress-draft and feel free to merge from there into the current page.
  • Simplify into a section with shortest possible list of IndieWeb Building Blocks necessary for interop, including using clustering to make fewer total blocks.
  • add [[Category:Demos]] to past camp demo pages for inclusion to https://indieweb.org/Demos
    • Chris Aldrich added a bunch in 2020-07 using search, but likely didn't get them all (yet)
  • garden this: Pages that link to "selfdogfood" and instead how to contextually link to https://indieweb.org/eat_what_you_cook
  • The demos from IWC Austin 2020 need to be extracted from chat logs and documented on 2020/Austin/Demos
  • stub a rude FAQ page based on the general idea as described in https://scottberkun.com/2007/how-to-write-a-rude-qa/ with answers to "but it costs money to have a domain" and "but what’s the business model"
    • "but it costs money to have a domain" is concern-trolling. It's a nonsense isolated argument when everyone making that argument has spent 100x on their hardware (and annual cell service!) that they are using to make the argument. also until we have cities/states/countries providing UBS like free public water/toilets to housing & healthcare and eventually wifi & domains, if you make something "free" to users then you turn them into the exploited product. also everything costs money and if it doesn't, then someone else is paying on your behalf, and very likely getting something out of it that benefits them in some way, e.g. ads, with the exception of something like UBS which requires political changes.
    • "but what’s the business model": Nope, no business model here, please go find something else to exploit you capitalist.