Re: [Sugar-devel] Google Season of Docs

[Jui Pradhan]

Hi,
 Apologies for the late reply.
Apart from all that which was already mentioned, I think we suffer from the
problem of scattered documentation/duplicated documentation. We might take
this opportunity to have structured documentation. By that, I mean removing
the duplicated documentation/ having the exact same documentation at both
places.
For example, the help activity has documentation for few activities, the
wiki page has documentation too. There are few activities which aren't
mentioned at all. Besides, we see new developers constantly seeking help
from the community to point them to documentation for contributing. In
short, the documentation is incomplete, scattered or duplicated.

Also, I support the idea of having supporting documentation for teachers.

Thanks.
Regards,
Jui

On Wed, Feb 17, 2021 at 4:46 AM Walter Bender 
wrote:

> On Mon, Feb 15, 2021 at 7:34 PM James Cameron  wrote:
> >
> > Thanks.  I agree.
> >
> > Would a technical writer alone be suitable, or must a technical writer
> > be combined with a teacher?  There's a risk that by placing domain
> > specific limitations on the project, we make it harder for GSoD to
> > choose us.
>
> I think we can provide the pedagogical support via mentoring much the
> way we provide programming support via mentoring.
>
> We have some very experienced people, e.g., Claudia, in our ranks.
>
> >
> > What mode of delivery is best suited to teachers; written manuals,
> > lesson plans, onscreen walkthroughs, or stand up lectures?  There's a
> > risk that GSoD candidates will concentrate on written documentation.
>
> I think lesson plans are a great place to start and can serve as a
> backbone for the modalities.
>
> >
> > How do we emphasise constructivism, constructionism, or constructivist
> > teaching methods?  Is there a degree or certification we can require?
>
> I don't think the writer needs to come with those skills but can learn
> from some good examples from the contructionsist community.
>
> >
> > On Mon, Feb 15, 2021 at 06:52:53PM -0500, Walter Bender wrote:
> > > Apologies for my late response to this thread.
> > >
> > > Regarding documentation, I think we have a major hole to fill in
> > > Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
> > > While we have docs for the individual components, we could go a long
> > > ways towards giving some structure to a teacher who might want to
> > > build a comprehensive program out of any of our major subsystems.
> > >
> > > -walter
> > >
> > > On Wed, Feb 10, 2021 at 4:31 AM James Cameron 
> wrote:
> > > >
> > > > Yes.  Please make a list of content if none is available and content
> > > > that should be demystified?
> > > >
> > > > On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > > > > Anyone can correct me if I am wrong. But the point of Season of
> Docs is
> > > > >
> > > > > 1. Generate content if none is available.
> > > > > 2. Very important is looking at the existing content and demystify
> it to the
> > > > > nearest minimum (Sugar Labs needs this)
> > > > >
> > > > > The idea for a technical writer is to simplify and transfer
> information between
> > > > > Sugar Labs and anyone consuming the content.
> > > > >
> > > > > To you, the content may look fine because you may not be the
> target, or in this
> > > > > case, you are an author of some of the tools generated.
> > > > >
> > > > > Having great doc is a demanding requirement for onboarding in open
> source, and
> > > > > unfortunately, I can't say Sugar Labs has one(simplifications).
> > > > >
> > > > > Also a completely different from GSoC.
> > > > >
> > > > > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org>
> wrote:
> > > > >
> > > > > My first question was the most important.
> > > > >
> > > > > I can't think of any documentation Sugar Labs needs that we
> haven't
> > > > > already got in some form or other across our sprawling web
> presence.
> > > > >
> > > > > I recommend against proceeding unless some documentation is
> needed.
> > > > >
> > > > > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > > > > Hello James,
> > > > > >
> > > > > > I read the documentation, yes it looks like a grant based
> program this
> > > > > time
> > > > > > around.
> > > > > >
> > > > > > Just as I mentioned last year, I would love to admin the
> program, or be
> > > > > one of
> > > > > > the admins.
> > > > > >
> > > > > > I am working on a system in place already.
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]
> qu...@laptop.org>
> > > > > wrote:
> > > > > >
> > > > > > Indeed.  So the question becomes;
> > > > > >
> > > > > > - what documentation does Sugar Labs need (e.g. for
> Sugarizer, Music
> > > > > >   Blocks, or Sugar); this forms part of a project
> proposal,
> > > > > >
> > > > > 

Re: [Sugar-devel] Google Season of Docs

[Walter Bender]

On Mon, Feb 15, 2021 at 7:34 PM James Cameron  wrote:
>
> Thanks.  I agree.
>
> Would a technical writer alone be suitable, or must a technical writer
> be combined with a teacher?  There's a risk that by placing domain
> specific limitations on the project, we make it harder for GSoD to
> choose us.

I think we can provide the pedagogical support via mentoring much the
way we provide programming support via mentoring.

We have some very experienced people, e.g., Claudia, in our ranks.

>
> What mode of delivery is best suited to teachers; written manuals,
> lesson plans, onscreen walkthroughs, or stand up lectures?  There's a
> risk that GSoD candidates will concentrate on written documentation.

I think lesson plans are a great place to start and can serve as a
backbone for the modalities.

>
> How do we emphasise constructivism, constructionism, or constructivist
> teaching methods?  Is there a degree or certification we can require?

I don't think the writer needs to come with those skills but can learn
from some good examples from the contructionsist community.

