[Sugar-devel] Introduction to community

[James Cameron]

What do you mean?  Designer is so vague.  Software designer?  Web site
designer?  Graphics designer?  System integration designer?  User
experience designer?  Design is part of everything we do already, and
a designer who can't implement what they design is generally
ineffective.

On Mon, Jul 29, 2019 at 02:03:24AM +0100, Oluebube Oti wrote:
> How about how to get started as a designer?
> 
> Sent from my iPhone
> 
> > On Jul 28, 2019, at 11:51 PM, James Cameron <quozl at laptop.org> wrote:
> > 
> > Welcome Deepak,
> > 
> > GCompris skills are needed.  The opportunities are;
> > 
> > - maintenance and improvement of the GCompris wrapper activity for
> >  Sugar, https://github.com/sugarlabs/gcompris-wrapper-activity
> > 
> > - porting a new GCompris Journal integration activity for
> >  Sugar on current releases of Debian, Ubuntu and Fedora Linux,
> >  https://wiki.sugarlabs.org/go/Activities/GCompris
> > 
> > - updating the GCompris Journal integration activity for Sugar on OLPC
> >  OS for XO-1, XO-1.5, XO-1.75 and XO-4 laptops; a much harder task
> >  because it requires backporting and testing on Fedora 18.
> >  https://wiki.sugarlabs.org/go/Activities/GCompris
> > 
> > You can find how to get started as a Sugar Labs developer below.
> > 
> > New to Sugar Labs?  Unlock these achievements.  Work from top to
> > bottom. [v7]
> > 
> > 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, so 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 that are
> >      compatible with 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
> >      or Ubuntu,
> > 
> >    * optional,
> > 
> > 14. Join the Internet Relay Chat channel #sugar
> > 
> >    irc://irc.freenode.net/#sugar
> > 
> >    * for synchronous chat with others; rare to see unless a meeting
> >      is arranged,
> > 
> >    * 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 to be logged,
> > 
> >    * requires registration with freenode.net,
> > 
> >    * optional,
> > 
> > 16. Join Gitter
> > 
> >    https://gitter.im/
> > 
> >    * for chat with others, although it has faded since introduced,
> > 
> >    * 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!
> > 
> > See also "How to ask for directions",
> > http://lists.sugarlabs.org/archive/sugar-devel/2018-October/055788.html
> > 
> >> On Sun, Jul 28, 2019 at 11:47:46PM +0530, Deepak Kumar wrote:
> >> Hello everyone,
> >> I am Deepak Kumar a 3rd year undergraduate pursuing B.E in Information
> >> Technology from Yeshwantrao Chavan College of Engineering, Nagpur. I am a open
> >> source developer earlier contributing to KDE GCompris project. I also found
> >> this project interesting and want to start making my contributions to this
> >> project. Can someone guide me please how to get started with it?
> >> 
> >> Thanks
> >> Deepak Kumar
> > 
> >> _______________________________________________
> >> Sugar-devel mailing list
> >> Sugar-devel at lists.sugarlabs.org
> >> http://lists.sugarlabs.org/listinfo/sugar-devel
> > 
> > 
> > -- 
> > James Cameron
> > http://quozl.netrek.org/
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
James Cameron
http://quozl.netrek.org/