[Sugar-devel] Fwd: Deployment of ASLOv3

[Jatin Dhankhar]

---------- Forwarded message ---------
From: Jatin Dhankhar <dhankhar.jatin at gmail.com>
Date: Mon, Sep 3, 2018 at 10:45 PM
Subject: Re: Deployment of ASLOv3
To: James Cameron <quozl at laptop.org>

Forgot to reply-all, forwarding the original message here.

That's a long of issues.
Thank you James for taking out time and compiling the list.
I don't have a definitive strategy in mind.
How about tackling them one issue at a time, each issue segregated into
categories, with priorities ranging from important to enhancements.
I am not sure about many issues.

1.

> - a transition plan is needed, to explain how to handle the Fedora 18
>   systems running Sugar 0.112 and earlier,
>
Didn't get this one. Do we need to support older client with a minimal
version of the website ?

2.

> how to list the compatible Sugar versions for an activity release?
>   activities.sugarlabs.org asks for this when uploading an activity,
>   and it works well with the Browse presentation of Sugar version
>   through the user agent string,
>

Right we are using a simple heuristics to determine min sugar version for
an activity
https://github.com/sugarlabs/aslo-v3/blob/master/aslo/api/release.py#L231
<https://github.com/sugarlabs/aslo-v3/blob/master/aslo/api/release.py#L191>
We currently don't log and use agent strings

3.

>  how to handle activities like Tam Tam, Fortune Hunter, Wikipedia and
>   soon Turtle Art, where the git repository makes more than one
>   activity bundle?
>

 Not sure about how different bundle works, for now we are using following
https://github.com/sugarlabs/aslo-v3/blob/master/activity-build-docker/Dockerfile#L8
to
generate .xo for source activity. If bundle is supplied as part of release
we give it preference (since the author attached that and wanted to release
it)


4.

>  how to handle activities like Browse, Measure, Speak, and Record,

  where non-master branches are used to make bundles compatible with
  different systems,

I think we took care of the branch. But different branch (i.e multiple
branches) for different systems are not supported, since it means different
bundles for a single activity. This needs to worked upon.


5.

> many activities are missing; e.g. Record,
>
Yes, not all activities are included

 6.

> an activity version number is not shown; workaround is to hover over
>   the download link, but this doesn't work in Browse because the link
>   URL is not shown,
>
Yes, we can add version on the UI as well. Hardest part is to settle on a
definitive and consistent UI.

7.

>  blurred icons; these are embedded PNG instead of SVG, and so when
>   they scale up they blur,
>
Yes, not many activities have svg icons.

8.

> page title is "Software Center | SugarLabs"; (a) don't think
>   "Software Center" is the right name; was there consensus?  (b) this
>   must be internationalised for more languages than "es" and "hi", and
>   (c) "SugarLabs" should be "Sugar Labs",
>
What should be the right name ?


9.

> in the detail view, the icons for the headings are too close to the
>   text, e.g. "<spiky circle>Activity" and "<pancake stack>Details",
>
Yes, that is an easy fix. Adding margin to font-awesome icons.


10.

> at the bottom of the page, the links to "Sugar Labs", "Development",
>   and "Resources" do not work,
>
Yes, not every link was decided. Easy fix.

11.

> the general layout of the page is unlike the other services at Sugar
>   Labs, as if there is no central theme,
>
Yes, that is one of the biggest issue, a consistent theme.

 12.

> Browse on Fedora 18 reports several instances of "Cross-origin
>   script load denied by Cross-Origin Resource Sharing policy.", and
>   the page does not finish loading,
>
Didn't test it on browse. Major browsers didn't complain about this.


13.

> many off-site resources are used; such as
>   https://cdnjs.cloudflare.com/ajax/libs/mdbootstrap/4.3.2/js/mdb.min.js
>   these must be local so as to avoid multiple DNS queries, to allow
>   port proxied use, and to pipeline requests.
>
Self hosting is on the list. I thought having a CDN resource will improve
the performance and reduce latency.
How about use both with cdn as fallback.



> For interest, an automated publishing tool for
> activities.sugarlabs.org is available at
> https://github.com/sugarlabs/sugar-tools/blob/master/activity-publish
>
> This tool decreases the time between "git tag vN" and activity
> available for download to a few seconds, and leverages our existing
> infrastructure.
>

Didn't knew about publish.
I wanted to integrate aslo-v3 closely with Github, so I followed that
route.

I might be wrong about lots of things. Do let me know.

Thanks,
Jatin Dhankhar


On Mon, Sep 3, 2018 at 2:55 AM James Cameron <quozl at laptop.org> wrote:

