OLPC:Volunteer Infrastructure Group: Difference between revisions
m (→Contacts) |
|||
| Line 25: | Line 25: | ||
The following infrastructures are in place to support this initiative: |
The following infrastructures are in place to support this initiative: |
||
* Mailing list: olpc-sysadmin |
* Mailing list: mailto:olpc-sysadmin@lists.laptop.org |
||
* http://lists.laptop.org/listinfo/olpc-sysadmin |
* http://lists.laptop.org/listinfo/olpc-sysadmin |
||
* [[IRC]] channel: irc.oftc.net:#olpc-admin |
* [[IRC]] channel: irc.oftc.net:#olpc-admin |
||
Revision as of 18:41, 20 August 2008
Infrastructure gang
Are you an experienced *NIX sysadmin looking for a way to volunteer for One Laptop per Child?
One Laptop Per Child is pleased to announce OLPC's Infrastructure-group! We are looking for a few good sysadmins to assist with our public-facing infrastructure.
Possible initial tasks include:
- Trac and git maintenance
- wiki extensions/improvements
- RT updating and administration
- Mailing list administration
- The Library and Sugar mailing lists could use some list administration help [1] 23:34, 19 August 2008 (UTC)
We will consider expanding the scope of the project as we learn more about what works.
Purpose of the Volunteer Infrastructure Group aka infrastructure-gang
- Make the sysadmin's job easier
- Improve the infrastructure systems through "many hands/many minds"
- Strengthen ties with the community
Contacts
The following infrastructures are in place to support this initiative:
- Mailing list: mailto:olpc-sysadmin@lists.laptop.org
- http://lists.laptop.org/listinfo/olpc-sysadmin
- IRC channel: irc.oftc.net:#olpc-admin
- Open an rt ticket: mailto:sysadmin@laptop.org
Weekly meetings
Next IRC meeting will be at irc.oftc.net:#olpc-admin 5:15 pm EDT (-04:00 UCT), every Tuesday
I-g documentation discussion
Currently most sysadmin documentation is on OLPC internal wiki, which is generally only open to NDA'ed employees and select contractors.
Here are some proposals on how to publish and protect i-g documentation.
1) Put docs, passwords and other information onto a protected area of teamwiki.
2) Put the information onto public wiki, and use encryption such as gpg to encipher sensitive data such as passwords.
3) Use git, and rely on git access controls for protection.
4) Put data into a text file on the root directory of a machine.
Please edit and add arguments pro and con.
Hhardy 17:41, 20 August 2008 (UTC)
See Michael's proposed infrastructure-documentation-system requirements