>
> On Mon, Feb 15, 2021 at 06:52:53PM -0500, Walter Bender wrote:
> > Apologies for my late response to this thread.
> >
> > Regarding documentation, I think we have a major hole to fill in
> > Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
> > While we have docs for the individual components, we could go a long
> > ways towards giving some structure to a teacher who might want to
> > build a comprehensive program out of any of our major subsystems.
> >
> > -walter
> >
> > On Wed, Feb 10, 2021 at 4:31 AM James Cameron  wrote:
> > >
> > > Yes.  Please make a list of content if none is available and content
> > > that should be demystified?
> > >
> > > On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > > > Anyone can correct me if I am wrong. But the point of Season of Docs is
> > > >
> > > > 1. Generate content if none is available.
> > > > 2. Very important is looking at the existing content and demystify it 
> > > > to the
> > > > nearest minimum (Sugar Labs needs this)
> > > >
> > > > The idea for a technical writer is to simplify and transfer information 
> > > > between
> > > > Sugar Labs and anyone consuming the content.
> > > >
> > > > To you, the content may look fine because you may not be the target, or 
> > > > in this
> > > > case, you are an author of some of the tools generated.
> > > >
> > > > Having great doc is a demanding requirement for onboarding in open 
> > > > source, and
> > > > unfortunately, I can't say Sugar Labs has one(simplifications).
> > > >
> > > > Also a completely different from GSoC.
> > > >
> > > > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> > > >
> > > > My first question was the most important.
> > > >
> > > > I can't think of any documentation Sugar Labs needs that we haven't
> > > > already got in some form or other across our sprawling web presence.
> > > >
> > > > I recommend against proceeding unless some documentation is needed.
> > > >
> > > > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > > > Hello James,
> > > > >
> > > > > I read the documentation, yes it looks like a grant based program 
> > > > this
> > > > time
> > > > > around.
> > > > >
> > > > > Just as I mentioned last year, I would love to admin the program, 
> > > > or be
> > > > one of
> > > > > the admins.
> > > > >
> > > > > I am working on a system in place already.
> > > > >
> > > > > Regards
> > > > >
> > > > > On Wed, Feb 10, 2021, 9:33 AM James Cameron 
> > > > <[1][2]qu...@laptop.org>
> > > > wrote:
> > > > >
> > > > > Indeed.  So the question becomes;
> > > > >
> > > > > - what documentation does Sugar Labs need (e.g. for 
> > > > Sugarizer, Music
> > > > >   Blocks, or Sugar); this forms part of a project proposal,
> > > > >
> > > > > - who will recruit, evaluate, and onboard a technical writer?
> > > > >
> > > > > - who will administer the program in Sugar Labs?
> > > > >
> > > > > 
> > > > [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> > > > >
> > > > > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > > > > > It is being organized differently this year; we have to 
> > > > apply for a
> > > > grant
> > > > > and
> > > > > > then we find the writer we reach out directly to the writer 
> > > > we want
> > > > to
> > > > > work
> > > > > > with, at least that is how I understood it.
> > > > > >
> > > > > > [1][3][4]https://opensource.googleblog.com/2021/02/
> > > > > > 
> > > > the-2021-season-of-docs-application-for-organizations-is-open.html?
> > > > m=1
> > > > > >
> > > > > > [2][4][5]https://developers.google.com/season-of-docs/docs/
> > > 

Re: [Sugar-devel] Google Season of Docs

[Chihurumnaya Ibiam]

A technical writer alone wouldn't be suitable hence we have a community for
anything more that's needed and I think the idea is the technical writer
could create a
template of sorts that any teacher can base any of their lesson plans .etc.
on as that seems
easier as it enables the teacher setup what they want with a frame of
reference.

-- 

Ibiam Chihurumnaya
ibiamchihurumn...@gmail.com



On Tue, Feb 16, 2021 at 1:34 AM James Cameron  wrote:

> Thanks.  I agree.
>
> Would a technical writer alone be suitable, or must a technical writer
> be combined with a teacher?  There's a risk that by placing domain
> specific limitations on the project, we make it harder for GSoD to
> choose us.
>
> What mode of delivery is best suited to teachers; written manuals,
> lesson plans, onscreen walkthroughs, or stand up lectures?  There's a
> risk that GSoD candidates will concentrate on written documentation.
>
> How do we emphasise constructivism, constructionism, or constructivist
> teaching methods?  Is there a degree or certification we can require?
>
> On Mon, Feb 15, 2021 at 06:52:53PM -0500, Walter Bender wrote:
> > Apologies for my late response to this thread.
> >
> > Regarding documentation, I think we have a major hole to fill in
> > Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
> > While we have docs for the individual components, we could go a long
> > ways towards giving some structure to a teacher who might want to
> > build a comprehensive program out of any of our major subsystems.
> >
> > -walter
> >
> > On Wed, Feb 10, 2021 at 4:31 AM James Cameron  wrote:
> > >
> > > Yes.  Please make a list of content if none is available and content
> > > that should be demystified?
> > >
> > > On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > > > Anyone can correct me if I am wrong. But the point of Season of Docs
> is
> > > >
> > > > 1. Generate content if none is available.
> > > > 2. Very important is looking at the existing content and demystify
> it to the
> > > > nearest minimum (Sugar Labs needs this)
> > > >
> > > > The idea for a technical writer is to simplify and transfer
> information between
> > > > Sugar Labs and anyone consuming the content.
> > > >
> > > > To you, the content may look fine because you may not be the target,
> or in this
> > > > case, you are an author of some of the tools generated.
> > > >
> > > > Having great doc is a demanding requirement for onboarding in open
> source, and
> > > > unfortunately, I can't say Sugar Labs has one(simplifications).
> > > >
> > > > Also a completely different from GSoC.
> > > >
> > > > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org>
> wrote:
> > > >
> > > > My first question was the most important.
> > > >
> > > > I can't think of any documentation Sugar Labs needs that we
> haven't
> > > > already got in some form or other across our sprawling web
> presence.
> > > >
> > > > I recommend against proceeding unless some documentation is
> needed.
> > > >
> > > > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > > > Hello James,
> > > > >
> > > > > I read the documentation, yes it looks like a grant based
> program this
> > > > time
> > > > > around.
> > > > >
> > > > > Just as I mentioned last year, I would love to admin the
> program, or be
> > > > one of
> > > > > the admins.
> > > > >
> > > > > I am working on a system in place already.
> > > > >
> > > > > Regards
> > > > >
> > > > > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]
> qu...@laptop.org>
> > > > wrote:
> > > > >
> > > > > Indeed.  So the question becomes;
> > > > >
> > > > > - what documentation does Sugar Labs need (e.g. for
> Sugarizer, Music
> > > > >   Blocks, or Sugar); this forms part of a project proposal,
> > > > >
> > > > > - who will recruit, evaluate, and onboard a technical
> writer?
> > > > >
> > > > > - who will administer the program in Sugar Labs?
> > > > >
> > > > > [2][3]
> https://developers.google.com/season-of-docs/docs/admin-guide
> > > > >
> > > > > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin
> wrote:
> > > > > > It is being organized differently this year; we have to
> apply for a
> > > > grant
> > > > > and
> > > > > > then we find the writer we reach out directly to the
> writer we want
> > > > to
> > > > > work
> > > > > > with, at least that is how I understood it.
> > > > > >
> > > > > > [1][3][4]https://opensource.googleblog.com/2021/02/
> > > > > >
> the-2021-season-of-docs-application-for-organizations-is-open.html?
> > > > m=1
> > > > > >
> > > > > > [2][4][5]
> https://developers.google.com/season-of-docs/docs/
> > > > tech-writer-guide
> > > > > >
> > > > > > On Wed, 10 Feb 2021, 06:18 

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Thanks.  I agree.

Would a technical writer alone be suitable, or must a technical writer
be combined with a teacher?  There's a risk that by placing domain
specific limitations on the project, we make it harder for GSoD to
choose us.

What mode of delivery is best suited to teachers; written manuals,
lesson plans, onscreen walkthroughs, or stand up lectures?  There's a
risk that GSoD candidates will concentrate on written documentation.

