2025-06-27 Wiki work

Wiki work

• Date: 2025-06-27
• Present: jade, piegames
• Topic: Information organization in the wiki and the homepage

Summary: We have a mess of information in the pad system which is not well organized by quality, and it's hard to deal with it.

Action items

• Create a new book for founding-days Lix pad in the Wiki, migrate stuff there
• Create a place for meeting notes in the wiki, with a nice template and everything
• Clarify whether people are intended to edit each section of the wiki (or like somehow blanket make it clear that it is okay absent further information)
• Maybe document a procedure for taking a matrix log (with LLM prompt for initial phase?) and turning it into more useful information
• piegames can take care of migrating the governance-related pads, in the sense of finalizing them and getting them approved and making them official (this will take a lot of time though)
• Rework https://wiki.lix.systems/link/9#bkmrk-freezes to reflect current processes
• Create a "Developers Announcements" channel for low-volume communication between all devs
• Migrate https://lix.systems/resources/ to the wiki

Meeting notes

• Organization of the design documents is confusing

• Need to explain contributions better

  • The "how to not write C++" is ill-located

• Need governance meta related channel

• We should probably move the resources page

• We probably should have better organization of the "lix manifesto" related stuff

• Related projects is ill located

• Unclear where we want to put each thing, e.g. do community standards go on the website

• minor wiggles moment of the quicklinks page being added to the website but not being linked anywhere

• Stuff like cultural values and so need to escape the pad zone

• IFD discussion pads

• Discoverability problems

  • Wiki > Pads > Matrix

• Pads problems

  • We sometimes archive matrix discussions into pads
  • Throw them into a large language model lol
  • Eg. improving IFD pad

• Who does this work of archiving and librarian stuff

  • Could jade do this while tired at work?

• Information organization

  • Wiki: stuff that should not connote endorsement and does not allow people to mess with wiki
  • piegames: this is kind of a problem for the governance pages
  • The website has no way to have table of contents and nesting support
  • Failure mode of not caring too much about too wide edit permissions is that people don't think that they are allowed to edit it

• RFC process where it gets committed to a repo means that you know what actually is committed to

  • In general we cannot afford more process

• This will burn out piegames if they have to do all the coordination labour in the project

  • How do we make this sustainable?

• We can avoid having to do more of this by having a very minimal quality bar for the wiki and accept that it is going to become a mess

• Archived stuff

• Space for meeting notes

  • Write meeting notes with a template that requires that it says who was doing the meeting

• Issues with pads is that we don't separate trash and useful information

  • Pad index is a mixture of stuff that is partially dev log and partially dev result
  • We should organize the dev log by date/topic, rather than by topic

• piegames prefers a process and end result type note structure rather than these, which are a headache