<div class="gmail_quote"><div>Hi Christoph -<br>Thanks for the query. We've been talking with David Farning and Walter Bender about the doc needs - and we've decided to do a lot of action the first week of March when a handful of us from FLOSS Manuals are at WinterCamp in Amsterdam.<br>
<br>We'll likely store off all the existing doc and mark it as 8.2 doc. Then we'll revise the Sugar guide and the Turtle Art manual as first priorities. <br><br>I would still like someone to point me to a git location where I can refresh the Help Activity. I think if I play around with git long enough I'd figure it out, but it sounds like I also need permissions. So if someone can help me with that, that'd be great. <br>
<br>I've also re-freshed the PDF file so that it can be sold on Amazon (yet another delay due to the page size) and Adam will update the pretty PDF at <a href="http://en.flossmanuals.net/publish/PDF/g1g1_2.pdf">http://en.flossmanuals.net/publish/PDF/g1g1_2.pdf</a> soon.<br>
<br>I just went on wiki.laptop.or to update some of the doc pages and will do the same on the Sugar Labs wiki as well so that people can easily step in and help, once we get our source files settled the first week of March. <br>
<br>Thanks,<br>Anne<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;">----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 17 Feb 2009 03:32:17 +0100<br>
From: Christoph Derndorfer <<a href="mailto:e0425826@student.tuwien.ac.at">e0425826@student.tuwien.ac.at</a>><br>
Subject: [OLPC library] Updating Sugar documentation for release 0.84<br>
To: Library-OLPC <<a href="mailto:library@lists.laptop.org">library@lists.laptop.org</a>><br>
Cc: iaep <<a href="mailto:iaep@lists.sugarlabs.org">iaep@lists.sugarlabs.org</a>>, Grassroots OLPC<br>
<<a href="mailto:grassroots@lists.laptop.org">grassroots@lists.laptop.org</a>><br>
Message-ID: <<a href="mailto:499A21B1.3000707@student.tuwien.ac.at">499A21B1.3000707@student.tuwien.ac.at</a>><br>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed<br>
<br>
Hi all,<br>
<br>
as some of you might be aware a new Sugar release - 0.84 - is going to<br>
be released at the beginning of March. So I thought it would a good time<br>
to start discussing how to update Sugar documentation to consider the<br>
changes and new features.<br>
<br>
Off the top of my head I can think of the following places which contain<br>
documentation that needs an overhaul:<br>
<br>
* <a href="http://wiki.sugarlabs.org" target="_blank">wiki.sugarlabs.org</a><br>
* FlossManuals<br>
* Help-Activity<br>
<br>
(Probably the most widely asked question will be "How can I upgrade my<br>
XO to Sugar 0.84?" so this might be worth also putting on the Sugar Labs<br>
landing page and spread via the various developer blogs.)<br>
<br>
I think a relatively short and remote (but well planned!) weekend-sprint<br>
would go a long way in getting the necessary work done!<br>
<br>
Before that can happen though we would need to decide how to fork the<br>
existing documentation and make it *very clear* that going forward there<br>
will be different versions of Sugar made available by OLPC and Sugar Labs.<br>
<br>
I still have a very limited understanding of what exactly this entails<br>
and how it's going to work out but as far as the FlossManuals and<br>
Help-Activity documentation is concerned making clearly distinct<br>
versions - one for OLPC's 8.2.x releases and another one for Sugar Labs'<br>
0.8x releases - seems like a reasonable starting point for me.<br>
<br>
Anyway, please let me know what you think and how we can make this<br>
happen! :-)<br>
<br>
Cheers,<br>
Christoph<br>
<br>
--<br>
Christoph Derndorfer<br>
co-editor, olpcnews<br>
url: <a href="http://www.olpcnews.com" target="_blank">www.olpcnews.com</a><br>
e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 16 Feb 2009 22:09:48 -0500<br>
From: Walter Bender <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>><br>
Subject: Re: [OLPC library] [IAEP] Updating Sugar documentation for<br>
release 0.84<br>
To: Christoph Derndorfer <<a href="mailto:e0425826@student.tuwien.ac.at">e0425826@student.tuwien.ac.at</a>><br>
Cc: Library-OLPC <<a href="mailto:library@lists.laptop.org">library@lists.laptop.org</a>>, iaep<br>
<<a href="mailto:iaep@lists.sugarlabs.org">iaep@lists.sugarlabs.org</a>>, Grassroots OLPC<br>
<<a href="mailto:grassroots@lists.laptop.org">grassroots@lists.laptop.org</a>><br>
Message-ID:<br>
<<a href="mailto:fd535e260902161909v3660e6edo47547a6b5abf413d@mail.gmail.com">fd535e260902161909v3660e6edo47547a6b5abf413d@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
The FLOSS Manual team how best to handle the changes to the Sugar<br>
Manual. Our plan is to archive the 0.82 manual and update to 0.84.<br>
<br>
-walter<br>
<br>
On Mon, Feb 16, 2009 at 9:32 PM, Christoph Derndorfer<br>
<<a href="mailto:e0425826@student.tuwien.ac.at">e0425826@student.tuwien.ac.at</a>> wrote:<br>
> Hi all,<br>
><br>
> as some of you might be aware a new Sugar release - 0.84 - is going to<br>
> be released at the beginning of March. So I thought it would a good time<br>
> to start discussing how to update Sugar documentation to consider the<br>
> changes and new features.<br>
><br>
> Off the top of my head I can think of the following places which contain<br>
> documentation that needs an overhaul:<br>
><br>
> * <a href="http://wiki.sugarlabs.org" target="_blank">wiki.sugarlabs.org</a><br>
> * FlossManuals<br>
> * Help-Activity<br>
><br>
> (Probably the most widely asked question will be "How can I upgrade my<br>
> XO to Sugar 0.84?" so this might be worth also putting on the Sugar Labs<br>
> landing page and spread via the various developer blogs.)<br>
><br>
> I think a relatively short and remote (but well planned!) weekend-sprint<br>
> would go a long way in getting the necessary work done!<br>
><br>
> Before that can happen though we would need to decide how to fork the<br>
> existing documentation and make it *very clear* that going forward there<br>
> will be different versions of Sugar made available by OLPC and Sugar Labs.<br>
><br>
> I still have a very limited understanding of what exactly this entails<br>
> and how it's going to work out but as far as the FlossManuals and<br>
> Help-Activity documentation is concerned making clearly distinct<br>
> versions - one for OLPC's 8.2.x releases and another one for Sugar Labs'<br>
> 0.8x releases - seems like a reasonable starting point for me.<br>
><br>
> Anyway, please let me know what you think and how we can make this<br>
> happen! :-)<br>
><br>
> Cheers,<br>
> Christoph<br>
><br>
> --<br>
> Christoph Derndorfer<br>
> co-editor, olpcnews<br>
> url: <a href="http://www.olpcnews.com" target="_blank">www.olpcnews.com</a><br>
> e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br>
><br>
><br>
> _______________________________________________<br>
> IAEP -- It's An Education Project (not a laptop project!)<br>
> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
><br>
<br>
<br>
<br>
--<br>
Walter Bender<br>
Sugar Labs<br>
<a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Library mailing list<br>
<a href="mailto:Library@lists.laptop.org">Library@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/library" target="_blank">http://lists.laptop.org/listinfo/library</a><br>
<br>
<br>
End of Library Digest, Vol 23, Issue 7<br>
**************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Anne Gentle<br>email: <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>blog: <a href="http://www.justwriteclick.com">www.justwriteclick.com</a><br>