[Sugar-devel] Google Code In

[Walter Bender]

Google Code In 2014-15 has just been announced [1]. As discussed at
yesterday's SLOB meeting [2], we have agreed to apply again this year.
(GCI has been a great source of new talent and mentoring youth
programmers is well aligned with our mission.)

Next steps:
(1) I will prepare our application, due that the end of the month;
(2) Potential mentors should please contact me ASAP;
(3) Anyone with ideas for tasks should also contact me ASAP.

Note: tasks can be programming (primarily Python and Javascript), but
also design documentation, outreach, etc. So please don't be shy about
sharing your ideas and talents.

regards

-walter

[1] http://www.google-melange.com/gci/homepage/google/gci2014
[2] http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-10-07
-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code In

[Walter Bender]

I just submitted the Sugar Labs application for Google Code In (GCI).

For those of you unfamiliar with GCI, it is a programming contest for
children ages 13-17. We've participated the past 2 years -- it is
really fun but the reason why we participate is that we want to
re-enforce the message that Sugar belongs to its users and that they
have both ownership and the responsibility that ownership implies.
Just as learning is not something done to you, but something you do,
learning with Sugar ultimately means participating in the Sugar
development process. At Sugar Labs, we are trying to bring the culture
of Free Software into the culture of school. So the Code-in is not
just an opportunity for us to get some tasks accomplished, it is
quintessential to our overall mission.

It is now time to sign up as a mentor (See [1]). Our organization ID
is sugarlabs.
Mentors help coach the students on their tasks and can sign off on
work that is completed. (Note: mentors must be age 18+). Please
contact me if you have any questions.

regards

-walter

[1] http://www.google-melange.com/gci/homepage/google/gci2014

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code In

[Walter Bender]

Sugar Labs is considering applying for Google Code In again (the
application process begins in October). As you may recall, Google Code
In is a programming contest for youths ages 13-17, where the tasks are
specific to the needs of the participating organization. It is through
Google Code In that we have been able to grow the ranks of our
developer ranks and also get some outstanding documentation written,
as well as feedback from our target audience about our work. It has
been a very positive experience for Sugar Labs over the past three
years. So why would not make every effort to participate again this
year? It is simply a matter of numbers. We need mentors. I've
personally carried the bulk of the administrative and mentoring
overhead in past years, but I need help this year as I have some
additional obligations in December and January. Are there members of
the community willing to help me this year? If so, please step
forward.

regards.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-In

[samir menon]

I was just wondering if anyone knew if Sugar labs will be participating. I
think it is a great way to encourage learners to help the Sugar community,
and will prove to be invaluable to the Sugar community. The deadline for
submission is , I believe, November 5th.

Thanks!,
~Samir
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google code in

[Chris Leonard]

In spite of failures to win status with GSOC, I thought Sugar Labs
might be interested in Google Code In.  (GCI)  It is possible that
prior GSOC success is a criterion for entry.

After all working with kids is supposed to be what we are all about.

http://google-opensource.blogspot.com/2012/09/google-code-in-contest-for-high-school.html

http://www.google-melange.com/gci/homepage/google/gci2012

I think the deadline for orgs to apply is Nov 5th.  (winners announced
Nov 12).  Without having had GSOC success, we may not be eligible.

FAQ
http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page

cjl
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code In 2016

[Walter Bender]

Great news. Sugar Labs was once again accepted as one of the organizations
participating in Google Code In.

We have a few weeks to prepare. If you are interested in being a mentor,
please contact me and also please sign up at https://codein.withgoogle.com

If you have project/task ideas, please send them my way or add them to the
wiki page at
https://wiki.sugarlabs.org/go/Google_Code_In_2016#This_is_a_stub_for_25.2B_example_tasks_new_for_GCI_2016
.

As always, I am very much looking forward to GCI.

regards.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-In Mentorship

[Dipansh Khandelwal]

