OLPC:Volunteer Infrastructure Group: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(179 intermediate revisions by 21 users not shown)
Line 1: Line 1:
[[Category:Participate]]
= Infrastructure gang =


{{userboxtop}}
Are you an experienced *NIX sysadmin looking for a way to volunteer for One Laptop per Child?
{{User VIG}}
{{user mail |dogi|laptop.org}}
{{userboxbottom}}


= Infrastructure gang =
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.


Are you an experienced *NIX sysadmin looking for a way to volunteer for One Laptop per Child? Are you committed to upholding high [http://lopsa.org/CodeOfEthics ethical standards]in the performance of your sysadmin duties?
Possible initial tasks include:


We are looking for a few good sysadmins to assist with our public-facing infrastructure. Want to get to know one of the most inspiring volunteer movements on this planet?
* 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 [http://lists.laptop.org/pipermail/library/2008-August/000703.html] 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 Mailing list admin page]
* [http://lists.laptop.org/pipermail/olpc-sysadmin/ Mailing List Archives]
* [[IRC]] channel: irc.oftc.net:#olpc-admin
* Open an rt ticket: mailto:sysadmin@laptop.org


== Weekly meetings ==
== Weekly meetings ==
'''Next IRC meeting will be at irc.oftc.net:#olpc-admin 5:15 pm EDT (-04:00 UCT), every Tuesday
'''Regular IRC meeting will be at irc://irc.oftc.net#treehouse 4:00 pm EST (UTC-5), or 4:00 pm EDT (UTC-4) as appropriate, every Tuesday.'''


[http://meeting.sugarlabs.org/treehouse #treehouse meeting logs]
== I-g documentation discussion ==


([http://meeting.sugarlabs.org/olpc-admin old #olpc-admin logs]
Currently most sysadmin documentation is on OLPC internal wiki, which is generally only open to NDA'ed employees and select contractors.
and even [[OLPC:Volunteer_Infrastructure_Group/oldmeetings|older logs ]])


== Get involved ==
Here are some proposals on how to publish and protect i-g documentation.
The spirit of OLPC includes one core thing: the community.
This includes everyone, from the children and their families to their teachers and everyone who are collaborating towards the success of the project.


; How to get in touch
1) Put docs, passwords and other information onto a protected area of
:The fast way to find us:
teamwiki.
:* irc://irc.oftc.net#treehouse or by clicking on this [http://embed.mibbit.com/?server=irc.oftc.net&channel=%23treehouse&nick=wanttojoinvig link]
:* [mailto:dogi@laptop.org dogi@laptop.org]


== Purpose of the Volunteer Infrastructure Group aka infrastructure-gang ==
2) Put the information onto public wiki, and use encryption such as
gpg to encipher sensitive data such as passwords.


* Make system administration more effective and efficient
3) Use git, and rely on git access controls for protection. Possibly transclude git to wiki.
* Improve the infrastructure systems through "many hands/many minds"

* Strengthen ties with the community
4) Put data into a text file on the root directory of a machine.

Please edit and add arguments pro and con.

[[User:Hhardy|Hhardy]] 17:41, 20 August 2008 (UTC)

See [[User:Mstone/Commentaries/Infrastructure_1|Michael's proposed infrastructure-documentation-system requirements]]

13:59 < m_stone> cjl: what did I miss?
14:00 < cjl> traceability of actions?
14:00 < m_stone> good.
14:00 -!- gregdek [~gdk@wireless-nat-pool-rdu.redhat.com] has joined #olpc-admin
14:00 < m_stone> cjl: actions on the documentation or actions on the system?
14:00 < m_stone> sorry, on the infrastructure being maintained.
14:00 < m_stone> gregdek:
http://wiki.laptop.org/go/User:Mstone/Commentaries/Infrastructure_1 might
interest you.
14:01 -!- _sj_ [~sj_@wireless-19-210.media.mit.edu] has joined #olpc-admin
14:02 < cjl> In my environment (Win) we enforce a separation between admin
identities and user identities so that most daily work by admins
is done with minimally priv'ed accounts. Possibly not as
necessary in Linux environment, less credential hijacking.
14:02 < cjl> sort of a Windows sudo
14:02 < cjl> I have superman and Clark Kent accounts
14:03 < cjl> m_stone: depends on ease of keeping such logging on various types
of actions. On docs, you are talking version control and history,
on systems, it is an accountability/logging thing.
14:06 < cjl> both are desirable, tolls make the difference between how easily
either is done. For any security measure, you need to have a
"threat model" that is realistic and not just a strawman or you
would turn off all your computers and hide them in the closet.
14:06 < cjl> s/tools/tools/
14:08 < cjl> It is of course one of the worst kept secrets in the IT world that
the greatest threats are internal (apropos henry's quis custodiet
ipsos custodes), and so it is generally a matter of risk
mitigation, not prevention.
14:10 < cjl> logging is an excellent risk mitigation tool because most of us
have reputations tha we value (semi-pseudonymous or otherwise) and
logging poses the risk of discovery and exposure of malfeasance or
misfeasance.
14:14 < cjl> In a high-risk environment (e.g. my Sarbanes-Oxley compliant
accounting system) actual examination of such logging is needed,
in a low-risk environment, the simple existence of such logs is a
deterrent and a valuable forensic/recovery resource
14:17 < cjl> m_stone: Sort of a long explanation, but does that answer your
question?

== Adric's draft RT_Strategies doc ==

[[User:Adricnet/RT_Strategies]]

=== Meeting notes ===
* [[/2008-08-19]]
* [[/2008-08-17]]
* [[/2008-08-12]]

==== Internal notes ====
* [[/2008-08-19-internal]]


[[Category:Gang]]
[[Category:Participate]]

Latest revision as of 07:07, 26 January 2011


Olpc Pirate Flag.png This user is a member of the Volunteer Infrastructure Group.
@ dogi
laptop.org

Infrastructure gang

Are you an experienced *NIX sysadmin looking for a way to volunteer for One Laptop per Child? Are you committed to upholding high ethical standardsin the performance of your sysadmin duties?

We are looking for a few good sysadmins to assist with our public-facing infrastructure. Want to get to know one of the most inspiring volunteer movements on this planet?

Weekly meetings

Regular IRC meeting will be at irc://irc.oftc.net#treehouse 4:00 pm EST (UTC-5), or 4:00 pm EDT (UTC-4) as appropriate, every Tuesday.

#treehouse meeting logs

(old #olpc-admin logs and even older logs )

Get involved

The spirit of OLPC includes one core thing: the community. This includes everyone, from the children and their families to their teachers and everyone who are collaborating towards the success of the project.

How to get in touch
The fast way to find us:

Purpose of the Volunteer Infrastructure Group aka infrastructure-gang

  • Make system administration more effective and efficient
  • Improve the infrastructure systems through "many hands/many minds"
  • Strengthen ties with the community
Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=OLPC:Volunteer_Infrastructure_Group&oldid=251962"