Re: [Sugar-devel] Introduction

[Ashutosh Gautam]

Yes , I have .
I have forked music blocks , sugar labs and have cloned it into my system .
I will start contributing very soon.
I am just going through the document of guidelines and all the things I
should keep in mind while doing it .


On Thu, Mar 24, 2022, 3:49 AM Walter Bender  wrote:

> Have you checked out the GSoC page on GitHub?
> https://github.com/sugarlabs/GSoC
>
> -walter
>
> On Wed, Mar 23, 2022 at 2:01 PM Ashutosh Gautam
>  wrote:
> >
> > Hi, Everyone! I am Ashutosh Gautam, sophomore at KIIT, Bhubaneswar
> pursuing B.Tech Cse and I look forward to contributing to Sugar Labs. I
> have a lot of experience in web Development using HTML and JavaScript ,
> specifically ReactJS.
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> --
> Walter Bender
> Sugar Labs
> https://www.sugarlabs.org
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction

[Walter Bender]

Have you checked out the GSoC page on GitHub? https://github.com/sugarlabs/GSoC

-walter

On Wed, Mar 23, 2022 at 2:01 PM Ashutosh Gautam
 wrote:
>
> Hi, Everyone! I am Ashutosh Gautam, sophomore at KIIT, Bhubaneswar pursuing 
> B.Tech Cse and I look forward to contributing to Sugar Labs. I have a lot of 
> experience in web Development using HTML and JavaScript , specifically 
> ReactJS.
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel



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

Re: [Sugar-devel] Introduction

[James Cameron]

Good to hear, thanks.

On Sat, Jan 02, 2021 at 07:55:17AM +0530, SHRAY TYAGI wrote:
> Yes, I would be interested. 
> 
> On Sat, 2 Jan 2021, 05:44 James Cameron, <[1]qu...@laptop.org> wrote:
> 
> Welcome.  Your experience with Django is immediately useful; we have a
> Django app called Pootle on [2]https://translate.sugarlabs.org/ that has
> not been maintained recently.  We continue to have occasional
> translators, but I don't think we have an active translation manager.
> 
> A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in
> the usual place (the wiki). There are several pages written by the
> previous Pootle maintainers:
> 
>   [3]http://wiki.sugarlabs.org/go/Service/translate
>   [4]http://wiki.sugarlabs.org/go/Service/Pootle
>   [5]http://wiki.sugarlabs.org/go/Service/Pootle2.5
>   [6]http://wiki.sugarlabs.org/go/Machine/pootle
> "
> 
> Is that something you're interested in?
> 
> On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote:
> > Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at
> Vishwakarma
> > Institute of Technology Pune. My technical knowledge includes python,
> React JS,
> > Html, CSS,django, Mysql,data structures and basics of java, Machine
> learning, c
> > , c++. Some of my projects include a basic django todo app, car showroom
> > database management system, digit detection using neural networks, basic
> > chatbot, etc. I am very much interested in participating in GSoC 2021.
> The main
> > reason for doing GSoC is to get exposure to the developer's world and to
> work
> > with new people. I am looking forward to working under sugarlabs.
> >
> > Regards,
> > Shray Tyagi
> 
> > ___
> > Sugar-devel mailing list
> > [7]Sugar-devel@lists.sugarlabs.org
> > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [9]https://quozl.linux.org.au/
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://translate.sugarlabs.org/
> [3] http://wiki.sugarlabs.org/go/Service/translate
> [4] http://wiki.sugarlabs.org/go/Service/Pootle
> [5] http://wiki.sugarlabs.org/go/Service/Pootle2.5
> [6] http://wiki.sugarlabs.org/go/Machine/pootle
> [7] mailto:Sugar-devel@lists.sugarlabs.org
> [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> [9] https://quozl.linux.org.au/

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

Re: [Sugar-devel] Introduction

[SHRAY TYAGI]

Yes, I would be interested.

On Sat, 2 Jan 2021, 05:44 James Cameron,  wrote:

> Welcome.  Your experience with Django is immediately useful; we have a
> Django app called Pootle on https://translate.sugarlabs.org/ that has
> not been maintained recently.  We continue to have occasional
> translators, but I don't think we have an active translation manager.
>
> A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in
> the usual place (the wiki). There are several pages written by the
> previous Pootle maintainers:
>
>   http://wiki.sugarlabs.org/go/Service/translate
>   http://wiki.sugarlabs.org/go/Service/Pootle
>   http://wiki.sugarlabs.org/go/Service/Pootle2.5
>   http://wiki.sugarlabs.org/go/Machine/pootle
> "
>
> Is that something you're interested in?
>
> On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote:
> > Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at
> Vishwakarma
> > Institute of Technology Pune. My technical knowledge includes python,
> React JS,
> > Html, CSS,django, Mysql,data structures and basics of java, Machine
> learning, c
> > , c++. Some of my projects include a basic django todo app, car showroom
> > database management system, digit detection using neural networks, basic
> > chatbot, etc. I am very much interested in participating in GSoC 2021.
> The main
> > reason for doing GSoC is to get exposure to the developer's world and to
> work
> > with new people. I am looking forward to working under sugarlabs.
> >
> > Regards,
> > Shray Tyagi
>
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> https://quozl.linux.org.au/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction

[James Cameron]

Welcome.  Your experience with Django is immediately useful; we have a
Django app called Pootle on https://translate.sugarlabs.org/ that has
not been maintained recently.  We continue to have occasional
translators, but I don't think we have an active translation manager.

A few years ago, Bernie Innocenti wrote "Sysadmin documentation is in
the usual place (the wiki). There are several pages written by the
previous Pootle maintainers:

  http://wiki.sugarlabs.org/go/Service/translate
  http://wiki.sugarlabs.org/go/Service/Pootle
  http://wiki.sugarlabs.org/go/Service/Pootle2.5
  http://wiki.sugarlabs.org/go/Machine/pootle
"

Is that something you're interested in?

On Fri, Jan 01, 2021 at 02:16:37PM +0530, SHRAY TYAGI wrote:
> Hello, My name is Shray Tyagi and I am a 3rd-year BTech student at Vishwakarma
> Institute of Technology Pune. My technical knowledge includes python, React 
> JS,
> Html, CSS,django, Mysql,data structures and basics of java, Machine learning, 
> c
> , c++. Some of my projects include a basic django todo app, car showroom
> database management system, digit detection using neural networks, basic
> chatbot, etc. I am very much interested in participating in GSoC 2021. The 
> main
> reason for doing GSoC is to get exposure to the developer's world and to work
> with new people. I am looking forward to working under sugarlabs.
> 
> Regards,
> Shray Tyagi

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


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

Re: [Sugar-devel] Introduction

[James Cameron]

Welcome.

Thanks for your offer.  If you haven't seen it already, you will find
my getting started guide in your spam folder.  You can also find it at

https://github.com/sugarlabs/sugar-docs/blob/master/src/sugar-labs-developer-howto.txt

You can find our guide to contributing at
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

You can find our guide to setting up a development environment at
https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md

(Given your wish to port activities from Python 2 to Python 3, the
lowest cost development environment is a virtual machine instance of
Sugar Live Build installed on a virtual disk.  Only Sugar Live Build
supports both versions of Python at once now that Linux distributions
have dropped Python 2.  You would find it most efficient to use an SSH
server on the instance, and use your regular development environment
as an SSH client.  Using SSH in this way minimises the edit and test
cycle.)

You can find our Python 3 Porting Guide at
https://github.com/sugarlabs/sugar-docs/blob/master/src/python-porting-guide.md

On Wed, Dec 16, 2020 at 07:00:06PM +0530, Nihal Mittal wrote:
> Hello everyone,
> I am Nihal Mittal currently an undergraduate majoring in information
> technology. I came across sugar labs searching while searching for 
> organisation
> to contribute to and have been amazed by the sugar activities and it's impact.
> I have good amount of experience in both python and javascript. I want to 
> start
> by porting activities from python2 to python3. Any starting guide and
> prerequisite regarding this would be greatly appreciated.
> Thanks ! Regards

> ___
> 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

Re: [Sugar-devel] Introduction

[Manish Kumar Sarangi]

Hey James,

I'll be happy to work on that. I'll take some time to familiarize myself
with the codebase, and then proceed from there.

Manish

On Tue, 15 Dec 2020, 05:55 James Cameron,  wrote:

> Welcome.  Thanks for volunteering.
>
> Given your skills, one of the opportunities is to port Sugarizer
> activities back to Sugar.
>
> One of our goals has been to leverage work done on activities so that
> they are available on both Sugar and Sugarizer.  Having a Sugar Web
> library that works on both is a better outcome than having two
> separate libraries, because it will reduce maintenance.
>
> What has tended to happen is that developers who want to work on
> JavaScript are attracted to Sugarizer, and developers who want to work
> on Python are attracted to Sugar.  A division by language preference.
>
> Once an activity is accepted into Sugarizer, developers have been
> content with that dopamine hit and haven't worked to get the activity
> working in Sugar.  Firstly because of the evolution of the Sugar Web
> library inside Sugarizer, secondly because of scope constraints for
> GCI tasks or GSoC projects, and thirdly because no other developers
> have been working on JavaScript activities in Sugar.
>
> Perhaps you, being skilled in JavaScript _and_ Python, may work on the
> Sugar Web library, and port activities to Sugar.
>
> On Tue, Dec 15, 2020 at 12:32:25AM +0530, Manish Kumar Sarangi wrote:
> > Hello everyone,
> >
> > This is Manish. I'm a MERN stack developer and am quite proficient in
> Python. I
> > am interested in this project and would like to contribute to its
> growth. So
> > please tell me where to start from.
> >
> > Manish
>
> > ___
> > 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

Re: [Sugar-devel] Introduction

[James Cameron]

Welcome.  Thanks for volunteering.

Given your skills, one of the opportunities is to port Sugarizer
activities back to Sugar.

One of our goals has been to leverage work done on activities so that
they are available on both Sugar and Sugarizer.  Having a Sugar Web
library that works on both is a better outcome than having two
separate libraries, because it will reduce maintenance.

What has tended to happen is that developers who want to work on
JavaScript are attracted to Sugarizer, and developers who want to work
on Python are attracted to Sugar.  A division by language preference.

Once an activity is accepted into Sugarizer, developers have been
content with that dopamine hit and haven't worked to get the activity
working in Sugar.  Firstly because of the evolution of the Sugar Web
library inside Sugarizer, secondly because of scope constraints for
GCI tasks or GSoC projects, and thirdly because no other developers
have been working on JavaScript activities in Sugar.

Perhaps you, being skilled in JavaScript _and_ Python, may work on the
Sugar Web library, and port activities to Sugar.

On Tue, Dec 15, 2020 at 12:32:25AM +0530, Manish Kumar Sarangi wrote:
> Hello everyone,
> 
> This is Manish. I'm a MERN stack developer and am quite proficient in Python. 
> I
> am interested in this project and would like to contribute to its growth. So
> please tell me where to start from.
> 
> Manish

> ___
> 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

Re: [Sugar-devel] Introduction and query about Github repos of some activities

[Muskan Lalit]

Oh, thanks a lot!
I'll get started on it and explore around right away!
Thanks again.



On Sat, Feb 29, 2020, 12:54 AM James Cameron  wrote:

> Welcom Muskan.
>
> The Sprint Math activity is embedded in the Sugarizer repository.
>
>
> https://github.com/llaske/sugarizer/tree/master/activities/SprintMath.activity
>
> Relevant data in the same repository can be found with "git grep
> Sprint".
>
> Or you could use GitHub to search for org.sugarlabs.SprintMath
>
> For how to contribute to Sugarizer, see;
>
> https://github.com/llaske/sugarizer/blob/master/CONTRIBUTING.md
>
> On Fri, Feb 28, 2020 at 11:29:30PM +0530, Muskan Lalit wrote:
> > Hey everyone,
> >
> > This is Muskan Lalit, a 2nd year CS undergraduate. This is my first time
> > mailing an entire mailing list but the community has seemed very warm to
> > newcomers so I've finally gathered the courage to do this.
> > I am really interested in working with SugarLabs with the Sugarizer
> Desktop
> > application. As I was exploring the application, I found some issues/
> > enhancements that can be done with some activities that I would like to
> work
> > with but I can't seem to find the GitHub repos for the same like the
> Sprint
> > Math Activity.
> >
> > Any help would be greatly appreciated
>
> > ___
> > 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

Re: [Sugar-devel] Introduction and query about Github repos of some activities

[James Cameron]

Welcom Muskan.

The Sprint Math activity is embedded in the Sugarizer repository.

https://github.com/llaske/sugarizer/tree/master/activities/SprintMath.activity

Relevant data in the same repository can be found with "git grep
Sprint".

Or you could use GitHub to search for org.sugarlabs.SprintMath

For how to contribute to Sugarizer, see;

https://github.com/llaske/sugarizer/blob/master/CONTRIBUTING.md

On Fri, Feb 28, 2020 at 11:29:30PM +0530, Muskan Lalit wrote:
> Hey everyone,
> 
> This is Muskan Lalit, a 2nd year CS undergraduate. This is my first time
> mailing an entire mailing list but the community has seemed very warm to
> newcomers so I've finally gathered the courage to do this.
> I am really interested in working with SugarLabs with the Sugarizer Desktop
> application. As I was exploring the application, I found some issues/
> enhancements that can be done with some activities that I would like to work
> with but I can't seem to find the GitHub repos for the same like the Sprint
> Math Activity.
> 
> Any help would be greatly appreciated

> ___
> 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

Re: [Sugar-devel] Introduction box code

[James Cameron]

Which application?

On Sat, Feb 08, 2020 at 08:15:03PM +0530, Rahul kohli wrote:
> In which file the code is available for introduction box which
> introduce us to the application?

-- 
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] Introduction to the community.

[Rahul Bothra]

Hello Amey,

See
https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md



On Sun, Aug 18, 2019 at 2:59 PM Amey Bhosle  wrote:

> Hello, My name is  Amey Bhosle and am  pursuing UG from India. My skills
> includes HTML, CSS, JavaScript, Python. I checked out this project and
> found it interesting as per my skills. I am a lot interested to contribute
> to this project. So, can anyone guide to make my first contribution and be
> part of this great community.
>
> Thanks
> Amey Bhosle
> ___
> 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] Introduction to community

[James Cameron]

