<div dir="ltr">We have a number of documents pertaining to configuration, backup procedures and passwords for the OLPC servers currently on the OLPC internal wiki. No volunteers, and few contractors have access to internal wiki. We would like to be able to share some or most of this information with the Volunteer Infrastructure Group members without making it available to the general public.<br>
<br>We want to be able to limit access to just these documents particularly to VIG members only. One way to do this is through using the lockdown extension currently installed on the OLPC teamwiki. Using this extension, one way to have granular access control over the documents would be to have a Volunteer Infrastructure Group namespace on teamwiki.<br>
<br>I would like to understand if there are any good reasons not to move these documents from internal wiki to a new VIG namespace on teamwiki. If so, please suggest better alternatives.<br><br>--HH.<br><br><div class="gmail_quote">
On Thu, Sep 18, 2008 at 11:36 PM, Mel Chua <span dir="ltr"><<a href="mailto:mel@melchua.com">mel@melchua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
SJ wanted to avoid making new namespaces in teamwiki - he/I/Kim/Adam had a conversation a few days back about how to manage data access / privacy, but that conversation was never quite finished since 8.2.0 slammed in. Not sure how to pick the convo up again just yet (everyone is hosed, and this argument will probably drag out when it comes up again).<br>
<br>
A possible different approach to where to port things: who *can't* have access to this stuff? (If we moved it into the Team namespace on teamwiki, would that work? Do we need to make everyone with access sign an NDA?)<br>
<br>
-Mel<br>
<br>
Henry Edward Hardy wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
Mel, thanks for the notes.<br>
<br>
For now, let's copy everything from the sysadmin stuff on internal to a new namespace on teamwiki.<br>
<br>
--HH.<br>
<br></div><div class="Ih2E3d">
On Wed, Sep 17, 2008 at 1:25 PM, Mel Chua <<a href="mailto:mel@laptop.org" target="_blank">mel@laptop.org</a> <mailto:<a href="mailto:mel@laptop.org" target="_blank">mel@laptop.org</a>>> wrote:<br>
<br>
Meeting notes from yesterday's i-gang meeting; apologies for the delay.<br>
<br>
<a href="http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group/2008-09-16" target="_blank">http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group/2008-09-16</a><br>
<br>
The table of machines I was going to make is already on internalwiki,<br>
<a href="https://laptop.org/internalwiki/index.php/Table_of_Machines" target="_blank">https://laptop.org/internalwiki/index.php/Table_of_Machines</a>. We need to<br>
migrate things from internal (and team, if there's stuff there) to<br>
public if possible - I'm willing to do the gruntwork of inter-wiki<br>
copying before things grow too large, if someone can help me flag what<br>
should and shouldn't go public.<br>
<br>
--<br>
Mel Chua<br>
QA/Support Engineer<br></div>
<a href="mailto:mel@laptop.org" target="_blank">mel@laptop.org</a> <mailto:<a href="mailto:mel@laptop.org" target="_blank">mel@laptop.org</a>><br>
<br>
_______________________________________________<br>
Olpc-sysadmin mailing list<br>
<a href="mailto:Olpc-sysadmin@lists.laptop.org" target="_blank">Olpc-sysadmin@lists.laptop.org</a> <mailto:<a href="mailto:Olpc-sysadmin@lists.laptop.org" target="_blank">Olpc-sysadmin@lists.laptop.org</a>><div class="Ih2E3d">
<br>
<a href="http://lists.laptop.org/listinfo/olpc-sysadmin" target="_blank">http://lists.laptop.org/listinfo/olpc-sysadmin</a><br>
<br>
<br>
<br>
<br>
-- <br>
"Work is love made visible"<br>
--Kahlil Gibran, 1923<br>
</div></blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>"Science has a simple faith, which transcends utility... It is the faith that it is the privilege of man to learn to understand, and that this is his mission. If we abandon that mission under stress we shall abandon it forever, for stress will not cease. Knowledge for the sake of understanding, not merely to prevail, that is the essence of our being."<br>
<br>--Vannevar Bush, 1967<br>
</div>