How do we emphasise constructivism, constructionism, or constructivist
teaching methods?  Is there a degree or certification we can require?

On Mon, Feb 15, 2021 at 06:52:53PM -0500, Walter Bender wrote:
> Apologies for my late response to this thread.
> 
> Regarding documentation, I think we have a major hole to fill in
> Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
> While we have docs for the individual components, we could go a long
> ways towards giving some structure to a teacher who might want to
> build a comprehensive program out of any of our major subsystems.
> 
> -walter
> 
> On Wed, Feb 10, 2021 at 4:31 AM James Cameron  wrote:
> >
> > Yes.  Please make a list of content if none is available and content
> > that should be demystified?
> >
> > On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > > Anyone can correct me if I am wrong. But the point of Season of Docs is
> > >
> > > 1. Generate content if none is available.
> > > 2. Very important is looking at the existing content and demystify it to 
> > > the
> > > nearest minimum (Sugar Labs needs this)
> > >
> > > The idea for a technical writer is to simplify and transfer information 
> > > between
> > > Sugar Labs and anyone consuming the content.
> > >
> > > To you, the content may look fine because you may not be the target, or 
> > > in this
> > > case, you are an author of some of the tools generated.
> > >
> > > Having great doc is a demanding requirement for onboarding in open 
> > > source, and
> > > unfortunately, I can't say Sugar Labs has one(simplifications).
> > >
> > > Also a completely different from GSoC.
> > >
> > > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> > >
> > > My first question was the most important.
> > >
> > > I can't think of any documentation Sugar Labs needs that we haven't
> > > already got in some form or other across our sprawling web presence.
> > >
> > > I recommend against proceeding unless some documentation is needed.
> > >
> > > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > > Hello James,
> > > >
> > > > I read the documentation, yes it looks like a grant based program 
> > > this
> > > time
> > > > around.
> > > >
> > > > Just as I mentioned last year, I would love to admin the program, 
> > > or be
> > > one of
> > > > the admins.
> > > >
> > > > I am working on a system in place already.
> > > >
> > > > Regards
> > > >
> > > > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]qu...@laptop.org>
> > > wrote:
> > > >
> > > > Indeed.  So the question becomes;
> > > >
> > > > - what documentation does Sugar Labs need (e.g. for Sugarizer, 
> > > Music
> > > >   Blocks, or Sugar); this forms part of a project proposal,
> > > >
> > > > - who will recruit, evaluate, and onboard a technical writer?
> > > >
> > > > - who will administer the program in Sugar Labs?
> > > >
> > > > 
> > > [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> > > >
> > > > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > > > > It is being organized differently this year; we have to apply 
> > > for a
> > > grant
> > > > and
> > > > > then we find the writer we reach out directly to the writer 
> > > we want
> > > to
> > > > work
> > > > > with, at least that is how I understood it.
> > > > >
> > > > > [1][3][4]https://opensource.googleblog.com/2021/02/
> > > > > 
> > > the-2021-season-of-docs-application-for-organizations-is-open.html?
> > > m=1
> > > > >
> > > > > [2][4][5]https://developers.google.com/season-of-docs/docs/
> > > tech-writer-guide
> > > > >
> > > > > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5][6]
> > > 2017...@iiitdmj.ac.in>
> > > > wrote:
> > > > >
> > > > > I think it is a great idea. Sugar labs should take part in
> > > GSoD.
> > > > >
> > > > > Regards
> > > > > Saumya Mishra
> > > > >
> > > > > On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4][6][7]
> > > qu...@laptop.org
> > > > > wrote:
> > > > >
> > > > > It's back.  Can we win a slot this year?  Ideas 
> > > welcome.
> > > > >
> > > > > 

Re: [Sugar-devel] Google Season of Docs

[Walter Bender]

Apologies for my late response to this thread.

Regarding documentation, I think we have a major hole to fill in
Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
While we have docs for the individual components, we could go a long
ways towards giving some structure to a teacher who might want to
build a comprehensive program out of any of our major subsystems.

-walter

On Wed, Feb 10, 2021 at 4:31 AM James Cameron  wrote:
>
> Yes.  Please make a list of content if none is available and content
> that should be demystified?
>
> On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > Anyone can correct me if I am wrong. But the point of Season of Docs is
> >
> > 1. Generate content if none is available.
> > 2. Very important is looking at the existing content and demystify it to the
> > nearest minimum (Sugar Labs needs this)
> >
> > The idea for a technical writer is to simplify and transfer information 
> > between
> > Sugar Labs and anyone consuming the content.
> >
> > To you, the content may look fine because you may not be the target, or in 
> > this
> > case, you are an author of some of the tools generated.
> >
> > Having great doc is a demanding requirement for onboarding in open source, 
> > and
> > unfortunately, I can't say Sugar Labs has one(simplifications).
> >
> > Also a completely different from GSoC.
> >
> > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> >
> > My first question was the most important.
> >
> > I can't think of any documentation Sugar Labs needs that we haven't
> > already got in some form or other across our sprawling web presence.
> >
> > I recommend against proceeding unless some documentation is needed.
> >
> > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > Hello James,
> > >
> > > I read the documentation, yes it looks like a grant based program this
> > time
> > > around.
> > >
> > > Just as I mentioned last year, I would love to admin the program, or 
> > be
> > one of
> > > the admins.
> > >
> > > I am working on a system in place already.
> > >
> > > Regards
> > >
> > > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]qu...@laptop.org>
> > wrote:
> > >
> > > Indeed.  So the question becomes;
> > >
> > > - what documentation does Sugar Labs need (e.g. for Sugarizer, 
> > Music
> > >   Blocks, or Sugar); this forms part of a project proposal,
> > >
> > > - who will recruit, evaluate, and onboard a technical writer?
> > >
> > > - who will administer the program in Sugar Labs?
> > >
> > > 
> > [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> > >
> > > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > > > It is being organized differently this year; we have to apply 
> > for a
> > grant
> > > and
> > > > then we find the writer we reach out directly to the writer we 
> > want
> > to
> > > work
> > > > with, at least that is how I understood it.
> > > >
> > > > [1][3][4]https://opensource.googleblog.com/2021/02/
> > > > 
> > the-2021-season-of-docs-application-for-organizations-is-open.html?
> > m=1
> > > >
> > > > [2][4][5]https://developers.google.com/season-of-docs/docs/
> > tech-writer-guide
> > > >
> > > > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5][6]
> > 2017...@iiitdmj.ac.in>
> > > wrote:
> > > >
> > > > I think it is a great idea. Sugar labs should take part in
> > GSoD.
> > > >
> > > > Regards
> > > > Saumya Mishra
> > > >
> > > > On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4][6][7]
> > qu...@laptop.org
> > > > wrote:
> > > >
> > > > It's back.  Can we win a slot this year?  Ideas welcome.
> > > >
> > > > [5][7][8]https://opensource.googleblog.com/2021/02/
> > > >
> > >  
> > the-2021-season-of-docs-application-for-organizations-is-open.html
> > > > [6][8][9]https://developers.google.com/season-of-docs
> > > >
> > > > --
> > > > James Cameron
> > > > [7][9][10]https://quozl.linux.org.au/
> > > > ___
> > > > Sugar-devel mailing list
> > > > [8][10][11]Sugar-devel@lists.sugarlabs.org
> > > > 
> > [9][11][12]http://lists.sugarlabs.org/listinfo/sugar-devel
> > > >
> > > > ___
> > > > Sugar-devel mailing list
> > > > [10][12][13]Sugar-devel@lists.sugarlabs.org
> > > > [11][13][14]http://lists.sugarlabs.org/listinfo/sugar-devel
> >  

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Yes.  Please make a list of content if none is available and content
that should be demystified?