Thanks for asking.  All tasks contain some design.  There is more to
do than can possibly be done.  We don't have time to make a list.

Could you please self-direct?  Please use Sugar, Sugarizer or Music
Blocks, and choose what to work on, based on;

* your time,

* your interest,

* your equipment,

* how many other people are also interested, and;

* your previous experience with the languages, tools, and operating
  systems.

You are always the best judge of these things.  If you fail in one of
these areas, you can self-improve.

Lionel can tell you what needs doing in Sugarizer.  Walter 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,

* adaption of Sugar to high resolution displays,

* review and testing of work by others.

You began looking at www-sugarlabs.  New developers should avoid
changes to our infrastructure, such as web sites and documentation,
until they have demonstrated ongoing contribution to Sugar, Sugarizer
or Music Blocks.

On Mon, Jul 29, 2019 at 02:32:11AM +0100, Oluebube Oti wrote:
> Am a junior product designer and software developer mostly front-end, with 
> five months of experience in UI/UX Design, I also help to implement the 
> designs into an actuall product. Please how can I joint the community and 
> contribute as a UI/UX designer or Web designer? Recently I cloned the 
> www.sugarlabs.org repo, had some issues on windows. When I asked the 
> community for help realized I need Linux OS to contribute. Please while I 
> work on that is their any design project I can work on?
> 
> > On Jul 29, 2019, at 2:15 AM, James Cameron  wrote:
> > 
> > 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  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 

Re: [Sugar-devel] Introduction to community

[Oluebube Oti]

Am a junior product designer and software developer mostly front-end, with five 
months of experience in UI/UX Design, I also help to implement the designs into 
an actuall product. Please how can I joint the community and contribute as a 
UI/UX designer or Web designer? Recently I cloned the www.sugarlabs.org repo, 
had some issues on windows. When I asked the community for help realized I need 
Linux OS to contribute. Please while I work on that is their any design project 
I can work on?

> On Jul 29, 2019, at 2:15 AM, James Cameron  wrote:
> 
> 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  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 

Re: [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  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 

Re: [Sugar-devel] Introduction to community

[Oluebube Oti]

How about how to get started as a designer?

Sent from my iPhone

> On Jul 28, 2019, at 11:51 PM, James Cameron  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/
> 

Re: [Sugar-devel] Introduction to community

[James Cameron]

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

Re: [Sugar-devel] Introduction

[Shubhika Bhardwaj]

Thanks, I'll check them out.

On Sun, Mar 31, 2019 at 5:21 AM Chihurumnaya Ibiam <
ibiamchihurumn...@gmail.com> wrote:

> Hi Shubhika,
>
>  They're some ideas for the type of activities to be created in the ideas
> page, feel free to add more ideas but these ideas should be new and not
> already in existence as sugar activities. You can visit
> activities.sugarlabs.org to view existing activities.
>
> On Fri, Mar 29, 2019, 6:27 PM Shubhika Bhardwaj <
> shubhikabhard...@gmail.com> wrote:
>
>> Hi !
>> I am Shubhika Bhardwaj.I am studying Bachelor of Technology in Computer
>> Science. I am currently in my second year.
>>
>> I am interested in the idea of creating a new set of activities. Can we
>> theme our activity on any technical topic of our choice.
>> ___
>> 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] Introduction

[Chihurumnaya Ibiam]

Hi Shubhika,

 They're some ideas for the type of activities to be created in the ideas
page, feel free to add more ideas but these ideas should be new and not
already in existence as sugar activities. You can visit
activities.sugarlabs.org to view existing activities.

On Fri, Mar 29, 2019, 6:27 PM Shubhika Bhardwaj 
wrote:

> Hi !
> I am Shubhika Bhardwaj.I am studying Bachelor of Technology in Computer
> Science. I am currently in my second year.
>
> I am interested in the idea of creating a new set of activities. Can we
> theme our activity on any technical topic of our choice.
> ___
> 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] Introduction

[James Cameron]

Welcome Yash.

Please choose some of the ideas you are really interested in, read
them carefully, look for ambiguities or places where information is
missing, and ask questions here on sugar-devel@.  We may then work
together to improve the ideas.

Please don't talk privately with mentors about the ideas, unless a
mentor has specifically asked you to.  Sugar Labs benefits most from
public discussion.  See our Code of Conduct for more details on
expected behaviour;


https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md

There are plenty of things you can do to improve your suitability; see
"How can I help?" and "Contribute code";

https://github.com/sugarlabs/sugar-docs

Also do some deep learning and practice with the technologies and
tools.  Given your experience with MERN, you might learn the other
tools used by Sugarizer.  See the repository for Sugarizer, both the
master and dev branches;

https://github.com/llaske/sugarizer

On Wed, Feb 20, 2019 at 06:25:54PM +0530, Yash Mehrotra wrote:
> *
> Hello all,
> My name is Yash Mehrotra I am a second year IT student and have experience 
> with
> MERN stack. I want to work with sugar labs for GSoC 2019. 
> I went through the ideas list and found some ideas really interesting, how
> should I proceed now .. :)
> Thanks in advance.
> 
> [1]Mailtrack  Sender notified by
>   [2]Mailtrack 20/02/19, 12:44:08 pm
> 
> References:
> 
> [1] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality5;
> [2] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality5;

> ___
> 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

Re: [Sugar-devel] introduction

[James Cameron]

Welcome, Amarjeet.

On Sun, Jan 20, 2019 at 11:06:05PM +0530, amarjeet singh wrote:
> Hello; I am Amarjeet Singh, I am an undergraduate student  studying
> computer science in Jaypee University of Engineering & technology,
> my knowledge skills include Javascript, Python, HTML and CSS, I am
> very much interested in contributing for open source and sugar labs 
> has some impressive ideas and project to work with and I am very
> much interested in contributing to this, and I acknowledge that I am
> a good and fast learner. :)

-- 
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] Introduction and review request of GSoC Proposal:

[Frederick Grose]

On Mon, Mar 26, 2018 at 2:10 AM, James Cameron  wrote:

> I don't know.  I don't have administrator rights on the Wiki.  Hope
> Walter or someone else can answer.  Meanwhile, I've been replacing
> migrated pages with links to the new location, so that old links don't
> break.
>

​This method should be preferred.  It is easy and effective, doesn't
destroy history, and points toward where you want people to look.
​

>
> On Mon, Mar 26, 2018 at 11:31:49AM +0530, Rudra Sadhu wrote:
> > thanks James for the assessment.
> >
> > I've successfully migrated a few of the pages from [1]https://
> > wiki.sugarlabs.org/go/Activities to GitHub
> > Find the pull request at [2]https://github.com/
> godiard/help-activity/pull/38
> >
> > and now, the wiki-pages needs to be deprecated.
> > As to delete a page from the wiki, an user needs 'administrators' rights,
> >
> > thus,
> > Some possible ways to delete the pages are:
> > 1. create a bot account with restricted permissions which can delete
> pages(my
> > preferred choice)
> > 2. for a temporary period grant delete rights to me
> > 3. someone trusted deletes the pages
> > 4. something else and better (please suggest)
> >
> > It may not be convenient to delete the pages manually as there will be
> > thousands of those(including extra images/files attached to the pages)
> for the
> > 345 pages to be migrated
> > All of the deletion is preferred to be done by a script (which
> uses [3]https://
> > www.mediawiki.org/wiki/API:Delete), under close supervision
> > Do not worry, no damage(if at all) will be permanent; since it is
> possible to
> > always recover pages deleted by an user with 'administrators' rights.
> Read [4]
> > https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion
> >
> > Please recommend the desired course of action
> >
> > thanks,
> > Rudra Sadhu
> >
> > On Mon, Mar 26, 2018 at 10:41 AM, James Cameron <[5]qu...@laptop.org>
> wrote:
> >
> > Thanks, I've reviewed your updated proposal.
> >
> > My assessment of project impact;
> >
> > Originally documentation was separate because we had non-coding
> > developers and tool chains that varied by type of developer.  Now we
> > use GitHub the tool chains are combined.
> >
> > With the project as described, documentation will be concentrated in
> > the source code repository for an activity, reducing ongoing
> > maintenance.
> >
> > We have less active Wiki contributors than we ever did, and in the
> > current threat environment a Wiki requires significant monitoring and
> > administration; we recently lost some system administrators and
> gained
> > new ones; using GitHub allows us to outsource system administration.
> >
> > On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > > Thanks James, Carlos, Gonzalo and everyone for the insights
> > >
> > > Your inputs helped a lot, and I've updated my proposal accordingly.
> > > A lot of important stuff was added such as the working the Help
> Activity,
> > > keeping check on the activity bundle sizes and completing the
> > miscellaneous
> > > section.
> > >
> > > The proposal is available at [1][6]https://wiki.sugarlabs.org/go/
> > Summer_of_Code/
> > > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > > I've also shared the same via the GSoC dashboard
> > > Please read, most importantly the 'About Project' section
> > >
> > > Let me know of the stuff I should add/remove/update to better
> justify the
> > > task.
> > >
> > > also It would help, if someone volunteers to answer the impact of
> this
> > project
> > > required to be filled in as an answer in the 'Project and the
> Community'
> > > section
> > >
> > > Thanks
> > > Rudra Sadhu
> > >
> > > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2][7]
> rdrsa...@gmail.com>
> > wrote:
> > >
> > > Thanks James,
> > > the resources you mentioned were really helpful.
> > >
> > > I went ahead to migrate a few of the pages by the guidelines
> you
> > described.
> > > Find the Pull Request here: [3][8]https://github.
> com/sugarlabs/
> > activity-abacus
> > > /pull/13
> > >
> > > Please review
> > >
> > > On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4][9]
> > qu...@laptop.org> wrote:
> > >
> > > On IRC #sugar Vipul Gupta asked;
> > >
> > >  Hey, in the Activity task of migration.
> We need
> > to
> > > migrate content from activities page to their Githubs or
> their
> > git
> > > pages.
> > >
> > >  ?
> > >
> > >  Please clarify which one is it. Some
> pages don't
> > have
> > > the links of their repository
> > >
> > >  The organisations is not uniform. I have
> > included
> > > this in my 

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[James Cameron]

I don't know.  I don't have administrator rights on the Wiki.  Hope
Walter or someone else can answer.  Meanwhile, I've been replacing
migrated pages with links to the new location, so that old links don't
break.

On Mon, Mar 26, 2018 at 11:31:49AM +0530, Rudra Sadhu wrote:
> thanks James for the assessment.
> 
> I've successfully migrated a few of the pages from [1]https://
> wiki.sugarlabs.org/go/Activities to GitHub
> Find the pull request at [2]https://github.com/godiard/help-activity/pull/38
> 
> and now, the wiki-pages needs to be deprecated.
> As to delete a page from the wiki, an user needs 'administrators' rights,
> 
> thus,
> Some possible ways to delete the pages are:
> 1. create a bot account with restricted permissions which can delete pages(my
> preferred choice)
> 2. for a temporary period grant delete rights to me
> 3. someone trusted deletes the pages
> 4. something else and better (please suggest)
> 
> It may not be convenient to delete the pages manually as there will be
> thousands of those(including extra images/files attached to the pages) for the
> 345 pages to be migrated
> All of the deletion is preferred to be done by a script (which uses 
> [3]https://
> www.mediawiki.org/wiki/API:Delete), under close supervision
> Do not worry, no damage(if at all) will be permanent; since it is possible to
> always recover pages deleted by an user with 'administrators' rights. Read [4]
> https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion
> 
> Please recommend the desired course of action
> 
> thanks,
> Rudra Sadhu
> 
> On Mon, Mar 26, 2018 at 10:41 AM, James Cameron <[5]qu...@laptop.org> wrote:
> 
> Thanks, I've reviewed your updated proposal.
> 
> My assessment of project impact;
> 
> Originally documentation was separate because we had non-coding
> developers and tool chains that varied by type of developer.  Now we
> use GitHub the tool chains are combined.
> 
> With the project as described, documentation will be concentrated in
> the source code repository for an activity, reducing ongoing
> maintenance.
> 
> We have less active Wiki contributors than we ever did, and in the
> current threat environment a Wiki requires significant monitoring and
> administration; we recently lost some system administrators and gained
> new ones; using GitHub allows us to outsource system administration.
>
> On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > Thanks James, Carlos, Gonzalo and everyone for the insights
> >
> > Your inputs helped a lot, and I've updated my proposal accordingly.
> > A lot of important stuff was added such as the working the Help 
> Activity,
> > keeping check on the activity bundle sizes and completing the
> miscellaneous
> > section.
> >
> > The proposal is available at [1][6]https://wiki.sugarlabs.org/go/
> Summer_of_Code/
> > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > I've also shared the same via the GSoC dashboard
> > Please read, most importantly the 'About Project' section
> >
> > Let me know of the stuff I should add/remove/update to better justify 
> the
> > task. 
> >
> > also It would help, if someone volunteers to answer the impact of this
> project
> > required to be filled in as an answer in the 'Project and the Community'
> > section 
> >
> > Thanks
> > Rudra Sadhu
> >
> > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2][7]rdrsa...@gmail.com>
> wrote:
> >
> >     Thanks James,
> >     the resources you mentioned were really helpful.
> >
> >     I went ahead to migrate a few of the pages by the guidelines you
> described.
> >     Find the Pull Request here: [3][8]https://github.com/sugarlabs/
> activity-abacus
> >     /pull/13
> >
> >     Please review
> >
> >     On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4][9]
> qu...@laptop.org> wrote:
> >
> >         On IRC #sugar Vipul Gupta asked;
> >
> >          Hey, in the Activity task of migration. We need
> to
> >         migrate content from activities page to their Githubs or their
> git
> >         pages.
> >
> >          ?
> >
> >          Please clarify which one is it. Some pages 
> don't
> have
> >         the links of their repository
> >
> >          The organisations is not uniform. I have
> included
> >         this in my proposal too.
> >
> >          vipulgupta2048: need to write a program that will
> migrate
> >         content from [5][10]wiki.sugarlabs.org activities page to
> respective GitHub
> >         repository README.md files, yet without duplicating what is
> there, and
> >         without duplicating user documentation in the help-activity, see
> >         recent posts to sugar-devel@ discussing the issue.
> >
> >      

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[Rudra Sadhu]

thanks James for the assessment.

