[Sugar-devel] Community Bonding Period

[Saumya Mishra]

Hello all,

My Project is - Port Sugar and core activities to Python3.

I had a good time with community members and mentors. I had a few meets
with James , Jui , Shaan and Rahul.

I have worked on Porting few activities to Python3. The activities include
showntell-activity, infoslicer, vncLauncher, solar-system and Frotz. The
solar-system activity is released and other activities are still in
progress. I will be working on those activities along with Jui to get them
released.

Along with this I also worked on some reviewing and testing of sugar source
code . I will continue this work in further weeks also.

I also worked on Port to TelepathyGLib of some activities -
activity-turtle-flags, and still working on activity-turtle-confusion and
AmazonasTortuga. I will also continue the work this week.

I have made two project plans one
 contains work on
sugar and fructose activities , second
 one includes work
on port of other activities. I will keep on updating my future plans as
To-Do's here with all Progress information.

Any suggestion or feedback is welcome.

Thanks and Regards
Saumya Mishra
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Community Bonding Period

[Chihurumnaya Ibiam]

Thanks for the update Jui.

On Sun, May 31, 2020 at 6:07 PM Jui Pradhan  wrote:

> Hi,
> My Project is - Maintain and release atleast 25 Sugar Activities. I had a
> good time coordinating with my mentor and attending the scheduled meets.
>
> My progress on the project includes my work on activities - iknowmyabcs,
> bridge, jumble, sugarchess, recall, nutrition, Analyze Journal, Pukllanapac
> and few changes to sugargame. You can see my merged commits here
> 
> .
>
> In the coming week I have planned to work on those activities which have
> incomplete / pending Pull requests. I haven't specifically narrowed down
> the ones I will be working on. Moreover, I will be testing the activities
> Saumya will be porting to python 3 and make necessary changes for the
> activity to be released. :)
>
> Any suggestion or feedback is welcome.
> Thankyou.
>
> Regards,
> Jui Pradhan
>
>
>
> [image: Mailtrack]
> 
>  Sender
> notified by
> Mailtrack
> 
>  05/31/20,
> 10:35:16 PM
> ___
> 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] Mode of distribution of Sugar Activities

[sugar]

Hello Srevin,

Yes, currently there is no single source of python3 activities (hence the 
asov4). But even after asolv4 is ready, there will be a gap between submitting 
activities for publication and approved activities being added to aslov4.

I think bundling activities as .xo file is the first step most developers do. 
Some of the activities are than are than packaged as distro specific packages 
(deb, rpm etc.) and submitted to distros to be added in their repositories. 
This allows installing activities natively like `# apt install 
sugar-browse-activity` . Shaan Subbaiah is currently working with Debian but I 
do not know if he submits packages as well. Maybe you can try yourself to 
submit your package to Debian and Fedora but its not straight forward and 
getting accepted is difficult, they have a rigorous quality standard including 
package should be reasonably free from bugs and should not interfere/modify 
other packages upon installation.

Activities on demo website are from Tony Anderson's repo 
 
https://github.com/tony37/Sugaractivities/tree/master/activities . These are 
old and mostly python2 based. Currently prototype of aslov4 with python3 
activities is available at http://dev.laptop.org/pub/us/activities/focal/ but I 
do not think it is meant for wider use and currently has only few activities as 
you can see from http://dev.laptop.org/pub/us/activities/focal/js/index.js .

As for, aslov4, it seems to be a lot smaller project than I expected (unless I 
am proved to be wrong, which is usually the case with every programming 
project). It should be completed in less than a month. Currently I am busy, so 
most likely, there will be very little progress until July.But you can head 
over to wiki https://github.com/free-libre-software/sugarappstore/wiki to find 
what needs to be done. Maybe you can implement some of the features. I will try 
to  push a broad test for generator part. So that if you work on it, you can 
work more confidently, knowing that changes you make won't create any 
regressions and compare changes using 'diff' between test output and actual 
output (change test output accordingly, if change is not regression but 
intended).

Regards,
Manish


May 31, 2020, 22:00 by srevi...@gmail.com:

