[resending to list]<br><br><div class="gmail_quote"><div class="gmail_quote"><div class="Ih2E3d">On Wed, Jun 4, 2008 at 5:03 PM, David Farning <<a href="mailto:dfarning@gmail.com" target="_blank">dfarning@gmail.com</a>> 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>On Wed, 2008-06-04 at 22:23 +0200, Marco Pesenti Gritti wrote:<br>
> On Wed, Jun 4, 2008 at 10:16 PM, David Farning <<a href="mailto:dfarning@gmail.com" target="_blank">dfarning@gmail.com</a>> wrote:<br>
> > Here is a update of the wiki status.<br>
> ><br>
> > 1. Started creating framework for developing modules within the large<br>
> > sugar community.<br>
> > <a href="http://wiki.sugarlabs.org/go/SugarLabs:Community_Portal#Modules" target="_blank">http://wiki.sugarlabs.org/go/SugarLabs:Community_Portal#Modules</a><br>
> ><br>
> > I would like to begin the 'big move' by first moving/copying the olpc<br>
> > information regarding theses topics to Sugar Labs. Is this something<br>
> > that I should talk to Sj about? or would someone who has been involved<br>
> > with OLPC and Sugar Labs prefer to start that conversation?<br>
><br>
> Can you explain more in detail what you would like to move where?<br>
</div> * SugarModule<br>
* SugarBaseModule<br>
* SugarDatastoreModule<br>
* SugarPresenceServiceModule<br>
* SugarToolkitModule<br>
* SugarArtworkModule<br>
<br>
/loop/<br>
1. I would like to go through the OLPC wiki page by page looking for<br>
material related to developing the 6 modules listed above. (working<br>
with around 5 pages per batch)<br>
2. Post a 'wiki -move request' to iaep and a appropriate communication<br>
channel at OLPC.</blockquote></div><div><br>The appropriate channel is the OLPC wiki itself. Transwiki'ed pages should copy their edit history to the new site. The OLPC wiki could use a new template for suggesting a page for a transwiki move -- if it's no longer needed on the OLPC wiki, it can be replaced by a soft redirect.<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
3. After receiving approval, export pages from wiki.olpc this will<br>
leave original contents at olpc.</blockquote></div><div><br>You don't need approval to export pages from the wiki. Both wikis use an attribution license, which makes reuse pretty straightforward.<br> </div><div class="Ih2E3d">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
4. Tag pages on OLPC as "Maintained at Sugar Labs" as of \data\ with<br>
link to Sugar Labs page</blockquote></div><div><br>Please only do this when it's clear that there is just one page being maintained and updated -- then add more than a tag; a full-page template that changes the background of the mirror page, saying "please go /here/ to update" is clearest. For an exapmle, see the Help: pages on any wikipedia, which point to <a href="http://meta.wikimedia.org" target="_blank">meta.wikimedia.org</a> for the latest version.<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
5. Import pages into correct place on <a href="http://wiki.sl" target="_blank">wiki.sl</a> heirarchy.<br>
6. sleep several days<br>
7. restart loop<br>
/end loop/<br>
</blockquote></div><div><br>You might want to measure out your sleep more carefully.<br> <br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
/for each loop/<br>
1. After brief waiting period, (1 week?) update links to original olpc<br>
pages with an interwiki link to new location at Sugar Labs.</blockquote></div><div><br>A proper interwiki map can help make [[sugar:TITLE]] and [[olpc:TITLE]] do the right thing.<br> </div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
2. After a second brief wait, (1 more week) replace original contents<br>
at olpc with a redirect to new location.</blockquote></div><div><br>I don't think this is the right thing to do -- for most of the pages I can imagine in the above modules, the olpc page should include a short description and a link to details; at worst a number of specific subpages can be merged into a higher-level page, but each module will likely still want a couple pages @ olpc with a different lens into the information @ slwiki.<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3. Request deletion of original page at olpc.<br>
<div></div></blockquote></div><div><br>If the original page was at all interesting, it's better to leave a soft redirect. deleted pages break links on the wider web, which we don't want to do.<br> <br> </div><div class="Ih2E3d">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>> Bernie, I thought we installed the latest?<br>
<br>
</div>Sorry, <a href="http://sugarlabs.org" target="_blank">sugarlabs.org</a> is running 1.12. I thought it was 1.5 last night<br>
when I was attempting to debug my bot login.<br>
</blockquote></div><div><br><br>SJ<br><br></div></div><br>
</div><br>