I've successfully migrated a few of the pages from
https://wiki.sugarlabs.org/go/Activities to GitHub
Find the pull request at https://github.com/godiard/help-activity/pull/38

and now, the wiki-pages needs to be deprecated.
As to delete a page from the wiki, an user needs 'administrators' rights,

thus,
Some possible ways to delete the pages are:
1. create a bot account with restricted permissions which can delete
pages(my preferred choice)
2. for a temporary period grant delete rights to me
3. someone trusted deletes the pages
4. something else and better (please suggest)

It may not be convenient to delete the pages manually as there will be
thousands of those(including extra images/files attached to the pages) for
the 345 pages to be migrated
All of the deletion is preferred to be done by a script (which uses
https://www.mediawiki.org/wiki/API:Delete), under close supervision
Do not worry, no damage(if at all) will be permanent; since it is possible
to always recover pages deleted by an user with 'administrators' rights.
Read https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion

Please recommend the desired course of action

thanks,
Rudra Sadhu


On Mon, Mar 26, 2018 at 10:41 AM, James Cameron  wrote:

> Thanks, I've reviewed your updated proposal.
>
> My assessment of project impact;
>
> Originally documentation was separate because we had non-coding
> developers and tool chains that varied by type of developer.  Now we
> use GitHub the tool chains are combined.
>
> With the project as described, documentation will be concentrated in
> the source code repository for an activity, reducing ongoing
> maintenance.
>
> We have less active Wiki contributors than we ever did, and in the
> current threat environment a Wiki requires significant monitoring and
> administration; we recently lost some system administrators and gained
> new ones; using GitHub allows us to outsource system administration.
>
> On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > Thanks James, Carlos, Gonzalo and everyone for the insights
> >
> > Your inputs helped a lot, and I've updated my proposal accordingly.
> > A lot of important stuff was added such as the working the Help Activity,
> > keeping check on the activity bundle sizes and completing the
> miscellaneous
> > section.
> >
> > The proposal is available at [1]https://wiki.sugarlabs.
> org/go/Summer_of_Code/
> > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > I've also shared the same via the GSoC dashboard
> > Please read, most importantly the 'About Project' section
> >
> > Let me know of the stuff I should add/remove/update to better justify the
> > task.
> >
> > also It would help, if someone volunteers to answer the impact of this
> project
> > required to be filled in as an answer in the 'Project and the Community'
> > section
> >
> > Thanks
> > Rudra Sadhu
> >
> > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2]rdrsa...@gmail.com>
> wrote:
> >
> > Thanks James,
> > the resources you mentioned were really helpful.
> >
> > I went ahead to migrate a few of the pages by the guidelines you
> described.
> > Find the Pull Request here: [3]https://github.com/
> sugarlabs/activity-abacus
> > /pull/13
> >
> > Please review
> >
> > On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4]qu...@laptop.org>
> wrote:
> >
> > On IRC #sugar Vipul Gupta asked;
> >
> >  Hey, in the Activity task of migration. We need
> to
> > migrate content from activities page to their Githubs or their
> git
> > pages.
> >
> >  ?
> >
> >  Please clarify which one is it. Some pages
> don't have
> > the links of their repository
> >
> >  The organisations is not uniform. I have
> included
> > this in my proposal too.
> >
> >  vipulgupta2048: need to write a program that will
> migrate
> > content from [5]wiki.sugarlabs.org activities page to
> respective GitHub
> > repository README.md files, yet without duplicating what is
> there, and
> > without duplicating user documentation in the help-activity, see
> > recent posts to sugar-devel@ discussing the issue.
> >
> >  vipulgupta2048: did you get the above?  if not, i'll
> have to
> > write a mail.
> >
> > My recent post is quoted below and can be found in the mailing
> list
> > archives.
> >
> > On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
> > > G'day Rudra,
> > >
> > > Thanks for being at the meeting earlier, and for your proposal.
> > >
> > > A project for GSoC 2013 added context sensitive help, or user
> > > documentation, to the Sugar desktop, with alt+shift+h key.
> > >
> > > It works with the Help activity.  Metadata in the Help
> activity links
> > a
> > > subject activity to a markdown source 

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[James Cameron]

Thanks, I've reviewed your updated proposal.

My assessment of project impact;

Originally documentation was separate because we had non-coding
developers and tool chains that varied by type of developer.  Now we
use GitHub the tool chains are combined.

With the project as described, documentation will be concentrated in
the source code repository for an activity, reducing ongoing
maintenance.

We have less active Wiki contributors than we ever did, and in the
current threat environment a Wiki requires significant monitoring and
administration; we recently lost some system administrators and gained
new ones; using GitHub allows us to outsource system administration.

On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> Thanks James, Carlos, Gonzalo and everyone for the insights
> 
> Your inputs helped a lot, and I've updated my proposal accordingly.
> A lot of important stuff was added such as the working the Help Activity,
> keeping check on the activity bundle sizes and completing the miscellaneous
> section.
> 
> The proposal is available at [1]https://wiki.sugarlabs.org/go/Summer_of_Code/
> 2018/attentive_migration_of_wiki_activity_pages_to_git
> I've also shared the same via the GSoC dashboard
> Please read, most importantly the 'About Project' section
> 
> Let me know of the stuff I should add/remove/update to better justify the
> task. 
> 
> also It would help, if someone volunteers to answer the impact of this project
> required to be filled in as an answer in the 'Project and the Community'
> section 
> 
> Thanks
> Rudra Sadhu
> 
> On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2]rdrsa...@gmail.com> wrote:
> 
> Thanks James,
> the resources you mentioned were really helpful.
> 
> I went ahead to migrate a few of the pages by the guidelines you 
> described.
> Find the Pull Request here: 
> [3]https://github.com/sugarlabs/activity-abacus
> /pull/13
> 
> Please review
> 
> On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4]qu...@laptop.org> 
> wrote:
> 
> On IRC #sugar Vipul Gupta asked;
> 
>  Hey, in the Activity task of migration. We need to
> migrate content from activities page to their Githubs or their git
> pages.
> 
>  ?
> 
>  Please clarify which one is it. Some pages don't have
> the links of their repository
> 
>  The organisations is not uniform. I have included
> this in my proposal too.
> 
>  vipulgupta2048: need to write a program that will migrate
> content from [5]wiki.sugarlabs.org activities page to respective 
> GitHub
> repository README.md files, yet without duplicating what is there, and
> without duplicating user documentation in the help-activity, see
> recent posts to sugar-devel@ discussing the issue.
> 
>  vipulgupta2048: did you get the above?  if not, i'll have to
> write a mail.
> 
> My recent post is quoted below and can be found in the mailing list
> archives.
> 
> On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
> > G'day Rudra,
> >
> > Thanks for being at the meeting earlier, and for your proposal.
> >
> > A project for GSoC 2013 added context sensitive help, or user
> > documentation, to the Sugar desktop, with alt+shift+h key.
> >
> > It works with the Help activity.  Metadata in the Help activity 
> links
> a
> > subject activity to a markdown source file, which is converted to
> HTML
> > and rendered in a tiny browser.
> >
> > Many of these source files came from the Wiki pages of activities,
> and
> > have been updated since then.
> >
> > Please review and integrate the Help activity into your proposal; 
> for
> > instance;
> >
> > - avoid duplicating user documentation into activity repositories,
> >   because that would make for unncessary maintenance burden, or;
> >
> > - move some of the Help activity files into activity repositories 
> and
> >   provide a way to update the Help activity from the subject
> >   activities.
> >
> > Please review the discussion on these two pull requests;
> >
> > [6]https://github.com/sugarlabs/activity-abacus/pull/12
> > [7]https://github.com/sugarlabs/sugar-docs/pull/137
> >
> > And then ask any questions to clarify, thanks.
> >
> > --
> > James Cameron
> > [8]http://quozl.netrek.org/
> 
> --
> James Cameron
> [9]http://quozl.netrek.org/
> 
> References:
> 
> [1] 
> https://wiki.sugarlabs.org/go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git
> [2] mailto:rdrsa...@gmail.com
> [3] https://github.com/sugarlabs/activity-abacus/pull/13
> [4] mailto:qu...@laptop.org
> [5] 

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[Rudra Sadhu]

Thanks James, Carlos, Gonzalo and everyone for the insights

Your inputs helped a lot, and I've updated my proposal accordingly.
A lot of important stuff was added such as the working the Help Activity,
keeping check on the activity bundle sizes and completing the miscellaneous
section.

The proposal is available at https://wiki.sugarlabs.org/
go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git
I've also shared the same via the GSoC dashboard
Please read, most importantly the 'About Project' section

Let me know of the stuff I should add/remove/update to better justify the
task.

also It would help, if someone volunteers to answer the impact of this
project required to be filled in as an answer in the 'Project and the
Community' section

Thanks
Rudra Sadhu

On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu  wrote:

> Thanks James,
> the resources you mentioned were really helpful.
>
> I went ahead to migrate a few of the pages by the guidelines you described.
> Find the Pull Request here: https://github.com/sugar
> labs/activity-abacus/pull/13
>
> Please review
>
>
> On Wed, Mar 21, 2018 at 4:32 AM, James Cameron  wrote:
>
>> On IRC #sugar Vipul Gupta asked;
>>
>>  Hey, in the Activity task of migration. We need to
>> migrate content from activities page to their Githubs or their git
>> pages.
>>
>>  ?
>>
>>  Please clarify which one is it. Some pages don't have
>> the links of their repository
>>
>>  The organisations is not uniform. I have included
>> this in my proposal too.
>>
>>  vipulgupta2048: need to write a program that will migrate
>> content from wiki.sugarlabs.org activities page to respective GitHub
>> repository README.md files, yet without duplicating what is there, and
>> without duplicating user documentation in the help-activity, see
>> recent posts to sugar-devel@ discussing the issue.
>>
>>  vipulgupta2048: did you get the above?  if not, i'll have to
>> write a mail.
>>
>> My recent post is quoted below and can be found in the mailing list
>> archives.
>>
>> On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
>> > G'day Rudra,
>> >
>> > Thanks for being at the meeting earlier, and for your proposal.
>> >
>> > A project for GSoC 2013 added context sensitive help, or user
>> > documentation, to the Sugar desktop, with alt+shift+h key.
>> >
>> > It works with the Help activity.  Metadata in the Help activity links a
>> > subject activity to a markdown source file, which is converted to HTML
>> > and rendered in a tiny browser.
>> >
>> > Many of these source files came from the Wiki pages of activities, and
>> > have been updated since then.
>> >
>> > Please review and integrate the Help activity into your proposal; for
>> > instance;
>> >
>> > - avoid duplicating user documentation into activity repositories,
>> >   because that would make for unncessary maintenance burden, or;
>> >
>> > - move some of the Help activity files into activity repositories and
>> >   provide a way to update the Help activity from the subject
>> >   activities.
>> >
>> > Please review the discussion on these two pull requests;
>> >
>> > https://github.com/sugarlabs/activity-abacus/pull/12
>> > https://github.com/sugarlabs/sugar-docs/pull/137
>> >
>> > And then ask any questions to clarify, thanks.
>> >
>> > --
>> > James Cameron
>> > http://quozl.netrek.org/
>>
>> --
>> 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] Introduction and review request of GSoC Proposal:

[Rudra Sadhu]

Thanks James,
the resources you mentioned were really helpful.

I went ahead to migrate a few of the pages by the guidelines you described.
Find the Pull Request here:
https://github.com/sugarlabs/activity-abacus/pull/13

Please review


On Wed, Mar 21, 2018 at 4:32 AM, James Cameron  wrote:

> On IRC #sugar Vipul Gupta asked;
>
>  Hey, in the Activity task of migration. We need to
> migrate content from activities page to their Githubs or their git
> pages.
>
>  ?
>
>  Please clarify which one is it. Some pages don't have
> the links of their repository
>
>  The organisations is not uniform. I have included
> this in my proposal too.
>
>  vipulgupta2048: need to write a program that will migrate
> content from wiki.sugarlabs.org activities page to respective GitHub
> repository README.md files, yet without duplicating what is there, and
> without duplicating user documentation in the help-activity, see
> recent posts to sugar-devel@ discussing the issue.
>
>  vipulgupta2048: did you get the above?  if not, i'll have to
> write a mail.
>
> My recent post is quoted below and can be found in the mailing list
> archives.
>
> On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
> > G'day Rudra,
> >
> > Thanks for being at the meeting earlier, and for your proposal.
> >
> > A project for GSoC 2013 added context sensitive help, or user
> > documentation, to the Sugar desktop, with alt+shift+h key.
> >
> > It works with the Help activity.  Metadata in the Help activity links a
> > subject activity to a markdown source file, which is converted to HTML
> > and rendered in a tiny browser.
> >
> > Many of these source files came from the Wiki pages of activities, and
> > have been updated since then.
> >
> > Please review and integrate the Help activity into your proposal; for
> > instance;
> >
> > - avoid duplicating user documentation into activity repositories,
> >   because that would make for unncessary maintenance burden, or;
> >
> > - move some of the Help activity files into activity repositories and
> >   provide a way to update the Help activity from the subject
> >   activities.
> >
> > Please review the discussion on these two pull requests;
> >
> > https://github.com/sugarlabs/activity-abacus/pull/12
> > https://github.com/sugarlabs/sugar-docs/pull/137
> >
> > And then ask any questions to clarify, thanks.
> >
> > --
> > James Cameron
> > http://quozl.netrek.org/
>
> --
> 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] Introduction and review request of GSoC Proposal:

[James Cameron]

On IRC #sugar Vipul Gupta asked;

 Hey, in the Activity task of migration. We need to
migrate content from activities page to their Githubs or their git
pages.

 ?

 Please clarify which one is it. Some pages don't have
the links of their repository

 The organisations is not uniform. I have included
this in my proposal too.

 vipulgupta2048: need to write a program that will migrate
content from wiki.sugarlabs.org activities page to respective GitHub
repository README.md files, yet without duplicating what is there, and
without duplicating user documentation in the help-activity, see
recent posts to sugar-devel@ discussing the issue.

 vipulgupta2048: did you get the above?  if not, i'll have to
write a mail.

My recent post is quoted below and can be found in the mailing list
archives.

