[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 at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


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