Re: Documentation Sprint

[Rohit Joshi <rj.rohit@xxxxxxxxx>]

Hi Ben,

Seems like we are doing things concurrently. Great !!

But, why wait till August?? Lets get started asap (before the world cup).
We have already discussed among ourselves and given thumbs up to the idea.

I think lets just give everybody freedom to improve/add/edit any wiki
pages. Every page can be read and reviewed by anyone.

Once the wiki documentation is written, we will pen down the process
of reviewing.
What do you think??

I am planning to announce it on the website asap.

Thanks

Rohit

PS: Please take care of "namespaces" in wiki.

On Mon, May 3, 2010 at 5:23 PM, Ben Arnold <iamseawolf@xxxxxxxxx> wrote:
> Hi Rohit & all --
>
>
> Thanks for the encouragement! I've started a page [1] to outline the
> doc-sprint (1). I welcome any comments, especially on the way its
> structured or if foresee any problems with it. I hope to have every
> wiki page linked there to organise them but each individual page
> should have the details.
>
> I used a wiki page as its probably the best way to get the process
> discussed and sorted, over a forum thread; it'll hopefully encourage
> more direct action in the shortish time span. On that note, do you all
> think August would be a good time to announce initially? Is there
> anything planned then? It gives enough time to prep & plan, plus it
> lets exams etc. get out the way along with, of course, the World Cup
> :)
>
> I'm happy to put my time where my mouth is & lead this; I understand
> the devs have enough work to do!
>
>
> Thanks!
> Ben
>
> --
>
>  1:  http://doc.slitaz.org/en:scratchbook:docsprint
>
> --
>
> Ben Arnold
> Chester, UK
>
> e: ben at seawolfsanctuary.com
> w: seawolfsanctuary.com | t: @seawolf
>
> nom = { :cookies => :mouth }
> nom; nom; nom
>
>
> On Tuesday 20 April 2010 17:56:27 Rohit Joshi wrote:
>> Hi Ben,
>>
>> +1 for the idea. Yeah, get the ball rolling before the world cup
>> fever grips everyone :-)
>>
>> On Tue, Apr 20, 2010, Ben Arnold <iamseawolf@xxxxxxxxx> wrote:
>> > I reckon we can get the ball rolling by identifying the most
>> > important, or most visible, pages to update first, as suggested
>> > by @jpeg. Things like Xorg & hardware set-up spring immediately
>> > to mind, as they've changed dramatically recently with kernel &
>> > software updates. Those will probably need a bit more work than
>> > others that call only for reading and checking. A 'junior jobs'
>> > list could be created to encourage time-constrained/newer users
>> > to contribute. A "this page has been confirmed correct!" box at
>> > the head of each page could it has been reviewed.
>

---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/