On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> Anyone can correct me if I am wrong. But the point of Season of Docs is 
> 
> 1. Generate content if none is available. 
> 2. Very important is looking at the existing content and demystify it to the
> nearest minimum (Sugar Labs needs this)
> 
> The idea for a technical writer is to simplify and transfer information 
> between
> Sugar Labs and anyone consuming the content. 
> 
> To you, the content may look fine because you may not be the target, or in 
> this
> case, you are an author of some of the tools generated. 
> 
> Having great doc is a demanding requirement for onboarding in open source, and
> unfortunately, I can't say Sugar Labs has one(simplifications). 
> 
> Also a completely different from GSoC. 
> 
> On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> My first question was the most important.
> 
> I can't think of any documentation Sugar Labs needs that we haven't
> already got in some form or other across our sprawling web presence.
> 
> I recommend against proceeding unless some documentation is needed.
> 
> On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > Hello James,
> >
> > I read the documentation, yes it looks like a grant based program this
> time
> > around.
> >
> > Just as I mentioned last year, I would love to admin the program, or be
> one of
> > the admins. 
> >
> > I am working on a system in place already. 
> >
> > Regards
> >
> > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]qu...@laptop.org>
> wrote:
> >
> >     Indeed.  So the question becomes;
> >
> >     - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
> >       Blocks, or Sugar); this forms part of a project proposal,
> >
> >     - who will recruit, evaluate, and onboard a technical writer?
> >
> >     - who will administer the program in Sugar Labs?
> >
> >     [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> >
> >     On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> >     > It is being organized differently this year; we have to apply for 
> a
> grant
> >     and
> >     > then we find the writer we reach out directly to the writer we 
> want
> to
> >     work
> >     > with, at least that is how I understood it. 
> >     >
> >     > [1][3][4]https://opensource.googleblog.com/2021/02/
> >     > 
> the-2021-season-of-docs-application-for-organizations-is-open.html?
> m=1
> >     >
> >     > [2][4][5]https://developers.google.com/season-of-docs/docs/
> tech-writer-guide
> >     >
> >     > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5][6]
> 2017...@iiitdmj.ac.in>
> >     wrote:
> >     >
> >     >     I think it is a great idea. Sugar labs should take part in
> GSoD.
> >     >
> >     >     Regards
> >     >     Saumya Mishra
> >     >
> >     >     On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4][6][7]
> qu...@laptop.org
> >     > wrote:
> >     >
> >     >         It's back.  Can we win a slot this year?  Ideas welcome.
> >     >
> >     >         [5][7][8]https://opensource.googleblog.com/2021/02/
> >     >       
> >      the-2021-season-of-docs-application-for-organizations-is-open.html
> >     >         [6][8][9]https://developers.google.com/season-of-docs
> >     >
> >     >         --
> >     >         James Cameron
> >     >         [7][9][10]https://quozl.linux.org.au/
> >     >         ___
> >     >         Sugar-devel mailing list
> >     >         [8][10][11]Sugar-devel@lists.sugarlabs.org
> >     >         [9][11][12]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     >
> >     >     ___
> >     >     Sugar-devel mailing list
> >     >     [10][12][13]Sugar-devel@lists.sugarlabs.org
> >     >     [11][13][14]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     >
> >     > References:
> >     >
> >     > [1] [14][15]https://opensource.googleblog.com/2021/02/
> >     
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=
> 1
> >     > [2] [15][16]https://developers.google.com/season-of-docs/docs/
> >     tech-writer-guide
> >     > [3] mailto:[16][17]2017...@iiitdmj.ac.in
> >     > [4] mailto:[17][18]qu...@laptop.org
> >     > [5] [18][19]https://opensource.googleblog.com/2021/02/
> >     the-2021-season-of-docs-application-for-organizations-is-open.html
> >     > [6] [19][20]https://developers.google.com/season-of-docs
> >     > [7] 

Re: [Sugar-devel] Google Season of Docs

[Samson Goddy]

Anyone can correct me if I am wrong. But the point of Season of Docs is

1. Generate content if none is available.
2. Very important is looking at the existing content and demystify it to
the nearest minimum (Sugar Labs needs this)

The idea for a technical writer is to simplify and transfer information
between Sugar Labs and anyone consuming the content.

To you, the content may look fine because you may not be the target, or in
this case, you are an author of some of the tools generated.

Having great doc is a demanding requirement for onboarding in open source,
and unfortunately, I can't say Sugar Labs has one(simplifications).

Also a completely different from GSoC.


On Wed, Feb 10, 2021, 9:59 AM James Cameron  wrote:

> My first question was the most important.
>
> I can't think of any documentation Sugar Labs needs that we haven't
> already got in some form or other across our sprawling web presence.
>
> I recommend against proceeding unless some documentation is needed.
>
> On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > Hello James,
> >
> > I read the documentation, yes it looks like a grant based program this
> time
> > around.
> >
> > Just as I mentioned last year, I would love to admin the program, or be
> one of
> > the admins.
> >
> > I am working on a system in place already.
> >
> > Regards
> >
> > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1]qu...@laptop.org> wrote:
> >
> > Indeed.  So the question becomes;
> >
> > - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
> >   Blocks, or Sugar); this forms part of a project proposal,
> >
> > - who will recruit, evaluate, and onboard a technical writer?
> >
> > - who will administer the program in Sugar Labs?
> >
> > [2]https://developers.google.com/season-of-docs/docs/admin-guide
> >
> > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > > It is being organized differently this year; we have to apply for
> a grant
> > and
> > > then we find the writer we reach out directly to the writer we
> want to
> > work
> > > with, at least that is how I understood it.
> > >
> > > [1][3]https://opensource.googleblog.com/2021/02/
> > >
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> > >
> > > [2][4]
> https://developers.google.com/season-of-docs/docs/tech-writer-guide
> > >
> > > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5]
> 2017...@iiitdmj.ac.in>
> > wrote:
> > >
> > > I think it is a great idea. Sugar labs should take part in
> GSoD.
> > >
> > > Regards
> > > Saumya Mishra
> > >
> > > On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4][6]
> qu...@laptop.org
> > > wrote:
> > >
> > > It's back.  Can we win a slot this year?  Ideas welcome.
> > >
> > > [5][7]https://opensource.googleblog.com/2021/02/
> > >
> >  the-2021-season-of-docs-application-for-organizations-is-open.html
> > > [6][8]https://developers.google.com/season-of-docs
> > >
> > > --
> > > James Cameron
> > > [7][9]https://quozl.linux.org.au/
> > > ___
> > > Sugar-devel mailing list
> > > [8][10]Sugar-devel@lists.sugarlabs.org
> > > [9][11]http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > > ___
> > > Sugar-devel mailing list
> > > [10][12]Sugar-devel@lists.sugarlabs.org
> > > [11][13]http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > > References:
> > >
> > > [1] [14]https://opensource.googleblog.com/2021/02/
> >
>  the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> > > [2] [15]https://developers.google.com/season-of-docs/docs/
> > tech-writer-guide
> > > [3] mailto:[16]2017...@iiitdmj.ac.in
> > > [4] mailto:[17]qu...@laptop.org
> > > [5] [18]https://opensource.googleblog.com/2021/02/
> > the-2021-season-of-docs-application-for-organizations-is-open.html
> > > [6] [19]https://developers.google.com/season-of-docs
> > > [7] [20]https://quozl.linux.org.au/
> > > [8] mailto:[21]Sugar-devel@lists.sugarlabs.org
> > > [9] [22]http://lists.sugarlabs.org/listinfo/sugar-devel
> > > [10] mailto:[23]Sugar-devel@lists.sugarlabs.org
> > > [11] [24]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [25]https://quozl.linux.org.au/
> > ___
> > Sugar-devel mailing list
> > [26]Sugar-devel@lists.sugarlabs.org
> > [27]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] mailto:qu...@laptop.org
> > [2] https://developers.google.com/season-of-docs/docs/admin-guide
> > [3] https://opensource.googleblog.com/2021/02/
> > 

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

My first question was the most important.

I can't think of any documentation Sugar Labs needs that we haven't
already got in some form or other across our sprawling web presence.

I recommend against proceeding unless some documentation is needed.

On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> Hello James,
> 
> I read the documentation, yes it looks like a grant based program this time
> around.
> 
> Just as I mentioned last year, I would love to admin the program, or be one of
> the admins. 
> 
> I am working on a system in place already. 
> 
> Regards
> 
> On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Indeed.  So the question becomes;
> 
> - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
>   Blocks, or Sugar); this forms part of a project proposal,
> 
> - who will recruit, evaluate, and onboard a technical writer?
> 
> - who will administer the program in Sugar Labs?
> 
> [2]https://developers.google.com/season-of-docs/docs/admin-guide
> 
> On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > It is being organised differently this year, we have to apply for a 
> grant
> and
> > then we find the writer we reach out directly to the writer we want to
> work
> > with, at least that is how I understood it. 
> >
> > [1][3]https://opensource.googleblog.com/2021/02/
> > the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> >
> > 
> [2][4]https://developers.google.com/season-of-docs/docs/tech-writer-guide
> >
> > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5]2017...@iiitdmj.ac.in>
> wrote:
> >
> >     I think it is a great idea. Sugar labs should take part in GSoD.
> >
> >     Regards
> >     Saumya Mishra
> >
> >     On Wed, Feb 10, 2021 at 7:05 AM James Cameron 
> <[4][6]qu...@laptop.org
> > wrote:
> >
> >         It's back.  Can we win a slot this year?  Ideas welcome.
> >
> >         [5][7]https://opensource.googleblog.com/2021/02/
> >       
>  the-2021-season-of-docs-application-for-organizations-is-open.html
> >         [6][8]https://developers.google.com/season-of-docs
> >
> >         --
> >         James Cameron
> >         [7][9]https://quozl.linux.org.au/
> >         ___
> >         Sugar-devel mailing list
> >         [8][10]Sugar-devel@lists.sugarlabs.org
> >         [9][11]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >     ___
> >     Sugar-devel mailing list
> >     [10][12]Sugar-devel@lists.sugarlabs.org
> >     [11][13]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] [14]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> > [2] [15]https://developers.google.com/season-of-docs/docs/
> tech-writer-guide
> > [3] mailto:[16]2017...@iiitdmj.ac.in
> > [4] mailto:[17]qu...@laptop.org
> > [5] [18]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html
> > [6] [19]https://developers.google.com/season-of-docs
> > [7] [20]https://quozl.linux.org.au/
> > [8] mailto:[21]Sugar-devel@lists.sugarlabs.org
> > [9] [22]http://lists.sugarlabs.org/listinfo/sugar-devel
> > [10] mailto:[23]Sugar-devel@lists.sugarlabs.org
> > [11] [24]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [25]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [26]Sugar-devel@lists.sugarlabs.org
> [27]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://developers.google.com/season-of-docs/docs/admin-guide
> [3] https://opensource.googleblog.com/2021/02/
> [4] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> [5] mailto:2017...@iiitdmj.ac.in
> [6] mailto:qu...@laptop.org
> [7] https://opensource.googleblog.com/2021/02/
> [8] https://developers.google.com/season-of-docs
> [9] https://quozl.linux.org.au/
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel
> [12] mailto:Sugar-devel@lists.sugarlabs.org
> [13] http://lists.sugarlabs.org/listinfo/sugar-devel
> [14] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> [15] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> [16] mailto:2017...@iiitdmj.ac.in
> [17] mailto:qu...@laptop.org
> [18] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> [19] https://developers.google.com/season-of-docs
> [20] 

Re: [Sugar-devel] Google Season of Docs

[Samson Goddy]

Hello James,

I read the documentation, yes it looks like a grant based program this time
around.

Just as I mentioned last year, I would love to admin the program, or be one
of the admins.

I am working on a system in place already.


Regards

On Wed, Feb 10, 2021, 9:33 AM James Cameron  wrote:

> Indeed.  So the question becomes;
>
> - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
>   Blocks, or Sugar); this forms part of a project proposal,
>
> - who will recruit, evaluate, and onboard a technical writer?
>
> - who will administer the program in Sugar Labs?
>
> https://developers.google.com/season-of-docs/docs/admin-guide
>
> On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > It is being organised differently this year, we have to apply for a
> grant and
> > then we find the writer we reach out directly to the writer we want to
> work
> > with, at least that is how I understood it.
> >
> > [1]https://opensource.googleblog.com/2021/02/
> > the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> >
> > [2]https://developers.google.com/season-of-docs/docs/tech-writer-guide
> >
> > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3]2017...@iiitdmj.ac.in>
> wrote:
> >
> > I think it is a great idea. Sugar labs should take part in GSoD.
> >
> > Regards
> > Saumya Mishra
> >
> > On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4]qu...@laptop.org>
> wrote:
> >
> > It's back.  Can we win a slot this year?  Ideas welcome.
> >
> > [5]https://opensource.googleblog.com/2021/02/
> >
>  the-2021-season-of-docs-application-for-organizations-is-open.html
> > [6]https://developers.google.com/season-of-docs
> >
> > --
> > James Cameron
> > [7]https://quozl.linux.org.au/
> > ___
> > Sugar-devel mailing list
> > [8]Sugar-devel@lists.sugarlabs.org
> > [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > ___
> > Sugar-devel mailing list
> > [10]Sugar-devel@lists.sugarlabs.org
> > [11]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1]
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> > [2] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> > [3] mailto:2017...@iiitdmj.ac.in
> > [4] mailto:qu...@laptop.org
> > [5]
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> > [6] https://developers.google.com/season-of-docs
> > [7] https://quozl.linux.org.au/
> > [8] mailto:Sugar-devel@lists.sugarlabs.org
> > [9] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [10] mailto:Sugar-devel@lists.sugarlabs.org
> > [11] http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameron
> https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Indeed.  So the question becomes;

- what documentation does Sugar Labs need (e.g. for Sugarizer, Music
  Blocks, or Sugar); this forms part of a project proposal,

- who will recruit, evaluate, and onboard a technical writer?

- who will administer the program in Sugar Labs?

https://developers.google.com/season-of-docs/docs/admin-guide