Hi @all, I am Dipansh Khandelwal
I would like to volunteer for the role of mentor in Google Code-In. I have
already applied for the same.
I have been into open source and using git and github from last 2 years.I
have worked with a few projects with sugar-labs also.
I have worked with Java, NodeJs, python using platforms like Android,
Django and React/React-Native, and also have a good experience of git and
open source. Presently I am working in blockchain development. I have also
worked with a few startups which helped me learn a lot more about team
development process.
So, I want to get more experience and as well as share my knowledge and
help the new students come up, learn and appreciate the power of open
source.
You can take a look at some of my projects here :
https://www.linkedin.com/in/dipanshkhandelwal/
Please connect with me at : https://github.com/DipanshKhandelwal/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-in-2019

[ANIKET MATHUR]

G'day everyone,

I am Aniket, an undergraduate at IIT Roorkee, I had my GSoC with Sugar Labs
and contributing to the organisation since December 2018.

I would like to be a mentor for Google Code-in 2019 for Sugar Labs. It
would be great if I get this opportunity.

Regards,
Aniket Mathur
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-in 2019

[Walter Bender]

I've begun putting together our application to GCI 2019. And I have
created a page in the wiki with background information [2]

If you are interested in mentoring, please let me know (and add your name
to the list at the bottom of the wiki page.). Please indicate what areas
you wish to help with (coding, design, research, documentation, and QA) and
relevant experience in the Sugar Labs community.

Looking forward to GCI.

regards.

-walter

[1] https://codein.withgoogle.com/
[2] https://wiki.sugarlabs.org/go/Google_Code_In_2019

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-In

[Walter Bender]

On Tue, Nov 2, 2010 at 8:17 AM, samir menon  wrote:
> I was just wondering if anyone knew if Sugar labs will be participating. I
> think it is a great way to encourage learners to help the Sugar community,
> and will prove to be invaluable to the Sugar community. The deadline for
> submission is , I believe, November 5th.

If someone would take the lead on it... I don't have the bandwidth at
the moment :(

-walter

>
> Thanks!,
> ~Samir
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google code in

[Alexandro Colorado]

I was talking with Ignacio, a kid from Uruguay that hangs on #sugar
and told him to sign in Code-In.

He is excited, but I still wonder if OLPC/SugarLabs would be joining
this effort.

Right how he is working with Flavio D. on doing some ports to GTK3.

On 10/14/12, Chris Leonard  wrote:
> In spite of failures to win status with GSOC, I thought Sugar Labs
> might be interested in Google Code In.  (GCI)  It is possible that
> prior GSOC success is a criterion for entry.
>
> After all working with kids is supposed to be what we are all about.
>
> http://google-opensource.blogspot.com/2012/09/google-code-in-contest-for-high-school.html
>
> http://www.google-melange.com/gci/homepage/google/gci2012
>
> I think the deadline for orgs to apply is Nov 5th.  (winners announced
> Nov 12).  Without having had GSOC success, we may not be eligible.
>
> FAQ
> http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page
>
> cjl
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google code in

[Chris Leonard]

On Sun, Oct 14, 2012 at 11:22 AM, Alexandro Colorado  wrote:
> I was talking with Ignacio, a kid from Uruguay that hangs on #sugar
> and told him to sign in Code-In.
>
> He is excited, but I still wonder if OLPC/SugarLabs would be joining
> this effort.
>
> Right how he is working with Flavio D. on doing some ports to GTK3.

It is not entirely clear to me that Sugar Labs will be eligible.  I
read something that made it sound like all orgs were previous GSOC
winners, I am not 100% sure though.

I would encourage any of our eligible younger members to sign up as
individual participants.  They will need a note from their parents to
be able to take part.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions


I don't think we have any one that will have an issue with this criteria.

 The Contest is not open to persons who are (1) residents of US
embargoed countries (Cuba, Iran, Myanmar (Burma), North Korea, Sudan,
or Syria), (2) ordinarily resident in such countries, or (3) otherwise
prohibited by applicable export controls and sanctions. The Contest is
also not open to residents of Brazil, Italy, Quebec, and Saudi Arabia.

Given how dependent Sugar Labs and OLPC are on the upstream software
stack, there are certain to be tasks for projects that will have
benefits that will flow downstream to us.

I first saw this on the Gnome Foundation list, it is not clear whether
they will be applying yet, but that would be a great example of an org
with tasks that could very directly help us, I'm sure our devs would
be more than happy to work with any individual participants to try to
identify orgs and tasks among those eventually posted by the
participating orgs that would also benefit the Sugar user community.

cjl
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google code in

[Chris Leonard]

On Sun, Oct 14, 2012 at 11:38 AM, Chris Leonard
 wrote:

> Given how dependent Sugar Labs and OLPC are on the upstream software
> stack, there are certain to be tasks for projects that will have
> benefits that will flow downstream to us.

Anything that improves any of the packages listed in a recent OLPC
Release packages.txt file would have direct benefits to our users.

x86 (XO-1)
http://build.laptop.org/13.1.0/os6/xo-1/31006o0.packages.txt

Just as an example, ARM architecture is new to a number of upstream
projects.  Anything that improved the ARM version of a package would
be a big win for Sugar Labs / OLPC.

ARM (XO-4)
http://build.laptop.org/13.1.0/os6/xo-4/31006o4.packages.txt

Of course, it remains to be seen which orgs are selected to
participate and what tasks they set, but my point is that there there
is lots of room for upstream work that is directly relevant to our
community.

Working with the upstream is also a fine lesson in the social and
technical aspects of FOSS development you an aspiring young coder to
learn.

If I had to guess I would say the chance of the Sugarista recruiting
their mentor to working on Sugar is probably greater than the chance
that the mentor would pull the Sugarista away from Sugar into the
upstream project :-)

