[Sugar-devel] How to get started as a Sugar Labs developer [v7]

[Oluebube Oti]

Please those this apply to this team?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 131072 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190909/dc19619a/attachment-0001.png>
-------------- next part --------------


Sent from my iPhone

> On Sep 8, 2019, at 10:57 PM, James Cameron <quozl at laptop.org> wrote:
> 
> New to Sugar Labs?  Unlock these achievements.  Work from top to
> bottom.
> 
> 1.  Use Sugar, Sugarizer, or Music Blocks,
> 
>    https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
> 
>    * by using Sugar, Sugarizer or Music Blocks you will learn how it
>      works, and what can be improved.
> 
>    * mandatory; we are an open source software project, and these
>      three software products are what we produce,
> 
> 2.  Read our Code of Conduct,
> 
>    https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md
> 
>    * especially 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,
> 
>    * take the time to check the archives in case your question has
>      already been answered,
> 
>    * 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 for Fedora
>      18 systems,
> 
>    * 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 announced meetings,
> 
>    * requires registration with freenode.net,
> 
>    * optional,
> 
> 16. Join Gitter
> 
>    https://gitter.im/
> 
>    * for chat with others, though it really hasn't taken off,
> 
>    * 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 maintenance,
> 
>    * adopt an activity you like as your focus.
> 
> Hope that helps!
> 
> ----
> 
> How to ask for directions?
> 
> “How to get started as a Sugar Labs developer” above assumes you are
> self-directed.  You will decide for yourself what is best for you to
> do.  You will use Sugar, Sugarizer or Music Blocks, and choose what to
> maintain or improve, based on;
> 
>    * your time,
>    * your interest,
>    * your equipment,
>    * how many other people are also interested, and;
>    * your previous experience with the languages and tools.
> 
> You are always the best judge of these things.  If you fail in one of
> these areas, you can self-improve.
> 
> Lionel (@llaske) can tell you what needs doing in Sugarizer.  Walter
> (@walterbender) can tell you what needs doing in Music Blocks.  For
> Sugar, what needs doing is;
> 
>    * maintenance of activities, through to release and publishing,
>    * back-porting Sugarizer activities to Sugar,
>    * maintenance of the GTK 3 toolkit and shell (for experts),
>    * porting old activities to GTK 3, TelepathyGLib and Python 3,
> 
> It is tempting to do something small like the web site.  Please don't.
> 
> New developers should avoid changes to our infrastructure, such as web
> sites and documentation, until they have demonstrated their
> contribution to and awareness of the source code of Sugar, Sugarizer
> or Music Blocks.
> 
> This is also a cultural difference.  Sugar Labs is closer to the
> innovation culture of Silicon Valley than to a university.  We don't
> direct ourselves much at all.
> 
> For personal development in the open source innovation culture, please
> also read How To Become A Hacker by Eric S. Raymond.
> 
> http://www.catb.org/esr/faqs/hacker-howto.html
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel