How to use DOCS
The DOCS (Documenting Our Crap and Stuff) initiative intends to provide a centralized , near-exhaustive, resource for all SIPB knowledge.
This space should provide – either directly, or by pointing to other sources – complete and easy to follow explanations of how our projects , their current statework, how to get started on them, relevant computing concepts and all our SIPB-related shenanigans!
Any other, non-sensitive, documentation outside of DOCS (e.g. AFS files, READMEs, website, Ask SIPB, Cluedumps archives) should ideally be pointed to in the relevant pages through external links, but can also be duplicates under the writer's discretion. Moreover, all pages with relevant information should have at least one listed page maintainer.
Apart from that, you have You have complete creative freedom to write documentation and make this space your own. You are encouraged to writegive feedback, updateimprove, and improve write to any textpage.
Read: Guidelines for writing DOCS
Administrivia:
Projects:
- Petrock: An OpenID connect provider for Touchstone.
- HWOPS: Server Room & Hardware Operations
- Lemonpepper: Internal SIPB Virtual Machines
- Matrix (TODO)
- Hydrant (TODO)
- CourseRoad (TODO)
- XVM (TODO)
- Scripts (TODO)
- LLMs (TODO)
- DormSoup (TODO)
- ARK (TODO)
- Mirrors (TODO)
- Tor (TODO)
- DoorPi (TODO)
- SIPB Sign (TODO)
- Project Database (TODO)
- AFS (TODO)
- Mattermost (TODO)
- Discord (TODO)
- Opengrades (TODO)
- Mastodon (TODO)
- join-dormspam (TODO)
- sipbgo (TODO)
Other:
Other other:
- Office Trivia: alert the FBI
- Fuzzball Stories: Anecdotes and History of SIPB
- SIPB Swag
- is sooner than you think
Projects Archive:
- LAMP: Library Access to Music Project