[Sugar-devel] Progress Update (Port Sugar and core activities to Python3) : 28th May 2020

[James Cameron]

Thanks Saumya.

Have you a project plan you can share?  While your GSoC proposal
contained a plan, we did not publish the proposals this year, and
there are likely to be changes to the plan as you learn more detail.

You've said "Review the source code of sugar after 0.112 is released".
I'm worried that isn't exactly what I had expected.  I've seen you
have been reviewing the current sugar code.  Perhaps I did a bad job
of explaining it.

Our project idea
https://github.com/sugarlabs/GSoC/blob/master/Ideas-2020.md#port-sugar-and-core-activities-to-python-3
may be a bit difficult to parse, so I'll take the first item on the
list and expand it for you.

"Review the Sugar source code changes since 0.112 that were made for
porting to Python 3,"

0.  consider the set of repositories sugar, sugar-toolkit-gtk3,
sugar-artwork, sugar-toolkit-gtk3, and each of the Fructose "core"
activity repositories,

1.  in each repository, list the set of _commits_ after the date of
the 0.112 tag, (not the source code of the master branch, but the
commits that led to it),

2.  exclude the commits that were not made for porting to Python 3,

3.  review the commits for correctness using our "Guide for Reviewers"
and our "Python 3 Porting Guide"; in particular whether the commits
are (a) a complete port to Python 3, (or Six in the toolkit), and (b)
adequately tested,

The discovery that led to this project idea was that despite porting
to Python 3 we have seen some regressions that suggest that our
porting was imprecise or hasty.

The next point in the project idea recognises that we didn't have a
good method of testing.

On Thu, May 28, 2020 at 11:29:05AM +0530, Saumya Mishra wrote:
> Hello All,
> 
> The work I have done so far and I am going to do next-
> 
> Review the source code of sugar after 0.112 is released, Test every patch and
> make changes wherever needed. Change I have made so far is mainly related to
> PEP 8 fixes however there are some fixMe comments on various places I am
> planning to work next on them as well as in Sugar - text clipping cannot get
> removed , the feature shows some errors, 
> [1]https://github.com/sugarlabs/sugar/issues/856 working on this. The sugar has
> currently 39 issues and 16 pull requests open, Some of the pull requests have
> significantly less amount of work required in order to get them merged. My work
> will be to review all of them and make changes after testing my work.
> 
> Work on Port of telepathy to TelepathyGLib - I first decided to work on all the
> activities , which share common code with Turtle-Art as a rebasing has to be
> done first. I found 4 activities related activity-turtle-flags,
> AmazonasTortuga, activity-turtle confusion, amazonas-activity . Turtle-Art has
> ported to TelepathyGLib before.
> 
> Work on infoslicer activity , Port to Python3 and from sgmllib to html.parser
> as sgmllib is dropped in python3 and HTMLParser class is designed as a base
> class and it extends SGMLParser class defined in module sgmllib. Port has done
> , but activity requires testing .
> 
> VncLauncher - activity is ported along with required x11vnc distro specific
> support. However [2]@James Cameron  and I thought about a slight modification ,
> as users of activity are teachers, and it is not necessary that they will be
> familiar with use of IP addresses, Next thing is to try registering an mdns
> name on the network and let the VNC client use that. 
> 
> I also had a meeting with James on IRC on 25th May 2020.
> 
> Thanks for reading , Suggestions are welcomed.
> 
> Saumya Mishra
> 
> References:
> 
> [1] https://github.com/sugarlabs/sugar/issues/856
> [2] mailto:quozl at laptop.org

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