See [[SIPB Documentation|/doc]] for documentation produced so far.
Existing documentation can always be improved.
-<!-- See LennyBugs and LennyBugsAll for the bugs we took on in the Lenny
-RC-bug-squashing hackathon of December 13, 2008. -->
+Other SIPB educational activites include the [AskSIPB](http://www.mit.edu/~asksipb/) column in The Tech, an array of [IAP classes](http://sipb.mit.edu/iap/), and the weekly [Cluedumps](http://cluedumps.mit.edu/) series each fall.
## Documentation Ideas
* "Athena Dotfiles" -- These are weird and nonstandard compared to traditional UNIX and should be documented, including things like `.environment`
* There's some documentation at [http://web.mit.edu/olh/Dotfiles/]
- * scripts.mit.edu -- lots of neat internals to explain
-
- * AFS: There should be a central documentation point to using your
- AFS space, granting access through AFS and through `web`, accessing
- files from various platforms, and so on. Don't duplicate iAFS;
- perhaps latex2html and update it.
-
- Setting up servers:
-
- * "Client Certs" should explain, if for some perverse reason you don't
- want to use scripts.mit.edu :-), how to set up client cert
- authentication on your own machine (grab the CA out of the
- apache-ssl locker, submit a CSR to mitcert@, set up scripts' magic
- Apache modules to make your life easier)
+ * scripts.mit.edu -- lots of neat internals to explain; the scripts.mit.edu bugtracker also includes some identified [documentation tasks](http://scripts.mit.edu/trac/query?status=assigned&status=new&status=reopened&keywords=~docs&group=component&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=keywords&order=priority)
* Add your own here!
-
## Useful Links
* [[ikiwiki/Formatting]] -- Documentation on this wiki's formatting language
sipb-www / wiki.git / blobdiff