[Sugar-devel] Google Season of Docs-2019
Tony Anderson
tony_anderson at usa.net
Sun Apr 14 20:35:41 EDT 2019
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 <amaaniqbal2786 at gmail.com
> <mailto:amaaniqbal2786 at gmail.com>> 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 <http://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
> <http://activities.sugarlabs.org/> account,
>
> https://activities.sugarlabs.org/
>
> * needed for releasing new versions of Sugar activities,
>
> * optional,
>
> 9. Get a shell.sugarlabs.org
> <http://shell.sugarlabs.org/> account,
>
> https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account
>
> * requires a justification,
>
> * also provides a @sugarlabs.org
> <http://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
> <http://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 <http://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 <http://irc.freenode.net/#sugar>
>
> * for synchronous chat with others,
>
> * requires registration with freenode.net
> <http://freenode.net/>,
>
> * optional,
>
> 15. Join the Internet Relay Chat channel #sugar-meeting
>
> irc://irc.freenode.net/#sugar-meeting
> <http://irc.freenode.net/#sugar-meeting>
> http://meeting.sugarlabs.org/
>
> * for meetings, but keep your own transcripts and minutes,
>
> * requires registration with freenode.net
> <http://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
> 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
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> <mailto:Sugar-devel at lists.sugarlabs.org>
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> Thanks,
> Amaan
>
> On Sun, Apr 14, 2019 at 5:08 PM Vipul Gupta
> <vipulgupta2048 at gmail.com <mailto:vipulgupta2048 at gmail.com>> wrote:
>
> 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 <https://mixstersite.wordpress.com/> | Github
> <https://github.com/vipulgupta2048>
>
> [1] - https://github.com/sugarlabs/GSoD
>
> On Sun, Apr 14, 2019 at 2:21 PM shivanshu raj shrivastava
> <shivanshu1333 at gmail.com <mailto:shivanshu1333 at 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 at lists.sugarlabs.org
> <mailto:Sugar-devel at lists.sugarlabs.org>
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> <mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190415/87e6c575/attachment-0001.html>
More information about the Sugar-devel
mailing list