> Hello, hope all are doing well
>
> While reading the sugarlabs wiki, I had come across > packages.sugarlabs.org 
> >  which seemed to work before, but at the 
> moment, I could not connect to it
> As long a the aslov4 is only under construction, I faced a confusion on where 
> is the right place to submit new activities. 
> On sugar-docs (GitHub), there is a small instance of uploading the .xo of a 
> python2 compatible activity however. Unfortunately, I failed in finding a 
> proper guide to "How to publish a sugar activity'. I had previously seen in 
> some discussions on IRC, but however the last known reference to the > 
> packages.sugarlabs.org >  is here > 
> https://bugs.sugarlabs.org/ticket/4786>  during GCI 2014. I can also see 
> that, as we have a lot of a activities not only on GitHub, that is, on 
> gitorious, etc. So I coud not find a curated list of sugarlabs' activities 
> listed except on the work by @radii (aslov4),
>
> Can anyone guide me, so that I (or someone who is interested) can update the 
> public wiki with the same information
>
> Few more links that confused me:
> * > downloads.sugarlabs.org 
> * > people.sugarlabs.org 
>
> Has distribution of activities turned into Linux Distribution specific 
> binaries like .deb and .rpms, or are (*.xo) bundles' still used for public 
> activity distribution (other than OLPC OS?); This also leads to another 
> question, i.e if most activities are packaged in .xo's or only (.deb, .rpm, 
> flatpak)
>
> Thanks
> V/r
> Srevin Saju
>

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

Re: [Sugar-devel] Community Bonding Period: Scale Degree Design Proposal

[Devin Ulibarri]

Hi All,
Aviral is doing great work.
Our strategy has been for him to fix more straightforward bugs related
to key/mode while we work together on a design for the less trivial
ones.
An average of 4 days a week, he has been getting a 30-60 minute music
theory lesson as well so that he can better identify conceptual errors
as we move ahead. :)
Devin
On Sun, 2020-05-31 at 22:10 +0530, Aviral Gangwar wrote:
> Hello all
> 
> This is a good time for an update since the Community Bonding Period
> is at an end.
> 
> During community bonding, I had regular meetings with my mentor
> Devin, Walter, and the rest of the MB team. We made some significant
> process, found some new issues, and subsequently worked on a fix.
> We fixed octave calculation, sharp and flat preferences for Lilypond
> Output, and finally the initial work of my proposal; renaming the old
> scale degree block to nth modal pitch and following changes to its
> functionality. [zero based indexing] 
> This work can be audited in
> PRs: #2275, #2284, and #2286 respectively.
> 
> - Besides this, I've had a few intensive design discussions with
> Devin regarding issue #1957 which has appeared as a bottleneck at
> times.
> 
> - I've also started work on the crux of my proposal: the addition of
> a new scale degree block and implemented some basic functionality.
> 
> In the upcoming week, I've planned on devising a basic solution for
> #1957 which would solve much of the problem and proceed with work on
> scale degree block. [For technicalities of that, one can visit #2058]
> 
> 
> Thanks
> Aviral
> 
> 
> 
> ___
> 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

[Sugar-devel] Community Bonding Period

[Jui Pradhan]

Hi,
My Project is - Maintain and release atleast 25 Sugar Activities. I had a
good time coordinating with my mentor and attending the scheduled meets.

My progress on the project includes my work on activities - iknowmyabcs,
bridge, jumble, sugarchess, recall, nutrition, Analyze Journal, Pukllanapac
and few changes to sugargame. You can see my merged commits here

.

In the coming week I have planned to work on those activities which have
incomplete / pending Pull requests. I haven't specifically narrowed down
the ones I will be working on. Moreover, I will be testing the activities
Saumya will be porting to python 3 and make necessary changes for the
activity to be released. :)

Any suggestion or feedback is welcome.
Thankyou.

Regards,
Jui Pradhan



[image: Mailtrack]

Sender
notified by
Mailtrack

05/31/20,
10:35:16 PM
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Community Bonding Period - Music Blocks JS Export

[Favour Kelvin]

Great progress

On Sun, 31 May 2020, 16:34 Jaskirat Singh,  wrote:

> Glad to see this progress going on
>
> On Sun, May 31, 2020 at 5:34 PM Samson Goddy 
> wrote:
>
>> This is great.
>>
>> On Sun, May 31, 2020, 12:08 PM Walter Bender 
>> wrote:
>>
>>>
>>>
>>> On Sun, May 31, 2020 at 1:39 AM Anindya Kundu 
>>> wrote:
>>>
 Hello,

 Coming to the end of the Community Bonding period, I want to sum up my
 initial progress on my project during the period, and my plans ahead as the
 official Coding Period begins.

 I had several meetings with my mentor, Walter, and other members of the
 Music Blocks group for this year's GSoC. Walter walked me through some of
 the complex functions, and we discussed on how to proceed.

 During the period, I've worked on the ES6 port, to clean up the code
 and make it ready for further work. Specifically, I've completely 
 refactored
 logo.js and turtle.js, which are most important to my project. In
 addition, I've done a lot of cleanup w.r.t whitespaces, comments, short
 statements, etc. And, I'm satisfied that the files are in a good condition
 for me to start with. In addition, I've separated out note execution
 related behaviour to an external class named NoteController.

 In the upcoming weeks, I'll primarily be focused on separation of Model
 , View, and Controller from logo.js and turtle.js. For better modular
 behaviour, I've conceptualised 5 models and 4 controllers. The
 NoteController, mentioned above, is an experimental feature which
 needs further discussion; I intend to carry it out in parallel in the
 coming week.

 I'm keeping a log, and all my progress is maintained in a GitHub
 project  created
 in my fork of Music Blocks. It has 5 columns: Milestones, To do, In
 progress, Done, and Plans. Milestones keeps track of my overall
 progress and upcoming goals, Plans keeps note of my conceptualised
 ideas, while the rest keep track (archived after milestone achieved) of
 intermediate progress.

 Thank You.

 *Anindya Kundu*