On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
> G'day Rudra,
> 
> Thanks for being at the meeting earlier, and for your proposal.
> 
> A project for GSoC 2013 added context sensitive help, or user
> documentation, to the Sugar desktop, with alt+shift+h key.
> 
> It works with the Help activity.  Metadata in the Help activity links a
> subject activity to a markdown source file, which is converted to HTML
> and rendered in a tiny browser.
> 
> Many of these source files came from the Wiki pages of activities, and
> have been updated since then.
> 
> Please review and integrate the Help activity into your proposal; for
> instance;
> 
> - avoid duplicating user documentation into activity repositories,
>   because that would make for unncessary maintenance burden, or;
> 
> - move some of the Help activity files into activity repositories and
>   provide a way to update the Help activity from the subject
>   activities.
> 
> Please review the discussion on these two pull requests;
> 
> https://github.com/sugarlabs/activity-abacus/pull/12
> https://github.com/sugarlabs/sugar-docs/pull/137
> 
> And then ask any questions to clarify, thanks.
> 
> -- 
> James Cameron
> http://quozl.netrek.org/

-- 
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] Introduction and review request of GSoC Proposal:

[James Cameron]

G'day Rudra,

Thanks for being at the meeting earlier, and for your proposal.

A project for GSoC 2013 added context sensitive help, or user
documentation, to the Sugar desktop, with alt+shift+h key.

It works with the Help activity.  Metadata in the Help activity links a
subject activity to a markdown source file, which is converted to HTML
and rendered in a tiny browser.

Many of these source files came from the Wiki pages of activities, and
have been updated since then.

Please review and integrate the Help activity into your proposal; for
instance;

- avoid duplicating user documentation into activity repositories,
  because that would make for unncessary maintenance burden, or;

- move some of the Help activity files into activity repositories and
  provide a way to update the Help activity from the subject
  activities.

Please review the discussion on these two pull requests;

https://github.com/sugarlabs/activity-abacus/pull/12
https://github.com/sugarlabs/sugar-docs/pull/137

And then ask any questions to clarify, thanks.

-- 
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] Introduction and review request of GSoC Proposal:

[Carlos mauro]

Hi Rudra

Look nice the proposal you will talk more that in the  meeting with more
details in the Sugarlabs.org meeting at at 5PM US/Eastern (9PM UTC) and get
more feedback from the community.

I suggest try to complete the Miscellaneous section is important to try to
understand the enviroment. Unless Walter, James, Ignacio or other member
consider or confirm if it's ok.



El 13 mar. 2018 3:07 p. m., "Rudra Sadhu"  escribió:

> Hello everyone!
> My name is Rudra Sadhu,
> and this is my first email to the sugar-developer mailing list.
>
> I've been learning about the Sugar Labs community since the past one month.
> lurking in IRC channels, using the sugar desktop environment, reading
> mailing-list archives, exploring different parts of the wiki and codebase,
> to better understand this community.
>
> Application window for GSoC 2018 has opened and I'm interested to work
> with Sugar Labs this summer.
> For the project: 'Migration of wiki activity pages to git'
> I've drafted a well thought implementation workflow, with all necessary
> details.
> Please find the proposal at https://wiki.sugarlabs.org/
> go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git
>
> I would love to discuss a lot more about different aspects of the proposal
> in detail.
> Let me know of everything you feel about the proposal, pointers on how it
> could be improved and please point out any mistakes you find.
>
> Your review and valuable feedback is important for the success of this
> project.
>
> Thanks,
> Rudra Sadhu
> email : rdrsa...@gmail.com
> IRC : rdrsadhu
>
> ___
> 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] Introduction for GSoC

[Glide]

Hello Utkarsh,

Glad to see you're interested in participating in our open source
organization.

Below are some useful links to hopefully get you started:

Sugar labs wiki for GSoC: https://wiki.sugarlabs.org/go/Summer_of_Code

GSoC's full timeline so you can know exactly when to start sending in your
proposals: https://summerofcode.withgoogle.com/how-it-works/#timeline

Here is the link to the list of projects available to work on  in this
year's GSoC: https://wiki.sugarlabs.org/go/Summer_of_Code/2018


Warm welcome to the organization and good luck on GSoC 2018.

Best Regards,
Abdul

On Mon, Feb 19, 2018 at 1:33 PM, utkarsh shukla 
wrote:

> Hi,
> I am Utkarsh Shukla, a C.S. Sophomore at IIT Roorkee.
> My special area of development is in javascript . Recently I helped my
> on-campus student group SDSLabs to develop a p2p media streaming website
> using vanilla WebRTC from scratch.
> I am interested in SugarLabs organisation as it  specialises in JavaScript
> "Applets" and web hosting.  I would like to contribute to SugarLabs via
> GSoC.
> Please help me to contribute to the projects, as to further work with the
> org.
> Thanks
> Utkarsh Shukla Github: https://github.com/utkarsh858
>
>
>
> On 18 February 2018 at 18:19, utkarsh shukla 
> wrote:
>
>> Hi,
>> I am Utkarsh Shukla, a C.S. Sophomore at IIT Roorkee.
>> My special area of development is in javascript . Recently I helped my
>> on-campus student group SDSLabs to develop a p2p media streaming website
>> using vanilla WebRTC from scratch.
>> I am interested in SugarLabs organisation as it  specialises in
>> JavaScript "Applets" and web hosting.  I would like to contribute to
>> SugarLabs via GSoC.
>> Please help me to contribute to the projects, as to further work with the
>> org.
>> Thanks
>> Utkarsh Shukla Github: https://github.com/utkarsh858
>>
>
>
> ___
> 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] Introduction for GSoC

[utkarsh shukla]

Hi,
I am Utkarsh Shukla, a C.S. Sophomore at IIT Roorkee.
My special area of development is in javascript . Recently I helped my
on-campus student group SDSLabs to develop a p2p media streaming website
using vanilla WebRTC from scratch.
I am interested in SugarLabs organisation as it  specialises in JavaScript
"Applets" and web hosting.  I would like to contribute to SugarLabs via
GSoC.
Please help me to contribute to the projects, as to further work with the
org.
Thanks
Utkarsh Shukla Github: https://github.com/utkarsh858



On 18 February 2018 at 18:19, utkarsh shukla 
wrote:

> Hi,
> I am Utkarsh Shukla, a C.S. Sophomore at IIT Roorkee.
> My special area of development is in javascript . Recently I helped my
> on-campus student group SDSLabs to develop a p2p media streaming website
> using vanilla WebRTC from scratch.
> I am interested in SugarLabs organisation as it  specialises in JavaScript
> "Applets" and web hosting.  I would like to contribute to SugarLabs via
> GSoC.
> Please help me to contribute to the projects, as to further work with the
> org.
> Thanks
> Utkarsh Shukla Github: https://github.com/utkarsh858
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction | Interest in Sugarizer Project | Doubts regarding build server setup

[Manraj Singh]

Hey Aaron! Nice to meet you too! Thank you for such prompt response.

I'm not sure of your IRC name. Please share it with me.

Yes, I was facing this issue after running the following step:

$ sudo mongod --fork --port 27018 --logpath /home/root/mongo.log

But now, it got fix itself after restarting just now. I will still share
the logs when I got this error.

http://pastebin.com/rKKb14Sa

>Also, after you post the logs, would you try this command instead?
>
>   $ mkdir ~/mongodb
>   $ mongod --dbpath /home/manrajsingh/mongodb --port 27018 --logpath
/home/manrajsingh/mongo.log

These seem to be working. No error while running them.
I'm using Ubuntu 14.04 64bit.

Regards,
Manraj Singh Grover
Find me on Github 
Connect on LinkedIN 

On Thu, Mar 10, 2016 at 9:59 PM, Aaron D Borden  wrote:

> On Thu, 2016-03-10 at 00:39 -0800, Manraj Singh <
> manrajsinghgro...@gmail.com> wrote:
> > Hello community members,
> >
> > I'm Manraj Singh, studying in Netaji Subhas Institute Of Technology(Delhi
> > University). I'm an Open Source Enthusiast and have previously
> contributed
> > to jQuery, Mozilla and Privly. I also have prior experience in working
> for
> > startups like Zomato and Refiral and have a good competitve coding
> profile.
>
> Hello! It's nice to meet you, Manraj! I'm a web developer in San
> Francisco of the US. I saw your message in IRC, so you can ping me there
> if it's easier for you. I've heard feedback that the server setup
> instructions don't always work and they're structured more like you
> would for deployment rather than development. Hopefully with your help
> we can make them a bit better.
>
> > I'm interested in working on "Sugarizer Server Dashboard" project for
> > Google Sumer Of Code, 2016 and currently getting server to work after
> > cloning the repository. I have loads of experience in Php, JS, Python and
> > Web Development and have worked on similar project before.
> >
> > I'm facing an issue. I have reached step "Run MongoDB and Sugarizer
> Server"
> > as mentioned here
> > https://github.com/llaske/sugarizer/blob/master/README.md#server but it
> is
> > exiting with error:
> >
> > ```
> > about to fork child process, waiting until server is ready for
> connections.
> > forked process: 28417
> > all output going to: /home/manrajsingh/mongo.log
> > ERROR: child process failed, exited with error number 100
>
> I assume this is from after running the following step?
>
> $ sudo mongod --fork --port 27018 --logpath /home/root/mongo.log
>
> Exit 100 is an unhandled exception in mongo, the database. Can you post
> the log from /home/manrajsingh/mongo.log ?
>
> Also, after you post the logs, would you try this command instead?
>
>$ mkdir ~/mongodb
>$ mongod --dbpath /home/manrajsingh/mongodb --port 27018 --logpath
> /home/manrajsingh/mongo.log
>
> Finally, what distro are you using?
>
>
> --
> Aaron Borden
> Human and Hacker
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction | Interest in Sugarizer Project | Doubts regarding build server setup

[Aaron D Borden]

On Thu, 2016-03-10 at 00:39 -0800, Manraj Singh  
wrote:
> Hello community members,
> 
> I'm Manraj Singh, studying in Netaji Subhas Institute Of Technology(Delhi
> University). I'm an Open Source Enthusiast and have previously contributed
> to jQuery, Mozilla and Privly. I also have prior experience in working for
> startups like Zomato and Refiral and have a good competitve coding profile.

Hello! It's nice to meet you, Manraj! I'm a web developer in San
Francisco of the US. I saw your message in IRC, so you can ping me there
if it's easier for you. I've heard feedback that the server setup
instructions don't always work and they're structured more like you
would for deployment rather than development. Hopefully with your help
we can make them a bit better.

> I'm interested in working on "Sugarizer Server Dashboard" project for
> Google Sumer Of Code, 2016 and currently getting server to work after
> cloning the repository. I have loads of experience in Php, JS, Python and
> Web Development and have worked on similar project before.
> 
> I'm facing an issue. I have reached step "Run MongoDB and Sugarizer Server"
> as mentioned here
> https://github.com/llaske/sugarizer/blob/master/README.md#server but it is
> exiting with error:
> 
> ```
> about to fork child process, waiting until server is ready for connections.
> forked process: 28417
> all output going to: /home/manrajsingh/mongo.log
> ERROR: child process failed, exited with error number 100

I assume this is from after running the following step?

$ sudo mongod --fork --port 27018 --logpath /home/root/mongo.log

Exit 100 is an unhandled exception in mongo, the database. Can you post
the log from /home/manrajsingh/mongo.log ?

Also, after you post the logs, would you try this command instead?

   $ mkdir ~/mongodb
   $ mongod --dbpath /home/manrajsingh/mongodb --port 27018 --logpath 
/home/manrajsingh/mongo.log

Finally, what distro are you using?


--
Aaron Borden
Human and Hacker


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

Re: [Sugar-devel] Introduction

[samson goddy]

Thanks for your interest in Sugar Labs. Here is all you need to become a 
developer, https://developer.sugarlabs.org/.

> Date: Tue, 9 Feb 2016 19:46:14 +0530
> From: adityadiveka...@gmail.com
> To: sugar-devel@lists.sugarlabs.org
> Subject: [Sugar-devel] Introduction
> 
> Hello Developers,
> My name is Aditya Divekar. I am a sophomore from IIT Guwahati.
> I would like to work on Sugar, and have setup the development environment.
> Can anyone help me out by pointing out some beginner bugs?
> Thanks.
> ___
> 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] Introduction

[samson goddy]

Hello Roshan, Welcome to sugarlabs. Here are some links 
http://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki 
https://developer.sugarlabs.org/ also here is our facebook page 
https://www.facebook.com/pages/SugarLabs/. This links will guild you on what to 
do. If you have any question please ask!!

Samson

Date: Wed, 9 Sep 2015 17:48:55 +0530
From: roshanm.r...@gmail.com
To: sugar-devel@lists.sugarlabs.org
Subject: [Sugar-devel] Introduction

Hi, I am Roshan and would like to contribute to Sugar by writing code. I have 
already downloaded the source code and was able to successfully build Sugar OS. 
Could someone please tell me what should be my next step to contribute to 
Sugar.  
Thanking YouYours sincerelyRoshan 
ᐧ

___
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] Introduction

[Gonzalo Odiard]

Hi Roshan,
The best to start, if you already have a development environment and can
run Sugar,
is try to solve some bug in bugs.sugarlabs.org or try do some little
improvement to Sugar
or to the activities.
If you find a bug in bus.sugarlabs.org that you test and is already fixed,
please report, that is a good help.
If you are looking for the repositories of some activity,
this page can be useful:
http://wiki.sugarlabs.org/go/Translation_Team/Pootle_Projects/Repositories

Gonzalo

On Wed, Sep 9, 2015 at 9:18 AM, Roshan M Regy 
wrote:

> Hi, I am Roshan and would like to contribute to Sugar by writing code. I
> have already downloaded the source code and was able to successfully build
> Sugar OS. Could someone please tell me what should be my next step to
> contribute to Sugar.
>
> Thanking You
> Yours sincerely
> Roshan
>
> ᐧ
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


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

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

It seems that the docker service is not running.