> Thanks.  Good progress.  Some issues;
>
> - a transition plan is needed, to explain how to handle the Fedora 18
>   systems running Sugar 0.112 and earlier,
>
> - how to list the compatible Sugar versions for an activity release?
>   activities.sugarlabs.org asks for this when uploading an activity,
>   and it works well with the Browse presentation of Sugar version
>   through the user agent string,
>
>
> https://github.com/sugarlabs/aslo/blob/master/site/app/config/core.php#L224
>   https://github.com/sugarlabs/browse-activity/blob/master/browser.py#L672
>
> - how to handle activities like Tam Tam, Fortune Hunter, Wikipedia and
>   soon Turtle Art, where the git repository makes more than one
>   activity bundle?
>
> - how to handle activities like Browse, Measure, Speak, and Record,
>   where non-master branches are used to make bundles compatible with
>   different systems,
>
> - many activities are missing; e.g. Record,
>
> - an activity version number is not shown; workaround is to hover over
>   the download link, but this doesn't work in Browse because the link
>   URL is not shown,
>
> - activity version is out of date; e.g. Read download is of 119, but
>   latest release is 121, what happened to 120?
>
> - blurred icons; these are embedded PNG instead of SVG, and so when
>   they scale up they blur,
>
> - changing the orange tags button does nothing to the current result
>   set, and there's no view by tag,
>
> - page title is "Software Center | SugarLabs"; (a) don't think
>   "Software Center" is the right name; was there consensus?  (b) this
>   must be internationalised for more languages than "es" and "hi", and
>   (c) "SugarLabs" should be "Sugar Labs",
>
> - in the detail view, the icons for the headings are too close to the
>   text, e.g. "<spiky circle>Activity" and "<pancake stack>Details",
>
> - in the detail view, "License" should be "Licenses" for those
>   many activities with multiple license scenario,
>
> - at the bottom of the page, the links to "Sugar Labs", "Development",
>   and "Resources" do not work,
>
> - the general layout of the page is unlike the other services at Sugar
>   Labs, as if there is no central theme,
>
> - Browse on Fedora 18 reports several instances of "Cross-origin
>   script load denied by Cross-Origin Resource Sharing policy.", and
>   the page does not finish loading,
>
> - many off-site resources are used; such as
>   https://cdnjs.cloudflare.com/ajax/libs/mdbootstrap/4.3.2/js/mdb.min.js
>   these must be local so as to avoid multiple DNS queries, to allow
>   port proxied use, and to pipeline requests.
>
> Hope that helps.  Let me know if you need any clarification.
>
> For interest, an automated publishing tool for
> activities.sugarlabs.org is available at
> https://github.com/sugarlabs/sugar-tools/blob/master/activity-publish
>
> This tool decreases the time between "git tag vN" and activity
> available for download to a few seconds, and leverages our existing
> infrastructure.
>
> On Sun, Sep 02, 2018 at 10:03:15PM +0530, Jatin Dhankhar wrote:
> > I, like many others here believe that aslo-v3 will handle the scale and
> I will
> > be glad if others join us in making it happen.
> > A pilot version (running for a year now ) of aslo-v3 can be viewed
> here [1]
> > https://aslo3-devel.sugarlabs.org/en/.
> > Here's a small video demonstrating the publishing flow of
> packages [2]https://
> > www.youtube.com/watch?v=XNount59G0Y  (We can avoid the forking to new
> org and
> > do it directly on every release via sugarlabs org )
> > There are some things (frontend design, adding unit tests) that need to
> be
> > discussed and worked out.
> >
> > Thanks,
> > Jatin Dhankhar
> >
> > On Sun, Sep 2, 2018 at 1:35 AM Walter Bender <[3]walter.bender at gmail.com
> >
> > wrote:
> >
> >     Whereas (1) you guys have been diligent about working on this, I am
> >     confident we have something that can be (and will be maintained) and
> (2) it
> >     makes life for the activity maintainer much easier, I am in favor of
> moving
> >     forward on this.
> >
> >     -walter
> >
> >     On Sat, Sep 1, 2018 at 3:39 PM Vipul Gupta <[4]
> vipulgupta2048 at gmail.com>
> >     wrote:
> >
> >         Hello folks,
> >
> >         Jatin and I had a discussion on finishing up the long-awaited,
> >         constantly developing and quite an important issue. That is the
> >         deployment of ASLOv3. The source code has already been written
> and
> >         present [1] by Jatin in GSoC 2017, there were little problems
> that were
> >         holding back its deployment that I took charge of solving most
> of them
> >         in GSoC 2018. We came to the conclusion of working as we go
> along to
> >         get the activities online on the new server.
> >
> >         We would like the community to put forward their views on the
> same.
> >         Also, guide us on how to go on about it. Looking forward to
> getting
> >         this done as quickly as we can. The mentors of our projects can
> put
> >         forward their helpful insights as they know about the project(s)
> >         better.
> >
> >         Cordially,
> >         Vipul Gupta
> >         [5]Mixster | [6]Github
> >
> >     --
> >     Walter Bender
> >     Sugar Labs
> >     [7]http://www.sugarlabs.org
> >     [8]
> >
> > References:
> >
> > [1] https://aslo3-devel.sugarlabs.org/en/
> > [2] https://www.youtube.com/watch?v=XNount59G0Y
> > [3] mailto:walter.bender at gmail.com
> > [4] mailto:vipulgupta2048 at gmail.com
> > [5] https://mixstersite.wordpress.com/
> > [6] https://github.com/vipulgupta2048
> > [7] http://www.sugarlabs.org/
> > [8] http://www.sugarlabs.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20180904/b02c70bd/attachment-0001.html>