cjl
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code In wiki page

[Walter Bender]

Please help us edit http://wiki.sugarlabs.org/go/Google_Code_In_2014

Tip-o-hat to SAMDroid who has already contributed some tasks.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code In 2016

[Tony Anderson]

Hi, Walter

Currently for GSOC and GCI, we tell applicants to create a development 
environment. I think that is a mistake. One of the great strengths of 
Sugar is that it is it's own development environment. For example, the 
design of Sugar is that Browse as an activity can be installed directly 
as an xo bundle with a version number independent of the Sugar version 
number. This, of course, has two advantages - a new version of Browse 
can be used on earlier versions of Sugar and the release of Sugar 
provides the ability to execute Sugar activities but is not dependent on 
them.


GCI can be a great opportunity to develop a Sugar release which can be 
installed on standard PCs and supported by Sugar Labs.  Possibly a 
Debian release supported by Sugar Labs would be most flexible. In this 
case there could also be SD card images which work on models of the 
Raspberry Pi. Such a release could be enhanced by users working 
independently and then submitting their working changes for 
incorporation in future official releases.


Tony

On 11/07/2016 10:25 AM, Walter Bender wrote:
Great news. Sugar Labs was once again accepted as one of the 
organizations participating in Google Code In.


We have a few weeks to prepare. If you are interested in being a 
mentor, please contact me and also please sign up at 
https://codein.withgoogle.com


If you have project/task ideas, please send them my way or add them to 
the wiki page at 
https://wiki.sugarlabs.org/go/Google_Code_In_2016#This_is_a_stub_for_25.2B_example_tasks_new_for_GCI_2016.


As always, I am very much looking forward to GCI.

regards.

-walter

--
Walter Bender
Sugar Labs
http://www.sugarlabs.org



___
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 Code In 2016

[Laura Vargas]

2016-11-08 11:12 GMT-05:00 Tony Anderson :

> Hi, Walter
>
> Currently for GSOC and GCI, we tell applicants to create a development
> environment. I think that is a mistake. One of the great strengths of Sugar
> is that it is it's own development environment. For example, the design of
> Sugar is that Browse as an activity can be installed directly as an xo
> bundle with a version number independent of the Sugar version number. This,
> of course, has two advantages - a new version of Browse can be used on
> earlier versions of Sugar and the release of Sugar provides the ability to
> execute Sugar activities but is not dependent on them.
>