Does systemctl start docker gave you an error ?
 Le 12 mai 2015 02:55, Gonzalo Odiard godi...@sugarlabs.org a écrit :

 I have installed docker-io

 As root:
 # dnf install -y docker-io
 # systemctl start docker.service
 # systemctl enable docker.service

 Then, with my user I cloned the repo:
 git clone https://github.com/mikklfr/docker-sugar.git
 cd docker-sugar/
 sh run.sh

 FATA[] Post http:///var/run/docker.sock/v1.18/containers/create: dial
 unix /var/run/docker.sock: no such file or directory. Are you trying to
 connect to a TLS-enabled daemon without TLS?

 Any idea?

 Gonzalo

 On Mon, May 11, 2015 at 6:54 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 Yes, I'll add an option to enable using just a folder, it will be better
 that way.

 I'm running this under ArchLinux.

 The docker-io is the correct package, the another one is something not
 related at all. It's a dock applet systray program : https://fedorahosted
 .org/fpc/ticket/341
 Many distros are getting into this naming problem.

 So, you should remove docker and get docker-io.
 I think that the docker service will start automatically.

 This docker recipe should work across distributions as I didn't used
 specific items.

 I forgot to tell it but docker will only run on amd64 machines.

 The first time you'll run the script, docker will fetch the sugar image
 I've built. It's around 500mb, the source code used is in the Dockerfile
 located inside the github repo.
 It will be cached and the next launches will be almost instant.

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-11 23:44 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:
 
  Maybe point to  directory where you have installed your activities?
  Or take it from a env variable.
 
  A few questions:
  What is your testing environment?
  I am looking at how to install docker in Fedora, and have different
 instructions
  depending on the version https://fedoraproject.org/wiki/Docker
  I am using F21, should I remove docker and install docker-io?
 
  What about other distributions? The docker recipe works across distros
  or we need a different recipe for everyone?
 
  Gonzalo
 
  Gonzalo
 
  On Mon, May 11, 2015 at 6:35 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:
 
  Hi !
 
  I've updated the script.
  You can now start a sugar environment and provide activities folders !
 
  https://github.com/mikklfr/docker-sugar
 
  I've got two activities folders which I want to test : 2048.activity
 and Valorar.activity.
 
  I can run sugar and provide those activities by running the script
 like this :
 
  $sh run.sh 2048.activity Valorar.activity
 
  Sugar shows up and activities are available in the list.
 
  You can edit the scripts from the host, they are synced with the
 docker container.
 
  Maybe you have some specific topics I could look into to get something
 useful for your needs ?
 
  --
  Michaël Ohayon
  Manager de l'Innovation Cloud et Mobilité
  Epitech Innovation Hub
 
  2015-05-11 18:26 GMT+02:00 Michaël Ohayon mohayo...@gmail.com:
 
  Hi,
 
  I've just setup something to run sugar with docker.
 
  It will work on GNU/Linux only with X11 and pulseaudio.
 
  I've published it on the docker registry and github.
 
  - https://github.com/mikklfr/docker-sugar
  - The docker image is mikkl/sugar
 
  It's kind of a poc for now.
  I'll setup a script to test an activity asap.
 
  If you want to test it :
 
  - Download and start docker service
  - Run the .sh script : https://github.com/mikklfr
 /docker-sugar/blob/master/run.sh
 
  I'll give updates :)
 
 
  --
  Michaël Ohayon
  Manager de l'Innovation Cloud et Mobilité
  Epitech Innovation Hub
 
  2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:
 
  Nice.
  And you have a docker recipe to create a sugar development
 environment?
  Can be used in any operating system?
  I am asking because we are thinking in how make easier develop in
 different os,
  and also how distribute Sugar to users in other platforms.
 
  Gonzalo
 
  On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:
 
  Thanks,
 
  Docker is a great tool for booting up a container using LXC, you
 can refer to it as a very light vm focused on a specific task.
  You can script in minutes a way to boot a program by targetting a
 specific OS from any GNU/Linux
 
  For instance here is a Dockerfile to
  - bootup an archlinux container
  - upgrading packages
  - copy a nginx conf file
  - clone sugarizer repository
  - expose nginx to port 80 on the host
 
  [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
  FROM base/archlinux:latest
 
  RUN yes | pacman -Syy
  RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git
 
  COPY nginx.conf /etc/nginx/nginx.conf
 
  RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
  RUN cd /opt/sugarizer/server; npm install
  RUN mkdir /opt/sugarizer/db
 
  EXPOSE 80
 
  CMD 

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Yes, docker should work now :)

--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-05-12 13:37 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:



 On Tue, May 12, 2015 at 3:33 AM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 It seems that the docker service is not running.

 Does systemctl start docker gave you an error ?


 No.

 Searching in Google I found this:

 https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1214104

 Then I tried:

 sudo sh run.sh

 and is downloading.

 Is the right solution?

 Gonzalo


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

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

Nice. Is working now.

This is very interesting. Started ok, and show a nice group of activities

A few comments/questions:

* Every time starts fresh (ask age/gender and select a color). There are
any way to
preserve a state?

* Docker is using the packages installed in Fedora, right? What Fedora
version?
I am trying to understand if we should use this as a distribution option,
as a testing option or if we can use it to develop/test.

* Where is all the stuff downloaded?

* Sugar crashed when I went to My Settings - My computer
(probably was trying to access some devices to get information about the
hardware)

Gonzalo

On Tue, May 12, 2015 at 8:41 AM, Michaël Ohayon mohayo...@gmail.com wrote:

 Yes, docker should work now :)

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-12 13:37 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:



 On Tue, May 12, 2015 at 3:33 AM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 It seems that the docker service is not running.

 Does systemctl start docker gave you an error ?


 No.

 Searching in Google I found this:

 https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1214104

 Then I tried:

 sudo sh run.sh

 and is downloading.

 Is the right solution?

 Gonzalo





-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Great !

- I'll look onto preserving the state for the next versions

- Docker can run any docker container based on any linux.
Your os got his own docker version but you can run everything.
My Dockerfile specifies that the container should use fedora. So the guest
OS is fedora even if I use ArchLinux, Fedora or any other distro as host.

It's a great tool for develop/test. As you can see they are some
limitations for the distribution and some specific testing, like for the
hardware part but it's kinda stable.

The docker images are stored inside /usr/share/docker I think, don't delete
them manually or you'll get into troubles.

*How to remove things :*

Image : base Image of a system (like Fedora)
Container : running instance of an image

You can list images using : docker images -a
You can list containers using : docker ps -a
You can remove all containers using : docker rm `docker ps -aq`
You can remove all images using : docker rmi `docker images -aq`

You must kill and remove containers before images, so *to remove everything*
:
docker kill `docker ps -q`
docker rm `docker ps -aq`
docker rmi `docker images -aq`