>>> Great progress so far. I think you are laying the foundation for a
>>> successful project.
>>>
>>> regards.
>>>
>>> -walter
>>> --
>>> Walter Bender
>>> Sugar Labs
>>> http://www.sugarlabs.org
>>> 
>>> ___
>>> 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
>>
> ___
> 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

[Sugar-devel] Community Bonding Period: Scale Degree Design Proposal

[Aviral Gangwar]

Hello all

This is a good time for an update since the Community Bonding Period is at
an end.

During community bonding, I had regular meetings with my mentor Devin,
Walter, and the rest of the MB team. We made some significant process,
found some new issues, and subsequently worked on a fix.
We fixed octave calculation, sharp and flat preferences for Lilypond
Output, and finally the initial work of my proposal; renaming the old scale
degree block to nth modal pitch and following changes to its functionality.
[zero based indexing]
This work can be audited in PRs: #2275
, #2284
, and #2286
 respectively.

- Besides this, I've had a few intensive design discussions with Devin
regarding issue #1957 
which has appeared as a bottleneck at times.

- I've also started work on the crux of my proposal: the addition of a new
scale degree block and implemented some basic functionality.

In the upcoming week, I've planned on devising a basic solution for #1957
 which would solve
much of the problem and proceed with work on scale degree block. [For
technicalities of that, one can visit #2058
]


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

Re: [Sugar-devel] Community Bonding Period - Music Blocks JS Export

[Jaskirat Singh]

Glad to see this progress going on

On Sun, May 31, 2020 at 5:34 PM Samson Goddy 
wrote:

> This is great.
>
> On Sun, May 31, 2020, 12:08 PM Walter Bender 
> wrote:
>
>>
>>
>> On Sun, May 31, 2020 at 1:39 AM Anindya Kundu 
>> wrote:
>>
>>> Hello,
>>>
>>> Coming to the end of the Community Bonding period, I want to sum up my
>>> initial progress on my project during the period, and my plans ahead as the
>>> official Coding Period begins.
>>>
>>> I had several meetings with my mentor, Walter, and other members of the
>>> Music Blocks group for this year's GSoC. Walter walked me through some of
>>> the complex functions, and we discussed on how to proceed.
>>>
>>> During the period, I've worked on the ES6 port, to clean up the code and
>>> make it ready for further work. Specifically, I've completely refactored
>>> logo.js and turtle.js, which are most important to my project. In
>>> addition, I've done a lot of cleanup w.r.t whitespaces, comments, short
>>> statements, etc. And, I'm satisfied that the files are in a good condition
>>> for me to start with. In addition, I've separated out note execution
>>> related behaviour to an external class named NoteController.
>>>
>>> In the upcoming weeks, I'll primarily be focused on separation of Model,
>>> View, and Controller from logo.js and turtle.js. For better modular
>>> behaviour, I've conceptualised 5 models and 4 controllers. The
>>> NoteController, mentioned above, is an experimental feature which needs
>>> further discussion; I intend to carry it out in parallel in the coming week.
>>>
>>> I'm keeping a log, and all my progress is maintained in a GitHub project
>>>  created in my
>>> fork of Music Blocks. It has 5 columns: Milestones, To do, In progress,
>>> Done, and Plans. Milestones keeps track of my overall progress and
>>> upcoming goals, Plans keeps note of my conceptualised ideas, while the
>>> rest keep track (archived after milestone achieved) of intermediate
>>> progress.
>>>
>>> Thank You.
>>>
>>> *Anindya Kundu*
>>>
>>>
>> Great progress so far. I think you are laying the foundation for a
>> successful project.
>>
>> regards.
>>
>> -walter
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Community Bonding Period - Music Blocks JS Export

[Samson Goddy]

This is great.

On Sun, May 31, 2020, 12:08 PM Walter Bender 
wrote:

>
>
> On Sun, May 31, 2020 at 1:39 AM Anindya Kundu 
> wrote:
>
>> Hello,
>>
>> Coming to the end of the Community Bonding period, I want to sum up my
>> initial progress on my project during the period, and my plans ahead as the
>> official Coding Period begins.
>>
>> I had several meetings with my mentor, Walter, and other members of the
>> Music Blocks group for this year's GSoC. Walter walked me through some of
>> the complex functions, and we discussed on how to proceed.
>>
>> During the period, I've worked on the ES6 port, to clean up the code and
>> make it ready for further work. Specifically, I've completely refactored
>> logo.js and turtle.js, which are most important to my project. In
>> addition, I've done a lot of cleanup w.r.t whitespaces, comments, short
>> statements, etc. And, I'm satisfied that the files are in a good condition
>> for me to start with. In addition, I've separated out note execution
>> related behaviour to an external class named NoteController.
>>
>> In the upcoming weeks, I'll primarily be focused on separation of Model,
>> View, and Controller from logo.js and turtle.js. For better modular
>> behaviour, I've conceptualised 5 models and 4 controllers. The
>> NoteController, mentioned above, is an experimental feature which needs
>> further discussion; I intend to carry it out in parallel in the coming week.
>>
>> I'm keeping a log, and all my progress is maintained in a GitHub project
>>  created in my
>> fork of Music Blocks. It has 5 columns: Milestones, To do, In progress,
>> Done, and Plans. Milestones keeps track of my overall progress and
>> upcoming goals, Plans keeps note of my conceptualised ideas, while the
>> rest keep track (archived after milestone achieved) of intermediate
>> progress.
>>
>> Thank You.
>>
>> *Anindya Kundu*
>>
>>
> Great progress so far. I think you are laying the foundation for a
> successful project.
>
> regards.
>
> -walter
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> 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

[Sugar-devel] Mode of distribution of Sugar Activities

[Srevin Saju]

Hello, hope all are doing well

While reading the sugarlabs wiki, I had come across packages.sugarlabs.org
which seemed to work before, but at the moment, I could not connect to it
As long a the aslov4 is only under construction, I faced a confusion on
where is the right place to submit new activities.
On sugar-docs (GitHub), there is a small instance of uploading the .xo of a
python2 compatible activity however. Unfortunately, I failed in finding a
proper guide to "How to publish a sugar activity'. I had previously seen in
some discussions on IRC, but however the last known reference to the
packages.sugarlabs.org is here https://bugs.sugarlabs.org/ticket/4786
during GCI 2014. I can also see that, as we have a lot of a activities not
only on GitHub, that is, on gitorious, etc. So I coud not find a curated
list of sugarlabs' activities listed except on the work by @radii (aslov4),

Can anyone guide me, so that I (or someone who is interested) can update
the public wiki with the same information

Few more links that confused me:
* downloads.sugarlabs.org
* people.sugarlabs.org

Has distribution of activities turned into Linux Distribution specific
binaries like .deb and .rpms, or are (*.xo) bundles' still used for public
activity distribution (other than OLPC OS?); This also leads to another
question, i.e if most activities are packaged in .xo's or only (.deb, .rpm,
flatpak)

Thanks
V/r
Srevin Saju
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Community Bonding Period - Music Blocks JS Export

[Walter Bender]

On Sun, May 31, 2020 at 1:39 AM Anindya Kundu 
wrote:

> Hello,
>
> Coming to the end of the Community Bonding period, I want to sum up my
> initial progress on my project during the period, and my plans ahead as the
> official Coding Period begins.
>
> I had several meetings with my mentor, Walter, and other members of the
> Music Blocks group for this year's GSoC. Walter walked me through some of
> the complex functions, and we discussed on how to proceed.
>
> During the period, I've worked on the ES6 port, to clean up the code and
> make it ready for further work. Specifically, I've completely refactored
> logo.js and turtle.js, which are most important to my project. In
> addition, I've done a lot of cleanup w.r.t whitespaces, comments, short
> statements, etc. And, I'm satisfied that the files are in a good condition
> for me to start with. In addition, I've separated out note execution
> related behaviour to an external class named NoteController.
>
> In the upcoming weeks, I'll primarily be focused on separation of Model,
> View, and Controller from logo.js and turtle.js. For better modular
> behaviour, I've conceptualised 5 models and 4 controllers. The
> NoteController, mentioned above, is an experimental feature which needs
> further discussion; I intend to carry it out in parallel in the coming week.
>
> I'm keeping a log, and all my progress is maintained in a GitHub project
>  created in my fork
> of Music Blocks. It has 5 columns: Milestones, To do, In progress, Done,
> and Plans. Milestones keeps track of my overall progress and upcoming
> goals, Plans keeps note of my conceptualised ideas, while the rest keep
> track (archived after milestone achieved) of intermediate progress.
>
> Thank You.
>
> *Anindya Kundu*
>
>
Great progress so far. I think you are laying the foundation for a
successful project.

regards.

-walter
-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

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