I am not a developer (yet) but this sounds like an interesting approach.


> GCI can be a great opportunity to develop a Sugar release which can be
> installed on standard PCs and supported by Sugar Labs.  Possibly a Debian
> release supported by Sugar Labs would be most flexible. In this case there
> could also be SD card images which work on models of the Raspberry Pi. Such
> a release could be enhanced by users working independently and then
> submitting their working changes for incorporation in future official
> releases.
>

There is clearly an identified need for such an image. I myself would like
to install and use it, specially if we could get a Sugar Network
"connection". We have documented several downstream projects like
"Huyaruro" and "Esperanza".

Still achieving such an image may be a larger project, and require
professional developers from SL. It would have to be part of the strategic
plan for Sugar Labs, for example to be able to contribute with open quality
sofwate to the edu-eco-bio-system.

Regards and blessings,

Laura Victoria


>
> Tony
>
>
> On 11/07/2016 10:25 AM, Walter Bender wrote:
>
> Great news. Sugar Labs was once again accepted as one of the organizations
> participating in Google Code In.
>
> We have a few weeks to prepare. If you are interested in being a mentor,
> please contact me and also please sign up at
> https://codein.withgoogle.com
>
> If you have project/task ideas, please send them my way or add them to the
> wiki page at https://wiki.sugarlabs.org/go/Google_Code_In_2016#This_
> is_a_stub_for_25.2B_example_tasks_new_for_GCI_2016.
>
> As always, I am very much looking forward to GCI.
>
> regards.
>
> -walter
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


-- 
Laura V.
I&D SomosAZUCAR.Org

Identi.ca/Skype acaire
IRC kaametza

Happy Learning!
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code In 2016

[Walter Bender]

On Tue, Nov 8, 2016 at 11:12 AM, Tony Anderson 
wrote:

> Hi, Walter
>
> Currently for GSOC and GCI, we tell applicants to create a development
> environment. I think that is a mistake. One of the great strengths of Sugar
> is that it is it's own development environment. For example, the design of
> Sugar is that Browse as an activity can be installed directly as an xo
> bundle with a version number independent of the Sugar version number. This,
> of course, has two advantages - a new version of Browse can be used on
> earlier versions of Sugar and the release of Sugar provides the ability to
> execute Sugar activities but is not dependent on them.
>

I don't understand what you are trying to say here re GCI. We have
introductory tasks for setting up either the Sugar developer environment,
installing from Sugar on a Stick, or installing the Sugarizer environment.
Not sure how at least most coding tasks can proceed without one of those.
Of course, some activities, e.g. the Python version of Turtle Blocks can
run without Sugar and the individual JS apps can run in a browser, but what
does that have to do with the example you cited? Could you please clarify?

>
> GCI can be a great opportunity to develop a Sugar release which can be
> installed on standard PCs and supported by Sugar Labs.  Possibly a Debian
> release supported by Sugar Labs would be most flexible. In this case there
> ctHould also be SD card images which work on models of the Raspberry Pi.
> Such a release could be enhanced by users working independently and then
> submitting their working changes for incorporation in future official
> releases.
>

Do you mean a Windows PC? Getting a full Sugar running native in Windows is
a bigger task than we can ask for in GCI. If you mean running on PC
hardware, doesn't Sugar on a Stick or yum install Sugar on Ubuntu already
do this?

That said, Alan got Turtle Blocks running in Windows. (I haven't tested it
since I don't have access to a Windows box.) Maybe we could have tasks for
doing the same for more activities?

regards.

-walter

>
> Tony
>
>
> On 11/07/2016 10:25 AM, Walter Bender wrote:
>
> Great news. Sugar Labs was once again accepted as one of the organizations
> participating in Google Code In.
>
> We have a few weeks to prepare. If you are interested in being a mentor,
> please contact me and also please sign up at
> https://codein.withgoogle.com
>
> If you have project/task ideas, please send them my way or add them to the
> wiki page at https://wiki.sugarlabs.org/go/Google_Code_In_2016#This_
> is_a_stub_for_25.2B_example_tasks_new_for_GCI_2016.
>
> As always, I am very much looking forward to GCI.
>
> regards.
>
> -walter
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code In wrap up

[Walter Bender]

Google Code In ended on Monday. We had 296 students participate and 422
tasks completed. From the feedback I have gotten from the students it was a
valuable experience for them and certainly from the point of view of Sugar
Labs we got some great work done. We also had 36 mentors this year, which
made it a much richer experience for the students and a much more
manageable situation for me. And some help from some non-mentors too
(tip-of-the-hat to Quozl).

The mentors need to select our 5 finalists from the top ten contributors as
well as our 2 grand-prize winners and 1 runner up.

TymonR 32
Cristian García 29
Pablo Salomón Ortega 23
Emily Ong Hui Qi 22
Hrishi Patel 19
Himanshu Sekhar Nayak 14
Kachachan Chotitamnavee 13
Hitesh Agarwal 12
eohomegrownapps 11
Matías Martínez 10
Ayush Kumar 10

Please email to me you thoughts so we can take them into consideration in
the decision.

I would also appreciate feedback on GCi, our process and our tasks. Would
be good for making sure we do a better job next year.

thanks all.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-in (GCI) update

[Walter Bender]

We have a good collection of initial tasks [1] for our GCI
application. But we still need more mentors. If you are interested in
being a mentor, please add your name to the wiki [2].

Tenemos una buena colección de tareas [1] iniciales para nuestra
aplicación GCI. Pero todavía necesitamos más mentores. Si usted está
interesado en ser un mentor, por favor agregue su nombre a la wiki
[2].

[1] http://wiki.sugarlabs.org/go/Google_Code_In_2013#Tasks
[2] http://wiki.sugarlabs.org/go/Google_Code_In_2013#Mentors

thanks

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-In Mentorship

[Vipul Gupta]

Hello Dipansh,

Thanks for reaching out and showing your interest. Can you list exactly
which projects you contributed to or are interested in Sugar Labs? Going
through your GitHub profile, since you are experienced in JS, you can fit
in with the Sugarizer team.

Being a mentor for this years GCI requires that you're a contributor to
sugarlabs, take a look at the list below - by James Cameron -
Looking forward to your contributions. Thanks.

New to Sugar Labs?  Unlock these achievements in any order;

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

* mandatory,

3.  Join the developer mailing list,

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

* for asking questions and helping others,

* don't use digest mode if you plan to post messages or replies,
  as it breaks threads, and please try to keep discussions public,

* mandatory,

4.  Get a GitHub account,

https://github.com/

* for reporting issues, and 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,

* may also provide @sugarlabs.org mail address,

* for releasing new versions of Sugar components, test builds,
  large data sets, or public git hosting,

* 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. Maintain an Activity

https://github.com/sugarlabs/sugar
-docs/blob/master/src/contributing.md#checklist---maintainer

* many learner-focused activities (apps) need simple maintenance,

* adopt an activity you like as your focus.

Hope that helps,

Cordially,
Vipul Gupta
Mixster  | Github

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-In Mentorship

[James Cameron]

Hey, have you contributed yet?

On Tue, Oct 02, 2018 at 05:12:59PM +0530, Dipansh Khandelwal wrote:
> Hi @all, I am Dipansh Khandelwal
> I would like to volunteer for the role of mentor in Google Code-In. I have
> already applied for the same.
> I have been into open source and using git and github from last 2 years.I have
> worked with a few projects with sugar-labs also.
> I have worked with Java, NodeJs, python using platforms like Android, Django
> and React/React-Native, and also have a good experience of git and open 
> source.
> Presently I am working in blockchain development. I have also worked with a 
> few
> startups which helped me learn a lot more about team development process.
> So, I want to get more experience and as well as share my knowledge and help
> the new students come up, learn and appreciate the power of open source.
> You can take a look at some of my projects here : [1]https://www.linkedin.com/
> in/dipanshkhandelwal/
> Please connect with me at : [2]https://github.com/DipanshKhandelwal/
> 
> References:
> 
> [1] https://www.linkedin.com/in/dipanshkhandelwal/
> [2] https://github.com/DipanshKhandelwal/

> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


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

[Sugar-devel] Google Code in (Reviewing process)

[Aryan Sharma]

Hey everyone,
I would like to highlight the issue that the reviewing process of the
Google code in task is taking longer than it should.Task is being reviewed
by 4-5 mentors and due to time difference everyone suggests their changes
at different times. I want to utilise my holidays. So,It would be greatful
if a non-coding task can be reviewed by only one person to remove the
conflicts and save time.
Thanks.
Regards
Aryan Sharma
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[Deepak Kumar]

Hi,
I am up for mentoring. As I am having my winter vacation during the GCI
period so I would love to spend my time mentoring the students for the task
and can be available for 2-3 hrs per day. Although, I am a new contributor
to this project but am familiar with the work flow of open source as
earlier I was contributing to KDE(Gcompris) project. I am skilled in
Python, Javascript(novice). I can mentor students for research,
documentation and code.

Thanks
Deepak Kumar

On Fri, 11 Oct 2019, 3:26 am Walter Bender,  wrote:

> I've begun putting together our application to GCI 2019. And I have
> created a page in the wiki with background information [2]
>
> If you are interested in mentoring, please let me know (and add your name
> to the list at the bottom of the wiki page.). Please indicate what areas
> you wish to help with (coding, design, research, documentation, and QA) and
> relevant experience in the Sugar Labs community.
>
> Looking forward to GCI.
>
> regards.
>
> -walter
>
> [1] https://codein.withgoogle.com/
> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> 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 Code-in 2019

[devil hacks]

Hi everyone,
I am Rupesh and am a full stack web developer and open source contributor.
I have contributed to some organisations like mifos, jboss etc.
Here is my github link- https://github.com/Rupeshiya.

I would love to mentor syudents in web dev related field.
Please let me know how I can get started contributing to GCI as a mentor in
this organisation.

Thanks
Rupesh


On Fri, 11 Oct 2019, 6:09 pm Deepak Kumar,  wrote:

> Hi,
> I am up for mentoring. As I am having my winter vacation during the GCI
> period so I would love to spend my time mentoring the students for the task
> and can be available for 2-3 hrs per day. Although, I am a new contributor
> to this project but am familiar with the work flow of open source as
> earlier I was contributing to KDE(Gcompris) project. I am skilled in
> Python, Javascript(novice). I can mentor students for research,
> documentation and code.
>
> Thanks
> Deepak Kumar
>
> On Fri, 11 Oct 2019, 3:26 am Walter Bender, 
> wrote:
>
>> I've begun putting together our application to GCI 2019. And I have
>> created a page in the wiki with background information [2]
>>
>> If you are interested in mentoring, please let me know (and add your name
>> to the list at the bottom of the wiki page.). Please indicate what areas
>> you wish to help with (coding, design, research, documentation, and QA) and
>> relevant experience in the Sugar Labs community.
>>
>> Looking forward to GCI.
>>
>> regards.
>>
>> -walter
>>
>> [1] https://codein.withgoogle.com/
>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> 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 Code-in 2019

[James Cameron]

Nice to have so many people wanting to be involved in mentoring, but
you must be involved in Sugar Labs.

Please use and test Music Blocks, Sugarizer, and Sugar.

Please post about your tests; what worked well, what didn't work, and
if you can use GitHub create issues.

Where you have selected mentoring for coding, write some more code.

Where you have selected mentoring for design, get involved in user
experience research or user interface design and interaction.

Where you have chosen mentoring for documentation, write some more
documentation.

You can't teach what you don't do.

Google says this in
https://developers.google.com/open-source/gci/faq#how_can_i_be_a_mentor_for_google_code-in

"You should already be a participant in the organization/open source
project that you wish to be a mentor for."

After past experiences I'm not interested in mentors who don't know
what Sugar Labs software does or how it can be used.  Such mentors are
disruptive.  They say things that are wrong.  They make technical
decisions in ignorance.  In short, they misrepresent our community of
designers, developers, and documenters.

Mentors who don't even have time to try out our software can avoid
this dissonance by;

- passing on to others questions that are outside their knowledge,

- asking public questions on behalf of a student,

- when time is of the essence, approve a task and leave the details of
  how it is tidied up to the people who know best,

When a student asks you a question in private you don't know the
answer to, don't make something up yourself.  Get them involved in
community and communicating in the open;

Google says this in
https://developers.google.com/open-source/gci/help/responsibilities#to_your_students

"Mentor Responsibilities ... to your Students ... Help and/or teach
the student how to ... be a part of your community ... communicate
more effectively and in the open".

Hope that helps!

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

Re: [Sugar-devel] Google Code-in 2019

[Favour Kelvin]

Awesome looking forward to this, I would love to be a mentor this year

Regards

On Fri, Oct 11, 2019, 11:56 PM James Cameron  wrote:

> Nice to have so many people wanting to be involved in mentoring, but
> you must be involved in Sugar Labs.
>
> Please use and test Music Blocks, Sugarizer, and Sugar.
>
> Please post about your tests; what worked well, what didn't work, and
> if you can use GitHub create issues.
>
> Where you have selected mentoring for coding, write some more code.
>
> Where you have selected mentoring for design, get involved in user
> experience research or user interface design and interaction.
>
> Where you have chosen mentoring for documentation, write some more
> documentation.
>
> You can't teach what you don't do.
>
> Google says this in
>
> https://developers.google.com/open-source/gci/faq#how_can_i_be_a_mentor_for_google_code-in
>
> "You should already be a participant in the organization/open source
> project that you wish to be a mentor for."
>
> After past experiences I'm not interested in mentors who don't know
> what Sugar Labs software does or how it can be used.  Such mentors are
> disruptive.  They say things that are wrong.  They make technical
> decisions in ignorance.  In short, they misrepresent our community of
> designers, developers, and documenters.
>
> Mentors who don't even have time to try out our software can avoid
> this dissonance by;
>
> - passing on to others questions that are outside their knowledge,
>
> - asking public questions on behalf of a student,
>
> - when time is of the essence, approve a task and leave the details of
>   how it is tidied up to the people who know best,
>
> When a student asks you a question in private you don't know the
> answer to, don't make something up yourself.  Get them involved in
> community and communicating in the open;
>
> Google says this in
>
> https://developers.google.com/open-source/gci/help/responsibilities#to_your_students
>
> "Mentor Responsibilities ... to your Students ... Help and/or teach
> the student how to ... be a part of your community ... communicate
> more effectively and in the open".
>
> Hope that helps!
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> 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 Code-in 2019

[Euan Ong]

Dear Walter,

Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely be
interested in mentoring this year.

Best regards,
Euan

On Thu, 10 Oct 2019 at 22:56, Walter Bender  wrote:

> I've begun putting together our application to GCI 2019. And I have
> created a page in the wiki with background information [2]
>
> If you are interested in mentoring, please let me know (and add your name
> to the list at the bottom of the wiki page.). Please indicate what areas
> you wish to help with (coding, design, research, documentation, and QA) and
> relevant experience in the Sugar Labs community.
>
> Looking forward to GCI.
>
> regards.
>
> -walter
>
> [1] https://codein.withgoogle.com/
> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> 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 Code-in 2019

[ANIKET MATHUR]

G'day everyone,

I wish to mentor GCI 2019 for Sugar Labs. I have a query about how to add
my name to the mentor list on the wiki page,
do I need a Sugar Labs wiki account for that?

Thanks!

On Wed, Oct 30, 2019 at 9:23 PM Euan Ong  wrote:

> Dear Walter,
>
> Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely
> be interested in mentoring this year.
>
> Best regards,
> Euan
>
> On Thu, 10 Oct 2019 at 22:56, Walter Bender 
> wrote:
>
>> I've begun putting together our application to GCI 2019. And I have
>> created a page in the wiki with background information [2]
>>
>> If you are interested in mentoring, please let me know (and add your name
>> to the list at the bottom of the wiki page.). Please indicate what areas
>> you wish to help with (coding, design, research, documentation, and QA) and
>> relevant experience in the Sugar Labs community.
>>
>> Looking forward to GCI.
>>
>> regards.
>>
>> -walter
>>
>> [1] https://codein.withgoogle.com/
>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> 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 Code In wrap up

[Dave Crossland]

Regarding a possible move from IRC to Slack, or Gitter, or something else
as suggested by Ignacio, I wonder that we could just upgrade
http://chat.sugarlabs.org from qwebchat to http://demo.shout-irc.com :)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code In wrap up

[Walter Bender]

There is also matrix.org, which is FOSS AFAIK and seems to let one
integrate irc with other channels people may prefer. I suggest a few
passionate community members give some of these systems a test-drive and
then convince us old-timers that we ought to learn some new tricks.

-walter

On Tue, Jan 17, 2017 at 4:52 PM, Dave Crossland  wrote:

> Regarding a possible move from IRC to Slack, or Gitter, or something else
> as suggested by Ignacio, I wonder that we could just upgrade
> http://chat.sugarlabs.org from qwebchat to http://demo.shout-irc.com :)
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code in (Reviewing process)

[Vipul Gupta]

Hi,
Aryan, can you point towards a particular issue where you facing such an
issue?

On Sat, Nov 10, 2018 at 3:17 PM Aryan Sharma  wrote:

> Hey everyone,
> I would like to highlight the issue that the reviewing process of the
> Google code in task is taking longer than it should.Task is being reviewed
> by 4-5 mentors and due to time difference everyone suggests their changes
> at different times. I want to utilise my holidays. So,It would be greatful
> if a non-coding task can be reviewed by only one person to remove the
> conflicts and save time.
> Thanks.
> Regards
> Aryan Sharma
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Cordially,
Vipul Gupta
Mixster  | Github

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code in (Reviewing process)

[James Cameron]

G'day Aryan,

Thanks for your feedback.

Let me introduce myself.  I'm paid by One Laptop per Child and we use
Sugar in our laptop products.  At Sugar Labs, my role is Release
Manager, and I focus on Sugar and activities.  I also do system
administration.  I'm not a GCI mentor or administrator, and cannot see
tasks.

Everyone else at Sugar Labs is a volunteer.  Their motivation is to
make Sugar Labs software better.

It is good we have so many mentors, as they can share the load; but as
you point out, review by many mentors can make a task harder.  Each
mentor is different, and will notice different things.

These reviews are not public.  Our mentors and students have a private
space at codein.withgoogle.com in which to work and review.  So I
cannot see what you are talking about.

However, I've looked through the contest rules and resources for you,
to better understand your situation;

1.  when you post a comment on a task or submit it for review, your
mentors will be sent a mail;
https://developers.google.com/open-source/gci/resources/getting-started
... there's no need to prod them into action on IRC or by private
mail, and that could backfire if you do it too much, because it may
look like you are seeking an advantage,

2.  you should get a response within 24 hours, or "occasionally under
36 hours is ok",
https://developers.google.com/open-source/gci/help/responsibilities
... if it takes longer than that, contact the organisation
administrator,

3.  other mentors and developers should work together to "facilitate
acceptance of student work", and this may mean you'll be asked to do
something that either the task did not say explicitly, or another
mentor may not have said; each student should be treated fairly in
this, and if you think you haven't been treated fairly, contact the
organisation administrator or Google.

Hope that helps.  Looking forward to your code contributions!

On Sat, Nov 10, 2018 at 09:47:17AM +0530, Aryan Sharma wrote:
> Hey everyone,
> I would like to highlight the issue that the reviewing process of the Google
> code in task is taking longer than it should.Task is being reviewed by 4-5
> mentors and due to time difference everyone suggests their changes at 
> different
> times. I want to utilise my holidays. So,It would be greatful if a non-coding
> task can be reviewed by only one person to remove the conflicts and save time.
> Thanks.
> Regards
> Aryan Sharma 

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