The quote ` and not ' or  is important.

I'll setup a wiki page to keep this available !

--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-05-12 14:18 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Nice. Is working now.

 This is very interesting. Started ok, and show a nice group of activities

 A few comments/questions:

 * Every time starts fresh (ask age/gender and select a color). There are
 any way to
 preserve a state?

 * Docker is using the packages installed in Fedora, right? What Fedora
 version?
 I am trying to understand if we should use this as a distribution option,
 as a testing option or if we can use it to develop/test.

 * Where is all the stuff downloaded?

 * Sugar crashed when I went to My Settings - My computer
 (probably was trying to access some devices to get information about the
 hardware)

 Gonzalo

 On Tue, May 12, 2015 at 8:41 AM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 Yes, docker should work now :)

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-12 13:37 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:



 On Tue, May 12, 2015 at 3:33 AM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 It seems that the docker service is not running.

 Does systemctl start docker gave you an error ?


 No.

 Searching in Google I found this:

 https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1214104

 Then I tried:

 sudo sh run.sh

 and is downloading.

 Is the right solution?

 Gonzalo





 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

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

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

 I'll setup a wiki page to keep this available !


Thanks, good idea.

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

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Yes, I'll add an option to enable using just a folder, it will be better
that way.

I'm running this under ArchLinux.

The docker-io is the correct package, the another one is something not
related at all. It's a dock applet systray program : https://fedorahosted
.org/fpc/ticket/341
Many distros are getting into this naming problem.

So, you should remove docker and get docker-io.
I think that the docker service will start automatically.

This docker recipe should work across distributions as I didn't used
specific items.

I forgot to tell it but docker will only run on amd64 machines.

The first time you'll run the script, docker will fetch the sugar image
I've built. It's around 500mb, the source code used is in the Dockerfile
located inside the github repo.
It will be cached and the next launches will be almost instant.

--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-05-11 23:44 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Maybe point to  directory where you have installed your activities?
 Or take it from a env variable.

 A few questions:
 What is your testing environment?
 I am looking at how to install docker in Fedora, and have different
instructions
 depending on the version https://fedoraproject.org/wiki/Docker
 I am using F21, should I remove docker and install docker-io?

 What about other distributions? The docker recipe works across distros
 or we need a different recipe for everyone?

 Gonzalo

 Gonzalo

 On Mon, May 11, 2015 at 6:35 PM, Michaël Ohayon mohayo...@gmail.com
wrote:

 Hi !

 I've updated the script.
 You can now start a sugar environment and provide activities folders !

 https://github.com/mikklfr/docker-sugar

 I've got two activities folders which I want to test : 2048.activity and
Valorar.activity.

 I can run sugar and provide those activities by running the script like
this :

 $sh run.sh 2048.activity Valorar.activity

 Sugar shows up and activities are available in the list.

 You can edit the scripts from the host, they are synced with the docker
container.

 Maybe you have some specific topics I could look into to get something
useful for your needs ?

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-11 18:26 GMT+02:00 Michaël Ohayon mohayo...@gmail.com:

 Hi,

 I've just setup something to run sugar with docker.

 It will work on GNU/Linux only with X11 and pulseaudio.

 I've published it on the docker registry and github.

 - https://github.com/mikklfr/docker-sugar
 - The docker image is mikkl/sugar

 It's kind of a poc for now.
 I'll setup a script to test an activity asap.

 If you want to test it :

 - Download and start docker service
 - Run the .sh script : https://github.com/mikklfr
/docker-sugar/blob/master/run.sh

 I'll give updates :)


 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Nice.
 And you have a docker recipe to create a sugar development environment?
 Can be used in any operating system?
 I am asking because we are thinking in how make easier develop in
different os,
 and also how distribute Sugar to users in other platforms.

 Gonzalo

 On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
wrote:

 Thanks,

 Docker is a great tool for booting up a container using LXC, you can
refer to it as a very light vm focused on a specific task.
 You can script in minutes a way to boot a program by targetting a
specific OS from any GNU/Linux

 For instance here is a Dockerfile to
 - bootup an archlinux container
 - upgrading packages
 - copy a nginx conf file
 - clone sugarizer repository
 - expose nginx to port 80 on the host

 [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
 FROM base/archlinux:latest

 RUN yes | pacman -Syy
 RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

 COPY nginx.conf /etc/nginx/nginx.conf

 RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
 RUN cd /opt/sugarizer/server; npm install
 RUN mkdir /opt/sugarizer/db

 EXPOSE 80

 CMD [/usr/bin/nginx]
 [ohayon_m@ohayon-m-thinkpad /tmp]$

 Each modification of a container is handled like a git commit so you
can rollback at any time and launch specific snapshots.
 It has a cache system. It will bootup almost instantly after the
container is build.

 I see it like a great tool to setup an env without having to script
install for every OS or if you don't want to install every
lib/framework/etc in your OS just for some testing.
 It can be used in production and manage/scale with the new tools :
Docker Swarm and Docker Compose

 Hope you'll find it usefull !



 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
Sugarizer and Sugar containers (with 

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Hi !

I've updated the script.
You can now start a sugar environment and provide activities folders !

https://github.com/mikklfr/docker-sugar

I've got two activities folders which I want to test : 2048.activity and
Valorar.activity.

I can run sugar and provide those activities by running the script like
this :

$sh run.sh 2048.activity Valorar.activity

Sugar shows up and activities are available in the list.

You can edit the scripts from the host, they are synced with the docker
container.

Maybe you have some specific topics I could look into to get something
useful for your needs ?

--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-05-11 18:26 GMT+02:00 Michaël Ohayon mohayo...@gmail.com:

 Hi,

 I've just setup something to run sugar with docker.

 It will work on GNU/Linux only with X11 and pulseaudio.

 I've published it on the docker registry and github.

 - https://github.com/mikklfr/docker-sugar
 - The docker image is mikkl/sugar

 It's kind of a poc for now.
 I'll setup a script to test an activity asap.

 If you want to test it :

 - Download and start docker service
 - Run the .sh script :
 https://github.com/mikklfr/docker-sugar/blob/master/run.sh

 I'll give updates :)


 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Nice.
 And you have a docker recipe to create a sugar development environment?
 Can be used in any operating system?
 I am asking because we are thinking in how make easier develop in
 different os,
 and also how distribute Sugar to users in other platforms.

 Gonzalo

 On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 Thanks,

 Docker is a great tool for booting up a container using LXC, you can
 refer to it as a very light vm focused on a specific task.
 You can script in minutes a way to boot a program by targetting a
 specific OS from any GNU/Linux

 For instance here is a Dockerfile to
 - bootup an archlinux container
 - upgrading packages
 - copy a nginx conf file
 - clone sugarizer repository
 - expose nginx to port 80 on the host

 [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
 FROM base/archlinux:latest

 RUN yes | pacman -Syy
 RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

 COPY nginx.conf /etc/nginx/nginx.conf

 RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
 RUN cd /opt/sugarizer/server; npm install
 RUN mkdir /opt/sugarizer/db

 EXPOSE 80

 CMD [/usr/bin/nginx]
 [ohayon_m@ohayon-m-thinkpad /tmp]$

 Each modification of a container is handled like a git commit so you can
 rollback at any time and launch specific snapshots.
 It has a cache system. It will bootup almost instantly after the
 container is build.

 I see it like a great tool to setup an env without having to script
 install for every OS or if you don't want to install every
 lib/framework/etc in your OS just for some testing.
 It can be used in production and manage/scale with the new tools :
 Docker Swarm and Docker Compose

 Hope you'll find it usefull !



 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar one).


 Interesting. I don't know more from Docker than the sporadic news,
 could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of
 some essential apps for the web version of Sugar.


 Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


 Great. Keep connected :)

 Gonzalo





 --
 Gonzalo Odiard

 SugarLabs - Software for children learning



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

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

I have installed docker-io

As root:
# dnf install -y docker-io
# systemctl start docker.service
# systemctl enable docker.service

Then, with my user I cloned the repo:
git clone https://github.com/mikklfr/docker-sugar.git
cd docker-sugar/
sh run.sh

FATA[] Post http:///var/run/docker.sock/v1.18/containers/create: dial
unix /var/run/docker.sock: no such file or directory. Are you trying to
connect to a TLS-enabled daemon without TLS?

Any idea?

Gonzalo

On Mon, May 11, 2015 at 6:54 PM, Michaël Ohayon mohayo...@gmail.com wrote:

 Yes, I'll add an option to enable using just a folder, it will be better
 that way.

 I'm running this under ArchLinux.

 The docker-io is the correct package, the another one is something not
 related at all. It's a dock applet systray program : https://fedorahosted
 .org/fpc/ticket/341
 Many distros are getting into this naming problem.

 So, you should remove docker and get docker-io.
 I think that the docker service will start automatically.

 This docker recipe should work across distributions as I didn't used
 specific items.

 I forgot to tell it but docker will only run on amd64 machines.

 The first time you'll run the script, docker will fetch the sugar image
 I've built. It's around 500mb, the source code used is in the Dockerfile
 located inside the github repo.
 It will be cached and the next launches will be almost instant.

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-11 23:44 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:
 
  Maybe point to  directory where you have installed your activities?
  Or take it from a env variable.
 
  A few questions:
  What is your testing environment?
  I am looking at how to install docker in Fedora, and have different
 instructions
  depending on the version https://fedoraproject.org/wiki/Docker
  I am using F21, should I remove docker and install docker-io?
 
  What about other distributions? The docker recipe works across distros
  or we need a different recipe for everyone?
 
  Gonzalo
 
  Gonzalo
 
  On Mon, May 11, 2015 at 6:35 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:
 
  Hi !
 
  I've updated the script.
  You can now start a sugar environment and provide activities folders !
 
  https://github.com/mikklfr/docker-sugar
 
  I've got two activities folders which I want to test : 2048.activity
 and Valorar.activity.
 
  I can run sugar and provide those activities by running the script like
 this :
 
  $sh run.sh 2048.activity Valorar.activity
 
  Sugar shows up and activities are available in the list.
 
  You can edit the scripts from the host, they are synced with the docker
 container.
 
  Maybe you have some specific topics I could look into to get something
 useful for your needs ?
 
  --
  Michaël Ohayon
  Manager de l'Innovation Cloud et Mobilité
  Epitech Innovation Hub
 
  2015-05-11 18:26 GMT+02:00 Michaël Ohayon mohayo...@gmail.com:
 
  Hi,
 
  I've just setup something to run sugar with docker.
 
  It will work on GNU/Linux only with X11 and pulseaudio.
 
  I've published it on the docker registry and github.
 
  - https://github.com/mikklfr/docker-sugar
  - The docker image is mikkl/sugar
 
  It's kind of a poc for now.
  I'll setup a script to test an activity asap.
 
  If you want to test it :
 
  - Download and start docker service
  - Run the .sh script : https://github.com/mikklfr
 /docker-sugar/blob/master/run.sh
 
  I'll give updates :)
 
 
  --
  Michaël Ohayon
  Manager de l'Innovation Cloud et Mobilité
  Epitech Innovation Hub
 
  2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:
 
  Nice.
  And you have a docker recipe to create a sugar development
 environment?
  Can be used in any operating system?
  I am asking because we are thinking in how make easier develop in
 different os,
  and also how distribute Sugar to users in other platforms.
 
  Gonzalo
 
  On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:
 
  Thanks,
 
  Docker is a great tool for booting up a container using LXC, you
 can refer to it as a very light vm focused on a specific task.
  You can script in minutes a way to boot a program by targetting a
 specific OS from any GNU/Linux
 
  For instance here is a Dockerfile to
  - bootup an archlinux container
  - upgrading packages
  - copy a nginx conf file
  - clone sugarizer repository
  - expose nginx to port 80 on the host
 
  [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
  FROM base/archlinux:latest
 
  RUN yes | pacman -Syy
  RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git
 
  COPY nginx.conf /etc/nginx/nginx.conf
 
  RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
  RUN cd /opt/sugarizer/server; npm install
  RUN mkdir /opt/sugarizer/db
 
  EXPOSE 80
 
  CMD [/usr/bin/nginx]
  [ohayon_m@ohayon-m-thinkpad /tmp]$
 
  Each modification of a container is handled like a git commit so you
 can rollback at any time and launch specific snapshots.
  

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

Maybe point to  directory where you have installed your activities?
Or take it from a env variable.

A few questions:
What is your testing environment?
I am looking at how to install docker in Fedora, and have different
instructions
depending on the version https://fedoraproject.org/wiki/Docker
I am using F21, should I remove docker and install docker-io?

What about other distributions? The docker recipe works across distros
or we need a different recipe for everyone?

Gonzalo

Gonzalo

On Mon, May 11, 2015 at 6:35 PM, Michaël Ohayon mohayo...@gmail.com wrote:

 Hi !

 I've updated the script.
 You can now start a sugar environment and provide activities folders !

 https://github.com/mikklfr/docker-sugar

 I've got two activities folders which I want to test : 2048.activity and
 Valorar.activity.

 I can run sugar and provide those activities by running the script like
 this :

 $sh run.sh 2048.activity Valorar.activity

 Sugar shows up and activities are available in the list.

 You can edit the scripts from the host, they are synced with the docker
 container.

 Maybe you have some specific topics I could look into to get something
 useful for your needs ?

 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-11 18:26 GMT+02:00 Michaël Ohayon mohayo...@gmail.com:

 Hi,

 I've just setup something to run sugar with docker.

 It will work on GNU/Linux only with X11 and pulseaudio.

 I've published it on the docker registry and github.

 - https://github.com/mikklfr/docker-sugar
 - The docker image is mikkl/sugar

 It's kind of a poc for now.
 I'll setup a script to test an activity asap.

 If you want to test it :

 - Download and start docker service
 - Run the .sh script :
 https://github.com/mikklfr/docker-sugar/blob/master/run.sh

 I'll give updates :)


 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Nice.
 And you have a docker recipe to create a sugar development environment?
 Can be used in any operating system?
 I am asking because we are thinking in how make easier develop in
 different os,
 and also how distribute Sugar to users in other platforms.

 Gonzalo

 On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 Thanks,

 Docker is a great tool for booting up a container using LXC, you can
 refer to it as a very light vm focused on a specific task.
 You can script in minutes a way to boot a program by targetting a
 specific OS from any GNU/Linux

 For instance here is a Dockerfile to
 - bootup an archlinux container
 - upgrading packages
 - copy a nginx conf file
 - clone sugarizer repository
 - expose nginx to port 80 on the host

 [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
 FROM base/archlinux:latest

 RUN yes | pacman -Syy
 RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

 COPY nginx.conf /etc/nginx/nginx.conf

 RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
 RUN cd /opt/sugarizer/server; npm install
 RUN mkdir /opt/sugarizer/db

 EXPOSE 80

 CMD [/usr/bin/nginx]
 [ohayon_m@ohayon-m-thinkpad /tmp]$

 Each modification of a container is handled like a git commit so you
 can rollback at any time and launch specific snapshots.
 It has a cache system. It will bootup almost instantly after the
 container is build.

 I see it like a great tool to setup an env without having to script
 install for every OS or if you don't want to install every
 lib/framework/etc in your OS just for some testing.
 It can be used in production and manage/scale with the new tools :
 Docker Swarm and Docker Compose

 Hope you'll find it usefull !



 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar 
 one).


 Interesting. I don't know more from Docker than the sporadic news,
 could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of
 some essential apps for the web version of Sugar.


 Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


 Great. Keep connected :)

 Gonzalo





 --
 Gonzalo Odiard

 SugarLabs - Software for children learning






-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Hi,

I've just setup something to run sugar with docker.

It will work on GNU/Linux only with X11 and pulseaudio.

I've published it on the docker registry and github.

- https://github.com/mikklfr/docker-sugar
- The docker image is mikkl/sugar

It's kind of a poc for now.
I'll setup a script to test an activity asap.

If you want to test it :

- Download and start docker service
- Run the .sh script :
https://github.com/mikklfr/docker-sugar/blob/master/run.sh

I'll give updates :)


--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-05-03 6:17 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Nice.
 And you have a docker recipe to create a sugar development environment?
 Can be used in any operating system?
 I am asking because we are thinking in how make easier develop in
 different os,
 and also how distribute Sugar to users in other platforms.

 Gonzalo

 On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com
 wrote:

 Thanks,

 Docker is a great tool for booting up a container using LXC, you can
 refer to it as a very light vm focused on a specific task.
 You can script in minutes a way to boot a program by targetting a
 specific OS from any GNU/Linux

 For instance here is a Dockerfile to
 - bootup an archlinux container
 - upgrading packages
 - copy a nginx conf file
 - clone sugarizer repository
 - expose nginx to port 80 on the host

 [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
 FROM base/archlinux:latest

 RUN yes | pacman -Syy
 RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

 COPY nginx.conf /etc/nginx/nginx.conf

 RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
 RUN cd /opt/sugarizer/server; npm install
 RUN mkdir /opt/sugarizer/db

 EXPOSE 80

 CMD [/usr/bin/nginx]
 [ohayon_m@ohayon-m-thinkpad /tmp]$

 Each modification of a container is handled like a git commit so you can
 rollback at any time and launch specific snapshots.
 It has a cache system. It will bootup almost instantly after the
 container is build.

 I see it like a great tool to setup an env without having to script
 install for every OS or if you don't want to install every
 lib/framework/etc in your OS just for some testing.
 It can be used in production and manage/scale with the new tools : Docker
 Swarm and Docker Compose

 Hope you'll find it usefull !



 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar one).


 Interesting. I don't know more from Docker than the sporadic news,
 could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of
 some essential apps for the web version of Sugar.


 Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


 Great. Keep connected :)

 Gonzalo





 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

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

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

Nice.
And you have a docker recipe to create a sugar development environment?
Can be used in any operating system?
I am asking because we are thinking in how make easier develop in different
os,
and also how distribute Sugar to users in other platforms.

Gonzalo

On Fri, May 1, 2015 at 1:23 PM, Michaël Ohayon mohayo...@gmail.com wrote:

 Thanks,

 Docker is a great tool for booting up a container using LXC, you can refer
 to it as a very light vm focused on a specific task.
 You can script in minutes a way to boot a program by targetting a specific
 OS from any GNU/Linux

 For instance here is a Dockerfile to
 - bootup an archlinux container
 - upgrading packages
 - copy a nginx conf file
 - clone sugarizer repository
 - expose nginx to port 80 on the host

 [ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
 FROM base/archlinux:latest

 RUN yes | pacman -Syy
 RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

 COPY nginx.conf /etc/nginx/nginx.conf

 RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
 RUN cd /opt/sugarizer/server; npm install
 RUN mkdir /opt/sugarizer/db

 EXPOSE 80

 CMD [/usr/bin/nginx]
 [ohayon_m@ohayon-m-thinkpad /tmp]$

 Each modification of a container is handled like a git commit so you can
 rollback at any time and launch specific snapshots.
 It has a cache system. It will bootup almost instantly after the
 container is build.

 I see it like a great tool to setup an env without having to script
 install for every OS or if you don't want to install every
 lib/framework/etc in your OS just for some testing.
 It can be used in production and manage/scale with the new tools : Docker
 Swarm and Docker Compose

 Hope you'll find it usefull !



 --
 Michaël Ohayon
 Manager de l'Innovation Cloud et Mobilité
 Epitech Innovation Hub

 2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar one).


 Interesting. I don't know more from Docker than the sporadic news,
 could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of
 some essential apps for the web version of Sugar.


 Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


 Great. Keep connected :)

 Gonzalo





-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction to the list

[Michaël Ohayon]

Thanks,

Docker is a great tool for booting up a container using LXC, you can refer
to it as a very light vm focused on a specific task.
You can script in minutes a way to boot a program by targetting a specific
OS from any GNU/Linux

For instance here is a Dockerfile to
- bootup an archlinux container
- upgrading packages
- copy a nginx conf file
- clone sugarizer repository
- expose nginx to port 80 on the host

[ohayon_m@ohayon-m-thinkpad /tmp]$ cat Dockerfile
FROM base/archlinux:latest

RUN yes | pacman -Syy
RUN yes | pacman -S gcc nodejs openssh mongodb supervisor nginx git

COPY nginx.conf /etc/nginx/nginx.conf

RUN cd /opt; git clone https://github.com/llaske/sugarizer.git
RUN cd /opt/sugarizer/server; npm install
RUN mkdir /opt/sugarizer/db

EXPOSE 80

CMD [/usr/bin/nginx]
[ohayon_m@ohayon-m-thinkpad /tmp]$

Each modification of a container is handled like a git commit so you can
rollback at any time and launch specific snapshots.
It has a cache system. It will bootup almost instantly after the
container is build.

I see it like a great tool to setup an env without having to script install
for every OS or if you don't want to install every lib/framework/etc in
your OS just for some testing.
It can be used in production and manage/scale with the new tools : Docker
Swarm and Docker Compose

Hope you'll find it usefull !



--
Michaël Ohayon
Manager de l'Innovation Cloud et Mobilité
Epitech Innovation Hub

2015-04-30 21:00 GMT+02:00 Gonzalo Odiard godi...@sugarlabs.org:

 Hi Michaël,
 Welcome!

 Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar one).


 Interesting. I don't know more from Docker than the sporadic news,
 could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of some
 essential apps for the web version of Sugar.


 Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


 Great. Keep connected :)

 Gonzalo

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

Re: [Sugar-devel] Introduction to the list

[Gonzalo Odiard]

Hi Michaël,
Welcome!

Few months later, I joined the Docker Paris Hackathon and had built
 Sugarizer and Sugar containers (with graphical support for the Sugar one).


Interesting. I don't know more from Docker than the sporadic news,
could explain what can be done with the Sugar container?


 My proposal is the SugarWeb Basic ActivitySet which is a writting of some
 essential apps for the web version of Sugar.


Here's the link to my GSOC proposal :
 http://wiki.sugarlabs.org/go/Summer_of_Code/2015/mohayon.SugarWebBasicActivitySet


Great. Keep connected :)

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

Re: [Sugar-devel] Introduction.

[Chris Leonard]

On Tue, Nov 1, 2011 at 8:34 AM, Iain Brown Douglas 
i...@browndouglas.plus.com wrote:

 Greetings,
 I have dipped into Sugar a number of times in the past. I have a
 personal interest in introducing creative and productive use of a
 computer to a new generation ages 3 and 9.
 I should declare a prejudice against global organisations which produce
 unhealthy drinks, high saturated fat products, search engines, and
 operating systems.
 http://wiki-devel.sugarlabs.org/go/User:Inkyfingers


Well, in that case, please note that Sugar is a metaphorical name and our
product does not contain high-fructose corn syrup.  :-)

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

Re: [Sugar-devel] Introduction

[Sascha Silbe]

Excerpts from James Simmons's message of Sat Jan 29 16:22:49 +0100 2011:

 The book Make Your Own Sugar Activities! has some suggestions on
 development environments and many other topics:
 
 http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction

[...]

In the What About Using sugar-jhbuild? section you write:

 When you're done you'll have an up to date test environment that you
 can run as an alternative to sugar-emulator.

sugar-jhbuild is an alternative to installing Sugar from distro
packages, nothing more or less.

In order to run Sugar inside an already-running desktop system (very
similar to running Linux inside a VM, just at the desktop system level
instead of at the operating system level) you can use sugar-emulator, no
matter how you installed it (distro packages or sugar-jhbuild).

Similarly, you can run Sugar in native mode no matter whether you got
it from distro packages or using sugar-jhbuild.

It would be nice if you could clarify this in your book, because this
misunderstanding has been a major source of confusion in the past (and
probably still is in the present).

Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/


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

Re: [Sugar-devel] Introduction

[Sascha Silbe]

Excerpts from Gary Martin's message of Sat Jan 29 16:09:43 +0100 2011:

  I don't have an XO laptops but I do have a VirtualBox Fedora and Ubuntu VMs 
  running sugarlabs. What do you use as a Python editor- I was hoping to use 
  eclipse but I have used a basic introduction to VIM in my classes so it can 
  be anything. I played around in the SugarLabs Pippy editor but I was hoping 
  that I could write another machine and import.
 
 The first things I usually yum install to a new Sugar image are vim and git, 
 that way I can git clone an Activity repository into the ~/Activities 
 directory, tinker with it using vim, and easily git commit and git push 
 changes back to the main repository after testing. If I'm going to be making 
 large source changes or starting something new I'll often just work on my Mac 
 using Xcode (my source editor of choice) and scp the Activity directory over 
 to various Sugar builds for testing.

FWIW, I'm increasingly using sshfs to hack on code that's inside a VM.
sshfs allows you to mount a remote file system that's accessible via
ssh/sftp and access it as if it were a local file system. That way you
can use all the editing / VCS / whatever tools you're used to, without
having to install them inside the VM. Because the tools are running on
your real machine, they work as usual - including things like
copypaste across applications (which requires special guest additions
in VirtualBox and doesn't work at all in KVM).

IIRC I've successfully used a special port of sshfs on MacOS X some time
ago. There are also tools for Windows that seem to provide something
similar, but I haven't tried them myself.

Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/


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

Re: [Sugar-devel] Introduction

[Sascha Silbe]

Excerpts from Mike Rehner's message of Fri Jan 28 19:56:12 +0100 2011:

 I am a retired high school computer science teacher from Columbus, Ohio,
 USA. My background includes both computer science and instructional design.
 I would like to volunteer 8-12 hours a week to work with the Activity Team.

Welcome! We can always use some help.

Others have already replied pointing out ways to contribute, so I guess
you already have enough to read up on to keep you busy for a while
before you decide on what you'd like to do. Let me just mention that
you're quite welcome to ask questions both on this list and our IRC
channel, #sugar on FreeNode [1]. Please don't give up if you're not
getting a reply instantly. Most of us have their IRC client running
all day (because it's our way to collaborate across physical borders),
but only check it occasionally (e.g. while we're waiting for a package
to finish building).

If you don't mind everything you write being preserved for eternity [2],
you can also use the #sugar-newbies channel. (The mailing list is
archived, too [3]).

Sascha

[1] http://wiki.sugarlabs.org/go/Internet_Relay_Chat#irc.freenode.net_channels
[2] http://jita.sugarlabs.org/freenode/%23sugar-newbies/index.html
[3] http://lists.sugarlabs.org/archive/sugar-devel/
-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/


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

Re: [Sugar-devel] Introduction

[James Simmons]

Sascha,

What I was trying to get across is that while the distro packages are
what most people should be using, they aren't up to the minute.  By
installing sugar-jhbuild you can test both the latest Sugar and an
older version that is more likely to be used in the field on the same
box without the two environments interfering with each other.  That's
not the easiest point to get across.  I also say that most developers
should not use sugar-jhbuild, at least not to begin with.

I'll look at it again when I have a chance.

James Simmons


On Sun, Jan 30, 2011 at 5:57 AM, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from James Simmons's message of Sat Jan 29 16:22:49 +0100 2011:

 The book Make Your Own Sugar Activities! has some suggestions on
 development environments and many other topics:

 http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction

 [...]

 In the What About Using sugar-jhbuild? section you write:

 When you're done you'll have an up to date test environment that you
 can run as an alternative to sugar-emulator.

 sugar-jhbuild is an alternative to installing Sugar from distro
 packages, nothing more or less.

 In order to run Sugar inside an already-running desktop system (very
 similar to running Linux inside a VM, just at the desktop system level
 instead of at the operating system level) you can use sugar-emulator, no
 matter how you installed it (distro packages or sugar-jhbuild).

 Similarly, you can run Sugar in native mode no matter whether you got
 it from distro packages or using sugar-jhbuild.

 It would be nice if you could clarify this in your book, because this
 misunderstanding has been a major source of confusion in the past (and
 probably still is in the present).

 Sascha

 --
 http://sascha.silbe.org/
 http://www.infra-silbe.de/

 ___
 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] Introduction

[Gary Martin]

Hi Sascha,

On 30 Jan 2011, at 12:10, Sascha Silbe sascha-ml-reply-to-201...@silbe.org 
wrote:

 Excerpts from Gary Martin's message of Sat Jan 29 16:09:43 +0100 2011:
 
 I don't have an XO laptops but I do have a VirtualBox Fedora and Ubuntu VMs 
 running sugarlabs. What do you use as a Python editor- I was hoping to use 
 eclipse but I have used a basic introduction to VIM in my classes so it can 
 be anything. I played around in the SugarLabs Pippy editor but I was hoping 
 that I could write another machine and import.
 
 The first things I usually yum install to a new Sugar image are vim and git, 
 that way I can git clone an Activity repository into the ~/Activities 
 directory, tinker with it using vim, and easily git commit and git push 
 changes back to the main repository after testing. If I'm going to be making 
 large source changes or starting something new I'll often just work on my 
 Mac using Xcode (my source editor of choice) and scp the Activity directory 
 over to various Sugar builds for testing.
 
 FWIW, I'm increasingly using sshfs to hack on code that's inside a VM.
 sshfs allows you to mount a remote file system that's accessible via
 ssh/sftp and access it as if it were a local file system.

Thanks for the hint! Sounds like a nice improvement to my usual work flow :-) 
I'll make sure to give it a run through.

Regards,
--Gary

 That way you
 can use all the editing / VCS / whatever tools you're used to, without
 having to install them inside the VM. Because the tools are running on
 your real machine, they work as usual - including things like
 copypaste across applications (which requires special guest additions
 in VirtualBox and doesn't work at all in KVM).
 
 IIRC I've successfully used a special port of sshfs on MacOS X some time
 ago. There are also tools for Windows that seem to provide something
 similar, but I haven't tried them myself.
 
 Sascha
 
 -- 
 http://sascha.silbe.org/
 http://www.infra-silbe.de/
 ___
 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] Introduction

[James Simmons]

Mike,

The book Make Your Own Sugar Activities! has some suggestions on
development environments and many other topics:

http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction

I have use Eclipse with the Python plugin for developing Activities
myself, and like it.  Usually I use Eric.

James Simmons


On Sat, Jan 29, 2011 at 9:09 AM, Gary Martin garycmar...@googlemail.com wrote:
 Hi Mike,

 On 28 Jan 2011, at 20:28, Mike Rehner babareh...@gmail.com wrote:

 Gary,

 I don't have an XO laptops but I do have a VirtualBox Fedora and Ubuntu VMs 
 running sugarlabs. What do you use as a Python editor- I was hoping to use 
 eclipse but I have used a basic introduction to VIM in my classes so it can 
 be anything. I played around in the SugarLabs Pippy editor but I was hoping 
 that I could write another machine and import.

 The first things I usually yum install to a new Sugar image are vim and git, 
 that way I can git clone an Activity repository into the ~/Activities 
 directory, tinker with it using vim, and easily git commit and git push 
 changes back to the main repository after testing. If I'm going to be making 
 large source changes or starting something new I'll often just work on my Mac 
 using Xcode (my source editor of choice) and scp the Activity directory over 
 to various Sugar builds for testing.

 Regards,
 --Gary
 ___
 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] Introduction

[Walter Bender]

On Fri, Jan 28, 2011 at 6:56 PM, Mike Rehner babareh...@gmail.com wrote:
 Hello

 I am a retired high school computer science teacher from Columbus, Ohio,
 USA. My background includes both computer science and instructional design.
 I would like to volunteer 8-12 hours a week to work with the Activity Team.
 I am looking to start something very small while I slowly set up my dev
 environment and become familiar with Sugar Labs.

Welcome to Sugar.

Are you interested in developing new activities? helping us develop
improved ways to use existing activities in the classroom? both?
something else altogether?

regards.

-walter


 cheers,

 Mike Rehner

 ___
 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] Introduction

[Gary Martin]

Hi Mike,

On 28 Jan 2011, at 18:56, Mike Rehner babareh...@gmail.com wrote:

 I am a retired high school computer science teacher from Columbus, Ohio, USA. 
 My background includes both computer science and instructional design. I 
 would like to volunteer 8-12 hours a week to work with the Activity Team. I 
 am looking to start something very small while I slowly set up my dev 
 environment and become familiar with Sugar Labs. 

Just wanted to say welcome!

Fab, I see you've already found the Activity Team pages on the wiki, that 
should lead you to the resources to get you up and running. Once you have your 
dev environment running comfortably (I use a mix of XO-1 laptops and my Mac 
laptop running a VirtualBox VM of Fedora with Sugar installed as its desktop) 
one way to help contribute could be to adopt an un-maintained Activity. This 
usually involves:

- getting familiar with Python, and some GTK+
- learning enough git to get you by using the repositories at 
http://git.sugarlabs.org 
- keeping an eye on tickets filed at http://bugs.sugarlabs.org for your adopted 
Activity
- releasing .xo bundles from time to time at http://activities.sugarlabs.org
- uploading the source to http://download.sugarlabs.org so distro packagers 
have easy access

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

Re: [Sugar-devel] Introduction

[Rafael Ortiz]

Hi Mike

On Fri, Jan 28, 2011 at 2:57 PM, Gary Martin garycmar...@googlemail.comwrote:

 Hi Mike,

 On 28 Jan 2011, at 18:56, Mike Rehner babareh...@gmail.com wrote:

  I am a retired high school computer science teacher from Columbus, Ohio,
 USA. My background includes both computer science and instructional design.
 I would like to volunteer 8-12 hours a week to work with the Activity Team.
 I am looking to start something very small while I slowly set up my dev
 environment and become familiar with Sugar Labs.


Welcome aboard!.

As Gary says one of the best ways to help is adopting an activity.

All the pages inside Category Activity Team are useful.


 http://wiki.sugarlabs.org/go/Category:Activity_Team

Cheers

 Just wanted to say welcome!

 Fab, I see you've already found the Activity Team pages on the wiki, that
 should lead you to the resources to get you up and running. Once you have
 your dev environment running comfortably (I use a mix of XO-1 laptops and my
 Mac laptop running a VirtualBox VM of Fedora with Sugar installed as its
 desktop) one way to help contribute could be to adopt an un-maintained
 Activity. This usually involves:

 - getting familiar with Python, and some GTK+
 - learning enough git to get you by using the repositories at
 http://git.sugarlabs.org
 - keeping an eye on tickets filed at http://bugs.sugarlabs.org for your
 adopted Activity
 - releasing .xo bundles from time to time at
 http://activities.sugarlabs.org
 - uploading the source to http://download.sugarlabs.org so distro
 packagers have easy access

 Regards,
 --Gary
 ___
 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] Introduction

[Tomeu Vizoso]

On Tue, Sep 28, 2010 at 12:46, Steven Parrish smparr...@gmail.com wrote:
 Some of you may have already heard that I have accepted a position
 with ActivityCentral to be the project manager for Dextrose.  It feels
 like I have come full circle as I started out as a volunteer
 maintaining the F11 for the XO-1 builds for the past 18 months.
 That work was very rewarding and I was glad to see OLPC step in and
 release official builds based on my work.  The F11 for the XO-1 was
 also a starting point for the original Dextrose system, which Bernie
 Innocenti brought to fruition.

 Now we will be taking the original Dextrose and expanding upon it.
 Dextrose2 will be the result.  Based on Fedora11 and Sugar 0.88 it
 will strive for stability, while providing deployments with a
 customizable product.  I have already started creating builds for the
 new system with additional language support, and they can be found at
 http://wiki.sugarlabs.org/go/Dextrose .  The builds will be for both
 the XO-1 and XO-1.5 and will be available both with Gnome and without.

 We have a team of developers at SEETA who will be working on this with
 us.  Many of them are already known to the community and more will
 become known as they join the effort.

 I have already started going over the outstanding issues and know that
 with everyone's help we can make Dextrose the Premier system for XO
 deployments.

 The issues that need to be worked on can be found at:

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=$love

 and

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonekeywords=$extrose

 If you are already working on any of these tickets please send me a
 quick note as to which tickets you are working on and what the status
 is.

 I look forward to working with everyone.

I'm very happy to read this, look forward to work further with you.

It would be very helpful if any new contributors could take the time
to present themselves and their plans as you have done.

Regards,

Tomeu

 Steven Parrish
 smparr...@gmail.com
 ___
 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] Introduction

[Aleksey Lim]

On Tue, Sep 28, 2010 at 06:46:00AM -0400, Steven Parrish wrote:
 Some of you may have already heard that I have accepted a position
 with ActivityCentral to be the project manager for Dextrose.

Great to hear!

 It feels
 like I have come full circle as I started out as a volunteer
 maintaining the F11 for the XO-1 builds for the past 18 months.
 That work was very rewarding and I was glad to see OLPC step in and
 release official builds based on my work.  The F11 for the XO-1 was
 also a starting point for the original Dextrose system, which Bernie
 Innocenti brought to fruition.
 
 Now we will be taking the original Dextrose and expanding upon it.
 Dextrose2 will be the result.  Based on Fedora11 and Sugar 0.88 it
 will strive for stability, while providing deployments with a
 customizable product.  I have already started creating builds for the
 new system with additional language support, and they can be found at
 http://wiki.sugarlabs.org/go/Dextrose .  The builds will be for both
 the XO-1 and XO-1.5 and will be available both with Gnome and without.

What about reusing bazaar.sl.o as Dextrose repository for all sugar
packages (it could be only sugar, other packages like hw maybe reused
directly from upstream, attached after bazaar repo or even build on
bazaar)?

I'm planing to have 0.88 Sugar Platform run on f11 at the end of this
week.

The benefits I see here is that we can reuse Dextrose efforts(regarding
to sugar itself) in other sugar distros directly (just building for
particular distro). Also, we can have the same repo of activities on
bazaar (w/o repacking it for several distros).

 We have a team of developers at SEETA who will be working on this with
 us.  Many of them are already known to the community and more will
 become known as they join the effort.
 
 I have already started going over the outstanding issues and know that
 with everyone's help we can make Dextrose the Premier system for XO
 deployments.
 
 The issues that need to be worked on can be found at:
 
 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=$love
 
 and
 
 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonekeywords=$extrose
 
 If you are already working on any of these tickets please send me a
 quick note as to which tickets you are working on and what the status
 is.
 
 I look forward to working with everyone.
 
 Steven Parrish
 smparr...@gmail.com
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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

Re: [Sugar-devel] Introduction

[Simon Schampijer]

Hi Steven,

On 09/28/2010 01:00 PM, Tomeu Vizoso wrote:
 On Tue, Sep 28, 2010 at 12:46, Steven Parrishsmparr...@gmail.com  wrote:
 Some of you may have already heard that I have accepted a position
 with ActivityCentral to be the project manager for Dextrose.  It feels
 like I have come full circle as I started out as a volunteer
 maintaining the F11 for the XO-1 builds for the past 18 months.
 That work was very rewarding and I was glad to see OLPC step in and
 release official builds based on my work.  The F11 for the XO-1 was
 also a starting point for the original Dextrose system, which Bernie
 Innocenti brought to fruition.

 Now we will be taking the original Dextrose and expanding upon it.
 Dextrose2 will be the result.  Based on Fedora11 and Sugar 0.88 it
 will strive for stability, while providing deployments with a
 customizable product.  I have already started creating builds for the
 new system with additional language support, and they can be found at
 http://wiki.sugarlabs.org/go/Dextrose .  The builds will be for both
 the XO-1 and XO-1.5 and will be available both with Gnome and without.

 We have a team of developers at SEETA who will be working on this with
 us.  Many of them are already known to the community and more will
 become known as they join the effort.

 I have already started going over the outstanding issues and know that
 with everyone's help we can make Dextrose the Premier system for XO
 deployments.

 The issues that need to be worked on can be found at:

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=$love

 and

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonekeywords=$extrose

 If you are already working on any of these tickets please send me a
 quick note as to which tickets you are working on and what the status
 is.

 I look forward to working with everyone.

 I'm very happy to read this, look forward to work further with you.

 It would be very helpful if any new contributors could take the time
 to present themselves and their plans as you have done.

 Regards,

 Tomeu

Thanks for your great introduction. It is a good habit to present 
oneself and his role to the community. I would like to encourage others 
to do so as well.

Looking forward to work with you,
Simon



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

Re: [Sugar-devel] Introduction

[Walter Bender]

On Mon, May 31, 2010 at 1:33 PM, xiaoqin ma maxiaoqin2...@gmail.com wrote:
 Tomeu asked me to write to the mailing list to get to know everyone.

 I am very passionate about Children education in developing country. I got
 my Ph.D from Computer Science and now I am a software engineer in San
 Francisco Area.

 I would like to devote time and effort to the sugarlab. I am familiar with
 C, C++, Java. If there is a need, I can program in any language.

 I feel excited about the idea of OLPC and would like to contribute!

Welcome to Sugar Labs... See you in #sugar on irc.freenode.net.

-walter

 ___
 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] Introduction

[xiaoqin ma]

 That is a cool site. I did a lot of system, especially storage system, file
 system work in school. I'm also now working on storage software. Really want
 to get to know details there. Really passionate to get to know more ...


 On Mon, May 31, 2010 at 10:39 AM, Walter Bender 
 walter.ben...@gmail.comwrote:

 On Mon, May 31, 2010 at 1:33 PM, xiaoqin ma maxiaoqin2...@gmail.com
 wrote:
  Tomeu asked me to write to the mailing list to get to know everyone.
 
  I am very passionate about Children education in developing country. I
 got
  my Ph.D from Computer Science and now I am a software engineer in San
  Francisco Area.
 
  I would like to devote time and effort to the sugarlab. I am familiar
 with
  C, C++, Java. If there is a need, I can program in any language.
 
  I feel excited about the idea of OLPC and would like to contribute!

 Welcome to Sugar Labs... See you in #sugar on irc.freenode.net.

 -walter

  ___
  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] Introduction - guidance needed

[James Simmons]

Roopesh,

If you're interested in developing Activities you might check out the
FLOSS Manual Make Your Own Sugar Activities! at this URL:

http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction

You might want to check out http://activities.sugarlabs.org to see
what is already available.  That might give you ideas about where you
could contribute.

You don't need a dedicated Linux box to do development for Sugar.  You
could run Linux in a VM on your laptop if it has enough memory to do
that, or you could set up the laptop to boot either Linux or Windows.
I do the dual-boot option myself.  You just need to create a partition
on your hard drive to hold Linux.  Having Linux partitions on your
laptop will not affect your experience running Windows, other than
losing the disk space the partitions use.

James Simmons

 Date: Fri, 23 Apr 2010 16:08:05 +0530
 From: Roopesh P Raj roopesh.p...@gmail.com
 Subject: [Sugar-devel] Introduction - guidance needed
 To: sugar-devel@lists.sugarlabs.org
 Message-ID:
        m2qabbbe62e1004230338wadccd1cckaf39bcb7abb42...@mail.gmail.com
 Content-Type: text/plain; charset=iso-8859-1

 Hi All,

 I am an experienced python developer, I have also worked with zope, css,
 html, javascript, java, and web framework like turbogears. I have a physics
 background and is very much interested in educational activities.

 I came to know about the project through OLPC project page. I am interested
 in getting involved in sugar lab project in what ever way I can. I can
 contribute through code contribution, bug fixes, testing etc. I can also
 contribute in documenting the work also.

 Please guide me in getting started - please suggest me any projects which
 requires python expertise so that I can start exploring.

 I don't have a linux box, I have only a laptop with windows installed. Will
 that be a problem?

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

Re: [Sugar-devel] Introduction - guidance needed

[Walter Bender]

On Fri, Apr 23, 2010 at 6:38 AM, Roopesh P Raj roopesh.p...@gmail.com wrote:
 Hi All,

 I am an experienced python developer, I have also worked with zope, css,
 html, javascript, java, and web framework like turbogears. I have a physics
 background and is very much interested in educational activities.

 I came to know about the project through OLPC project page. I am interested
 in getting involved in sugar lab project in what ever way I can. I can
 contribute through code contribution, bug fixes, testing etc. I can also
 contribute in documenting the work also.

In addition to Jim's suggestion re writing an activity, we have a
number open tickets of varying sorts in our bug tracker
(bugs.sugarlabs.org) and a number of open feature requests described
in our wiki (wiki.sugarlabs.org/go/Features) as places to get
inspiration.

 Please guide me in getting started - please suggest me any projects which
 requires python expertise so that I can start exploring.

 I don't have a linux box, I have only a laptop with windows installed. Will
 that be a problem?

Not a problem. You can install Sugar in a VM that runs in Windows.

regards.

-walter


 Warm Regards,
 Roopesh

 ___
 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] Introduction and question about introducing Sugar development

[Aleksey Lim]

(I guess I forgot to change cc list)

On Wed, Jul 08, 2009 at 11:29:16PM +0200, Bernie Innocenti wrote:
 On 07/08/09 22:45, Steve Dalton wrote:
  I started having a look at the speak app - this is perhaps something I
  could maintain.
 
 Sure.  alsroot is listed as the current maintainer, but he's already got
 plenty of activities to maintain so I guess he'll be glad to let you
 take Speak over or, even better, co-maintain Speak with you.

sure, ask Joshua(Cc'ed) to add you to git.sl.o/speak commiters list

  I've also been having a good look around gitorious and found this:
 
  http://git.sugarlabs.org/projects/listen-spell-new
  
  Which looks like the speak-and-spell type applicaton that you talked
  about. I believe this is a fork of listen-spell which was a Google
  Summer of Code project last year.
 
 There's no code in git, however.  I'm cc'ing chiragjain1989 in case he
 can tell us more.

I guess its the same project

  I think it's quite fitting that there is a speak and spell app for the
  XO... the XOs remind me a lot of the speak and spell units (it's the
  moulded plastic). ET phone home? Maybe we also need a SETI app :P
 
 lol ;-)
 
 Please, also keep the sugar-devel@ mailing list on cc for this kind of
 communication, so others can jump in with their ideas and suggestions.
 
 -- 
// Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs   - http://sugarlabs.org/
 

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

Re: [Sugar-devel] Introduction and question about introducing Sugar development

[Tomeu Vizoso]

2009/6/26 Steve Dalton steve.dal...@gmail.com:
 Hi All

 Just went on IRC channel - but no-one around - so I'll try here.

 Steve Dalton here from Gold Coast, Queensland, Australia. I'm an experienced 
 developer - mainly C/C++/Java/Groovy - but also dabble with Ruby/Python, just 
 starting out playing with Sugar development

 I was kindly donated 5 XOs a while back and I have been trying to get a bit 
 of a local OLPC developers group started here in QLD. Have young kids and my 
 (almost) 4 year old is already getting stuck into Sugar and working things 
 out which makes me think you guys are onto something really awesome - I'd 
 love to help in some way.

 Anyway - one way I think I might be able to stimulate some local activity is 
 by doing some sort of live demo on developing with Sugar. I was hoping to 
 demo something at Barcamp Brisbane next month and possibly something at the 
 OSDC (Open Source Developers Conference) in Brisbane later this year if it 
 works. I have made one of my paper submission for OSDC a Sugar one but It's 
 sitting in my drafts folder until I can be sure I have something that has 
 half a chance of working out (I like jumping in at the deep-end but don't 
 want to make a complete fool of myself).

 Does anyone have any good suggestions on what to do? I've done the Hello 
 world demo and had a look at some of the activities already developed... but 
 was hoping to do something a little more interesting with some cool value 
 to get people interested. Are there any canned demos or tutorials around that 
 anyone can recommend? Might give me some ideas.

Not that I know, though my recommendation would be to check out how
your kid is using Sugar and think of how the learning experience could
be improved. Most experienced developers will be happier to help if
it's something that addresses a real need than if it's something done
out of pure curiosity.

Regards,

Tomeu

 Many thanks in advance
 Steve

 --
 I did have a signature, but the dog ate it.

 google:steve.dalton | skype:spidieman | msn: m...@steve.dalts.net | 
 yahoo:daltonsp | aol: spidie100 | twitter: @spidie | mynetfone:09203861

 ___
 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] Introduction and question about introducing Sugar development

[Bernie Innocenti]

On Fri, 2009-06-26 at 12:53 +1000, Steve Dalton wrote:
 Just went on IRC channel - but no-one around - so I'll try here.

The #sugar channel is usually very active.

This weekend, most Sugar Labbers are in Berlin for the LinuxTag 
FUDCon, and anyway it was night in Europe and US when you posted this.


 Steve Dalton here from Gold Coast, Queensland, Australia. I'm an
 experienced developer - mainly C/C++/Java/Groovy - but also dabble
 with Ruby/Python, just starting out playing with Sugar development

As you learn your way through Sugar, please let us know what was hard to
discover or unclear in our documentation, development process or code.

We need to find out what makes it hard for newcomers to get started to
lower the bar as much as possible.  We go around saying that young kids
will one day become contributors, so there's a lot of work to do in this
area.

If sugar-jhbuild defeats you, try my streamlined clone.  I believe it
makes things faster and easier, but it's been tested lightly on distros
other than Fedora 11.


 I was kindly donated 5 XOs a while back and I have been trying to get
 a bit of a local OLPC developers group started here in QLD. Have young
 kids and my (almost) 4 year old is already getting stuck into Sugar
 and working things out which makes me think you guys are onto
 something really awesome - I'd love to help in some way.

Also let us know what parts of the UI work well and which ones don't for
kids that young.


 Anyway - one way I think I might be able to stimulate some local
 activity is by doing some sort of live demo on developing with Sugar.
 I was hoping to demo something at Barcamp Brisbane next month and
 possibly something at the OSDC (Open Source Developers Conference) in
 Brisbane later this year if it works. I have made one of my paper
 submission for OSDC a Sugar one but It's sitting in my drafts folder
 until I can be sure I have something that has half a chance of working
 out (I like jumping in at the deep-end but don't want to make a
 complete fool of myself).


Are you aware of the OLPC friends local community in Oz?

 http://www.olpcfriends.org/


My good friend Joel Stanley from Adelaide (also on this list) was
planning to start a Local Lab some time ago.  You should get in contact
with him as well.


 Does anyone have any good suggestions on what to do? I've done the
 Hello world demo and had a look at some of the activities already
 developed... but was hoping to do something a little more interesting
 with some cool value to get people interested. Are there any canned
 demos or tutorials around that anyone can recommend? Might give me
 some ideas.

Many others can give you better advice than me on the current status of
development, but my feeling is that we need to involve more people on
enhancing existing activities rather than start new ones.

From your skill profile, you seem suitable for working on Browse, which
is xulrunner C++ code wrapped in a Python UI.  Caution: it's non-trivial
code, certainly not recommended for beginners.

Since you have pre-school kids, you might want to work on enhancing
Speak.  It's currently unmaintained, but very simple and cool IMHO...
Wouldn't it be awesome if someone grew it into a Speak  Spell activity?


 Many thanks in advance

Thanks to *you* for helping!

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs   - http://sugarlabs.org/


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