On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> It is being organised differently this year, we have to apply for a grant and
> then we find the writer we reach out directly to the writer we want to work
> with, at least that is how I understood it. 
> 
> [1]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> 
> [2]https://developers.google.com/season-of-docs/docs/tech-writer-guide
> 
> On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3]2017...@iiitdmj.ac.in> wrote:
> 
> I think it is a great idea. Sugar labs should take part in GSoD.
> 
> Regards
> Saumya Mishra
> 
> On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4]qu...@laptop.org> wrote:
> 
> It's back.  Can we win a slot this year?  Ideas welcome.
> 
> [5]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html
> [6]https://developers.google.com/season-of-docs
> 
> --
> James Cameron
> [7]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org
> [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> ___
> Sugar-devel mailing list
> [10]Sugar-devel@lists.sugarlabs.org
> [11]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> [2] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> [3] mailto:2017...@iiitdmj.ac.in
> [4] mailto:qu...@laptop.org
> [5] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> [6] https://developers.google.com/season-of-docs
> [7] https://quozl.linux.org.au/
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
James Cameron
https://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Season of Docs

[Favour Kelvin]

It is being organised differently this year, we have to apply for a grant
and then we find the writer we reach out directly to the writer we want to
work with, at least that is how I understood it.

https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html?m=1

https://developers.google.com/season-of-docs/docs/tech-writer-guide

On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <2017...@iiitdmj.ac.in> wrote:

> I think it is a great idea. Sugar labs should take part in GSoD.
>
>
> Regards
> Saumya Mishra
>
> On Wed, Feb 10, 2021 at 7:05 AM James Cameron  wrote:
>
>> It's back.  Can we win a slot this year?  Ideas welcome.
>>
>>
>> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
>> https://developers.google.com/season-of-docs
>>
>> --
>> James Cameron
>> https://quozl.linux.org.au/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Season of Docs

[Saumya Mishra]

I think it is a great idea. Sugar labs should take part in GSoD.


Regards
Saumya Mishra

On Wed, Feb 10, 2021 at 7:05 AM James Cameron  wrote:

> It's back.  Can we win a slot this year?  Ideas welcome.
>
>
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> https://developers.google.com/season-of-docs
>
> --
> James Cameron
> https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Season of Docs

[Peace Ojemeh]

It will be really great if we can.


On Wed, 10 Feb 2021 at 2:35 am James Cameron  wrote:

> It's back.  Can we win a slot this year?  Ideas welcome.
>
>
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> https://developers.google.com/season-of-docs
>
> --
> James Cameron
> https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-- 
Peace Ojemeh(Perrie)
Twitter: https://twitter.com/Peace_Ojemeh
Email: fidelis.peaceoje...@gmail.com
peaceoje...@sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Season of Docs

[James Cameron]

It's back.  Can we win a slot this year?  Ideas welcome.

https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
https://developers.google.com/season-of-docs

-- 
James Cameron
https://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Season of Docs-2019

[Tony Anderson]

Clearly, you want to contribute to our documentation. GSOC makes clear 
that Sugar Labs has at least three separate elements: Sugar, Sugarizer 
and Music Blocks. I would like to see you help us with the Sugar 
documentation. This is found at help.sugarlabs.org. This documentation 
is made with Sphinx (http://www.sphinx-doc.org/en/stable/). Detailed 
information is provided in help.sugarlabs.org/how to contribute.


We are just beginning to think about how to participate in GSOD as you 
can see from the https://github.com/sugarlabs/GSoD link which is 
essentially a stub. However, the above information in help.sugarlabs.org 
is enough to enable you to make immediate contributions. As an example, 
we need a section describing how to download and install the SOAS 
version of Sugar. There are some differences in SOAS from Sugar as 
implemented for the XO - e.g. SOAS does not have a 'Gnome interface'. 
Another section is needed to document how to set up Ubuntu 18.04 
alongside Windows and how to install Sugar (sucrose) to work with 
Ubuntu. This version does provide the 'gnome interface' via Ubuntu 
itself but switching between Sugar and Ubuntu is not intuitive. A third 
option is Sugar on the Raspberry Pi where the alternate interface is 
Raspbian. These topics may be directly useful to you as you need to be 
able to use Sugar and to make screenshots.


Documentation of Sugar in the context of the XO is important since that 
is the environment in which over 90% of our users operate. Further 
documentation that emphasizes pictures (mostly screenshots) and 
minimizes text is critical since the majority of our uses do not speak 
English as a native language and attend schools where the medium of 
instruction is the native language.


Looking forward to seeing you contribution. Please feel free to ask for 
help on Sugar-Devel and to the Sugar Labs education committee by the 
IAEP mailing list or to me directly if I can be of help.


Yours,

Tony


On 4/15/19 2:34 AM, shivanshu raj shrivastava wrote:

Thanks for the quick information.

Shivanshu Raj Shrivastava
B.Tech 3rd year,
Electronics and Communication Department
IIT Roorkee, India
Contact:+91-9425646127,+91-8006470279


On Sun, Apr 14, 2019 at 6:15 PM Amaan Iqbal > wrote:


Hello Shivanshu,

Welcome to SugarLabs. As such, there is no prerequisite for
contributing to SugarLabs. You can visit
https://github.com/sugarlabs/GSoD to see our updates about GSoD
anytime as mentioned by Vipul.

Best way to begin is to start contributing to any of our
repositories on https://github.com/sugarlabs/ with the
technologies you are already familiar with.

Here is a list by James to get started.

New to Sugar Labs? Unlock these achievements.  Work from top to
bottom.

1.  Use Sugar or Sugarizer,


https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md

    * by using Sugar or Sugarizer you will learn how it works, and
      what can be improved.

    * mandatory,

2.  Read our Code of Conduct,


https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md

    * especially note the need to choose an appropriate forum, and
      remind others to do the same,

    * mandatory,

3.  Join the developer mailing list,

https://lists.sugarlabs.org/listinfo/sugar-devel

    * for asking questions and helping others,

    * subscribe before posting,

    * don't use digest mode if you plan to post messages or
replies,
      as it breaks threads,

    * try to keep discussions public; the default reply mode is
      private, use reply-all,

    * mandatory,

4.  Get a GitHub account,

https://github.com/

    * for reporting issues that you won't fix,

    * for fixing problems in source code,

    * recommended,

5.  Join the Sugar Labs GitHub organisation,

https://github.com/sugarlabs

    * for regular source code contributors, and reviewers, by
      invitation, contact one of the existing members,

    * helpful for mail notification of GitHub activity,

    * optional,

6.  Join as a Member of Sugar Labs,

https://wiki.sugarlabs.org/go/Sugar_Labs/Members

    * requires some contribution; code, documentation,
translations,
      maintenance, running a Sugar deployment, or any other
      non-trivial activities which benefit Sugar Labs,

    * reviewed by committee,

    * optional,

7.  Get a wiki.sugarlabs.org  account,

https://wiki.sugarlabs.org/

    * needed for maintaining Wiki content,

    * needed as part of moving Wiki content to GitHub,

    * for subscribing to edit 

Re: [Sugar-devel] Google Season of Docs-2019

[shivanshu raj shrivastava]

Thanks for the quick information.

Shivanshu Raj Shrivastava
B.Tech 3rd year,
Electronics and Communication Department
IIT Roorkee, India
Contact:+91-9425646127,+91-8006470279


On Sun, Apr 14, 2019 at 6:15 PM Amaan Iqbal 
wrote:

> Hello Shivanshu,
>
> Welcome to SugarLabs. As such, there is no prerequisite for contributing
> to SugarLabs. You can visit https://github.com/sugarlabs/GSoD to see our
> updates about GSoD anytime as mentioned by Vipul.
>
> Best way to begin is to start contributing to any of our repositories on
> https://github.com/sugarlabs/ with the technologies you are already
> familiar with.
>
> Here is a list by James to get started.
>
> New to Sugar Labs?  Unlock these achievements.  Work from top to
>> bottom.
>>
>> 1.  Use Sugar or Sugarizer,
>>
>>
>> https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
>>
>> * by using Sugar or Sugarizer you will learn how it works, and
>>   what can be improved.
>>
>> * mandatory,
>>
>> 2.  Read our Code of Conduct,
>>
>>
>> https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md
>>
>> * especially note the need to choose an appropriate forum, and
>>   remind others to do the same,
>>
>> * mandatory,
>>
>> 3.  Join the developer mailing list,
>>
>> https://lists.sugarlabs.org/listinfo/sugar-devel
>>
>> * for asking questions and helping others,
>>
>> * subscribe before posting,
>>
>> * don't use digest mode if you plan to post messages or replies,
>>   as it breaks threads,
>>
>> * try to keep discussions public; the default reply mode is
>>   private, use reply-all,
>>
>> * mandatory,
>>
>> 4.  Get a GitHub account,
>>
>> https://github.com/
>>
>> * for reporting issues that you won't fix,
>>
>> * for fixing problems in source code,
>>
>> * recommended,
>>
>> 5.  Join the Sugar Labs GitHub organisation,
>>
>> https://github.com/sugarlabs
>>
>> * for regular source code contributors, and reviewers, by
>>   invitation, contact one of the existing members,
>>
>> * helpful for mail notification of GitHub activity,
>>
>> * optional,
>>
>> 6.  Join as a Member of Sugar Labs,
>>
>> https://wiki.sugarlabs.org/go/Sugar_Labs/Members
>>
>> * requires some contribution; code, documentation, translations,
>>   maintenance, running a Sugar deployment, or any other
>>   non-trivial activities which benefit Sugar Labs,
>>
>> * reviewed by committee,
>>
>> * optional,
>>
>> 7.  Get a wiki.sugarlabs.org account,
>>
>> https://wiki.sugarlabs.org/
>>
>> * needed for maintaining Wiki content,
>>
>> * needed as part of moving Wiki content to GitHub,
>>
>> * for subscribing to edit notifications.
>>
>> * optional,
>>
>> 8.  Get an activities.sugarlabs.org account,
>>
>> https://activities.sugarlabs.org/
>>
>> * needed for releasing new versions of Sugar activities,
>>
>> * optional,
>>
>> 9.  Get a shell.sugarlabs.org account,
>>
>>
>> https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account
>>
>> * requires a justification,
>>
>> * also provides a @sugarlabs.org mail alias,
>>
>> * for releasing new versions of Sugar components, test builds,
>>   or large data sets,
>>
>> * for limited experimentation with non-root network services, such
>>   as bots or IRC proxies,
>>
>> * optional,
>>
>> 10. Get a translate.sugarlabs.org account,
>>
>> https://translate.sugarlabs.org/
>>
>> * if you are bi- or multi-lingual, use your skills,
>>
>> * especially if you can test Sugar activities and components, as
>>   this will inform your translations,
>>
>> * optional,
>>
>> 11. Get a bugs.sugarlabs.org account,
>>
>> https://bugs.sugarlabs.org/
>>
>> * only if you must maintain old bug reports,
>>
>> * new issues may be reported via GitHub,
>>
>> * optional,
>>
>> 12. Join Sugar on Fedora live system mailing list,
>>
>> https://lists.sugarlabs.org/listinfo/soas
>>
>> * download, test, report bugs, fix bugs, package,
>>
>> * share your experience with others who focus on this
>>   distribution,
>>
>> * optional,
>>
>> 13. Join Sugar on Debian mailing lists,
>>
>>
>> https://github.com/sugarlabs/sugar/blob/master/docs/debian.md#packaging
>>
>> * download, test, report bugs, fix bugs, package,
>>
>> * share your experience with others who focus on this distribution,
>>
>> * optional,
>>
>> 14. Join the Internet Relay Chat channel #sugar
>>
>> irc://irc.freenode.net/#sugar
>>
>> * for synchronous chat with others,
>>
>> * requires registration with freenode.net,
>>
>> * optional,
>>
>> 15. Join the Internet Relay Chat channel #sugar-meeting
>>
>> irc://irc.freenode.net/#sugar-meeting
>> http://meeting.sugarlabs.org/
>>
>> * for meetings, but keep your own transcripts and minutes,
>>
>> * requires registration with freenode.net,
>>
>> * optional,
>>
>> 16. 

Re: [Sugar-devel] Google Season of Docs-2019

[Amaan Iqbal]

Hello Shivanshu,

Welcome to SugarLabs. As such, there is no prerequisite for contributing to
SugarLabs. You can visit https://github.com/sugarlabs/GSoD to see our
updates about GSoD anytime as mentioned by Vipul.

Best way to begin is to start contributing to any of our repositories on
https://github.com/sugarlabs/ with the technologies you are already
familiar with.

Here is a list by James to get started.

New to Sugar Labs?  Unlock these achievements.  Work from top to
> bottom.
>
> 1.  Use Sugar or Sugarizer,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
>
> * by using Sugar or Sugarizer you will learn how it works, and
>   what can be improved.
>
> * mandatory,
>
> 2.  Read our Code of Conduct,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md
>
> * especially note the need to choose an appropriate forum, and
>   remind others to do the same,
>
> * mandatory,
>
> 3.  Join the developer mailing list,
>
> https://lists.sugarlabs.org/listinfo/sugar-devel
>
> * for asking questions and helping others,
>
> * subscribe before posting,
>
> * don't use digest mode if you plan to post messages or replies,
>   as it breaks threads,
>
> * try to keep discussions public; the default reply mode is
>   private, use reply-all,
>
> * mandatory,
>
> 4.  Get a GitHub account,
>
> https://github.com/
>
> * for reporting issues that you won't fix,
>
> * for fixing problems in source code,
>
> * recommended,
>
> 5.  Join the Sugar Labs GitHub organisation,
>
> https://github.com/sugarlabs
>
> * for regular source code contributors, and reviewers, by
>   invitation, contact one of the existing members,
>
> * helpful for mail notification of GitHub activity,
>
> * optional,
>
> 6.  Join as a Member of Sugar Labs,
>
> https://wiki.sugarlabs.org/go/Sugar_Labs/Members
>
> * requires some contribution; code, documentation, translations,
>   maintenance, running a Sugar deployment, or any other
>   non-trivial activities which benefit Sugar Labs,
>
> * reviewed by committee,
>
> * optional,
>
> 7.  Get a wiki.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/
>
> * needed for maintaining Wiki content,
>
> * needed as part of moving Wiki content to GitHub,
>
> * for subscribing to edit notifications.
>
> * optional,
>
> 8.  Get an activities.sugarlabs.org account,
>
> https://activities.sugarlabs.org/
>
> * needed for releasing new versions of Sugar activities,
>
> * optional,
>
> 9.  Get a shell.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account
>
> * requires a justification,
>
> * also provides a @sugarlabs.org mail alias,
>
> * for releasing new versions of Sugar components, test builds,
>   or large data sets,
>
> * for limited experimentation with non-root network services, such
>   as bots or IRC proxies,
>
> * optional,
>
> 10. Get a translate.sugarlabs.org account,
>
> https://translate.sugarlabs.org/
>
> * if you are bi- or multi-lingual, use your skills,
>
> * especially if you can test Sugar activities and components, as
>   this will inform your translations,
>
> * optional,
>
> 11. Get a bugs.sugarlabs.org account,
>
> https://bugs.sugarlabs.org/
>
> * only if you must maintain old bug reports,
>
> * new issues may be reported via GitHub,
>
> * optional,
>
> 12. Join Sugar on Fedora live system mailing list,
>
> https://lists.sugarlabs.org/listinfo/soas
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this
>   distribution,
>
> * optional,
>
> 13. Join Sugar on Debian mailing lists,
>
>
> https://github.com/sugarlabs/sugar/blob/master/docs/debian.md#packaging
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this distribution,
>
> * optional,
>
> 14. Join the Internet Relay Chat channel #sugar
>
> irc://irc.freenode.net/#sugar
>
> * for synchronous chat with others,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 15. Join the Internet Relay Chat channel #sugar-meeting
>
> irc://irc.freenode.net/#sugar-meeting
> http://meeting.sugarlabs.org/
>
> * for meetings, but keep your own transcripts and minutes,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 16. Join Gitter
>
> https://gitter.im/
>
> * for chat with others,
>
> * best is mailing list sugar-devel@ for topics of general interest,
>
> * requires registration with one of several organisations,
>
> * optional,
>
> 17. Maintain an Activity
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>
> * many learner focused activities (apps) need simple 

Re: [Sugar-devel] Google Season of Docs-2019

[Vipul Gupta]

Hello Shivanshu,

Yes, that it has been. Firstly, welcome to Sugar Labs. While we are very
excited about participating in Google Season of Docs this year, I would
like to inform you that the planning for the same is underway. You can
follow the conversation on the mailing list or watch for changes on the
GSoD repository [1]. Till the time organisations are announced as per the
GSoD timeline, I highly suggest you to start contributing to Sugar Labs
wherever you see fit. We are always here to help. Hope that fulfills your
request.

Cordially,
Vipul Gupta
Mixster  | Github


[1] - https://github.com/sugarlabs/GSoD

On Sun, Apr 14, 2019 at 2:21 PM shivanshu raj shrivastava <
shivanshu1...@gmail.com> wrote:

> Hi everyone,
> Well, it's been a hectic weekend for both Sugar Labs and GSoC aspirants.
> I am new to the community and interested in Google Season of Docs with
> Sugar, I request Sugar Labs to tell me about prerequisites and their plans
> for GSoD-2019, So that I can prepare well for it.
> Thank You!
>
> Shivanshu Raj Shrivastava
> B.Tech 3rd year,
> Electronics and Communication Department
> IIT Roorkee, India
> Contact:+91-9425646127,+91-8006470279
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Season of Docs-2019

[shivanshu raj shrivastava]

Hi everyone,
Well, it's been a hectic weekend for both Sugar Labs and GSoC aspirants.
I am new to the community and interested in Google Season of Docs with
Sugar, I request Sugar Labs to tell me about prerequisites and their plans
for GSoD-2019, So that I can prepare well for it.
Thank You!

Shivanshu Raj Shrivastava
B.Tech 3rd year,
Electronics and Communication Department
IIT Roorkee, India
Contact:+91-9425646127,+91-8006470279
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel