[Sugar-devel] Regarding Google Code In 2018 mentorship

Rishabh Thaney rishabhthaney at gmail.com
Tue Oct 2 07:17:37 EDT 2018


Hey Roshni

One of the pre requisites we had for selecting mentors this year was that
they should've previously contributed to Sugar Labs. You can still get
involved with contributing to our org though.

Here's a list by James, that you should look at:

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!
Looking forward to your contributions

Best Regards
Rishabh


On Tue, Oct 2, 2018 at 3:30 PM Roshni Ram <roshni.ram001 at gmail.com> wrote:

> Hello,
> I would like to know if there is a vacancy for becoming a Google Code-In
> mentor with Sugar Labs this year.
> I have prior experience in Android, React, React native, Deep learning,
> Computer Vision, Digital Image Processing(Research) and I am an active
> contributor in the IIITV organization.
> I have prior experience of open source and working remotely. I hope to
> leverage these experiences into the Google Code-In mentor role.
> LinkedIn: https://www.linkedin.com/in/roshni-ram-306b0a164/
> GitHub: https://github.com/roshniRam
> Looking forward to your reply.
>
> Thank you
> Roshni Ram
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20181002/b2a7d290/attachment-0001.html>


More information about the Sugar-devel mailing list