<div dir="ltr">On Tue, Sep 2, 2008 at 12:05 PM, David Farning <span dir="ltr"><<a href="mailto:dfarning@sugarlabs.org">dfarning@sugarlabs.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1. Create <a href="mailto:Sugar-devel@sugarlabs.org">Sugar-devel@sugarlabs.org</a> mailing list. We have discussed<br>
this a few time over the last few months. Now that we are getting<br>
distro (other the OLPC) related comments the time seems right<br>
<br>
2. Create <a href="mailto:Activities-devel@sugarlabs.org">Activities-devel@sugarlabs.org</a> mailing list. This will focus<br>
on activity developer related issues.<br>
</blockquote><div><br>Please don't fork sugar and activities lists without need! Regardless of where these lists are hosted, we should have one of each. olpc already has a general olpc-only devel list, the sugar and activities lists aren't meant to be so restricted. <br>
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3. Improve API documentation. Last week at the Book Sprint, I met a<br>
professional writer who does Python api documentation for a living. She<br>
is willing to help us get our documentation processes set up and get us<br>
started.<br>
</blockquote><div><br>+1<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
4. Work on the getting involved documentation on the Sugar Wiki.<br>
<br>
5. Move the Sugar documentation from w.l.o to w.s.o. When I started<br>
this move a few moths ago, I am afraid that it was seen as a power grab<br>
for Sugar Labs. I will restart this move if I receive buy-in and<br>
support from OLPC personal.<br>
</blockquote><div><br>As I mentioned then, we should pool bot expertise and set up some good bots. <br>There is a reasonable tradition of soft redirects -- preserving existing pages and first adding a header that says "this is a mirror of info at <link>, to edit or see the latest info please go to <source site>", then replacing that text with a template that indicatesd the cross-site redirect. [you don't want to remove the original since inbound links point to it]<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">6. Using AMO as an activities server. There are many advantages to<br>
using Amo as an activity server. The issues that i ran into was the need<br>
to push some patches back to mozilla to abstract the types of files AMO<br>
serves. With the patch set, modifing amo to meet our needs would be<br>
pretty straight forward. Without the patches being accepted we would<br>
have to fork the code amo codebase.<br>
</blockquote><div><br>Does amo provide a way for visitors/users to export data from it?<br> <br>SJ<br></div></div><br></div>