<div dir="ltr">Hi Tony,<div><br></div><div>I think the same, as per commit history project didn't get much attention recently. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">The website itself is implemented in PhP and is patterned after the Mozilla addons site.</span></blockquote><div><br></div><div>Yes, the README mentions it's based upon Remora<font color="#24292e">(</font><a href="http://wiki.mozilla.org/Update:Remora" style="font-family:sfmono-regular,consolas,"liberation mono",menlo,courier,monospace;font-size:15px;white-space:pre-wrap;background-color:transparent;box-sizing:border-box;color:rgb(3,102,214);text-decoration-line:none">http://wiki.mozilla.org/Update:Remora</a> ) which old and deprecated now in favor of AMO (<a href="https://wiki.mozilla.org/AMO:Developers">https://wiki.mozilla.org/AMO:Developers</a>) .</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">At the moment I am trying to find out which of the activities actually work in the current release of Sugar. The library currently has about 600 activities. A Sugar activity is intended to be self-contained (any dependencies not satisfied by Sugar are to be incorporated in the bundle).</span></blockquote><div><br></div><div>I think it's a moonshot but I am thinking to include a testing suite to determine whether a current version builds against a certain sugar version by using a CI or something like OpenSuse's QA (<a href="http://open.qa/">http://open.qa/</a>) for more comprehensive suite. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">How this will be done is a mystery to me. Logically, each of the versions of an activity should be commited in git so that a developer (or maintainer) can the changes made over time.</span></blockquote><div>Yes, that seems right thing to do, last year Arch Linux shifted all their AUR packages to a git backend, maybe they can help, I can try finding persons who carried out the transition.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">If you look at the ASLO site, it seems clear that the page needs to specify more than which versions of Sugar are supported. It will need to specify which models of the XO are supported. It will also need to mention any restrictions on architecture or peripherals needed for the users system (microphone, camera, network connection - wired or wireless, and so on). </span></blockquote><div><br></div><div>Yes more like a Manifest, similar to what Play Stores does for Android. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px"> My plan is to use Django (which enables code to be in Python and not PhP). The school server already provides sqllite, mariadb, and postgresql so db support is readily available. Django is designed to support fusion - creating web pages dynamically based on information from a db and so should match the requirement.</span></blockquote><div>Yes, re-write seems a reasonable choice. One thing that I am curious is that current repo suggests that it's is a mix of Python and PHP and going full python would be a great move, in my opinion. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br style="font-size:12.8px"><span style="font-size:12.8px">Just for further background. Many deployments I work with have no access to the internet. To provide an alternative, I support a school server which XO users can access by wifi in the classroom</span></blockquote><div>I think point makes a strong case for easily replicable instances of ASLO with little to no configuration on the user side, which means we need to make a simple and consistent build process so that users can run their own versions of ASLO easily. Docker is a option worth looking into.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">I hope you will consider this challenging and not discouraging.</span></blockquote><div>Yes, I find it equally challenging and interesting.<br></div><div><br></div><div>I made a proposal ASLO that shares some of the concerns that you discussed . Kindly take a look and let me know what do you think of it. Here is the proposal link <a href="https://docs.google.com/document/d/1wECi_gtxyar3MWbC8ly6bjdW8SSLYe5YNcXPiTUUlkg/edit?usp=sharing">https://docs.google.com/document/d/1wECi_gtxyar3MWbC8ly6bjdW8SSLYe5YNcXPiTUUlkg/edit?usp=sharing</a></div><div><br></div><div><br></div><div>Thanks,</div><div>Jatin Dhankhar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 1, 2017 at 3:20 PM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi, Jatin<br>
<br>
The ASLO site is in desparate need of work. At the moment I am
trying to find out which of the activities actually work in the
current release of Sugar. The library currently has about 600
activities. A Sugar activity is intended to be self-contained (any
dependencies not satisfied by Sugar are to be incorporated in the
bundle). Naturally, an activity should work on any Sugar. However,
this situation is becoming very complicated. First, two of the XO
models (1 and 1.5) have Intel 32 bit architecture processors. The
others (1.75 and 4) have Arm processors. Some of the activities
incorporate binary modules which limit their use. The Sugar
community wishes to support Sugar on a range of platforms. For
mobile devices, Lionel Laske is developing Sugarizer. While
traditional activities were implemented in Python (with some binary
exceptions using Java or C), Sugarizer activities are written in
Javascript (HTML5 and CSS). Naturally a trend in modern computers is
to 64 bit architecture (AMD 64).<br>
<br>
The website itself is implemented in PhP and is patterned after the
Mozilla addons site. It has a repository of activity bundles (.xo
files) which is visible at <a class="m_-7838966876582265289moz-txt-link-freetext" href="http://download.sugarlabs.org" target="_blank">http://download.sugarlabs.org</a>. Each
activity has an 'add-on' id (4000-4999 at the moment). Versions of
activities are numbered beginning with 1 and incrementing by 1 with
subsequent versions. So the directories in ASLO contain bundles for
multiple bundles with the highest numbered version considered the
latest. In addition to the bundle, the site contains metadata which
is displayed in the pages devoted to an activity. I suspect this
metadata is stored in a database but I haven't investigated to find
out the details. <br>
<br>
In the meantime, Sugar Labs has decided to create a repository for
activities in github. The reasoning appears to be that this will
make it easier for the community to undertake ongoing development
and maintenance of these activities. Currently, the ASLO site has a
'developer hub' which allows registered users to add or update their
own activities. This function will need defined and moved to github.
<br>
<br>
How this will be done is a mystery to me. Logically, each of the
versions of an activity should be commited in git so that a
developer (or maintainer) can the changes made over time. Also, some
method is needed to manage over 600 additional repositories in the
Sugar Labs github. <br>
<br>
If you look at the ASLO site, it seems clear that the page needs to
specify more than which versions of Sugar are supported. It will
need to specify which models of the XO are supported. It will also
need to mention any restrictions on architecture or peripherals
needed for the users system (microphone, camera, network connection
- wired or wireless, and so on). <br>
<br>
Over time, Sugar has dropped many packages which were ordinarily
included. This has rendered many of the activities currently
unusable. For example, Sugar switched from a browser based on
hulahop to one based on WebKit. Some effort will be needed to update
activities using hulahop to use WebKit. Sugar Labs hopes that
activities will be ported to GTK3 (called sugar3) from the original
GTK (sugar). If this can be accomplished, the size and complexity of
Sugar can be significantly reduced. <br>
<br>
I hope you will consider this challenging and not discouraging.<br>
<br>
Just for further background. Many deployments I work with have no
access to the internet. To provide an alternative, I support a
school server which XO users can access by wifi in the classroom. My
hope is to provide a version of ASLO on the school server which will
give these users the ability to install any of the activities they
choose and for which their XO has storage capacity. That capability
exists now (and has for some years). However, the selection is
basically a list of activities by name and does not provide the
metadata descriptions found on the ASLO pages. My plan is to use
Django (which enables code to be in Python and not PhP). The school
server already provides sqllite, mariadb, and postgresql so db
support is readily available. Django is designed to support fusion -
creating web pages dynamically based on information from a db and so
should match the requirement. <br><span class="HOEnZb"><font color="#888888">
<br>
Tony <br></font></span><div><div class="h5">
<br>
<div class="m_-7838966876582265289moz-cite-prefix">On 04/01/2017 04:00 PM, Jatin Dhankhar
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Tony,
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">There are two major elements to
Sugar. The desktop interface - Sugar and the activities.
ASLO is a library of these activities. Build only applies to
Sugar. </span><br style="font-size:12.8px">
<br style="font-size:12.8px">
<span style="font-size:12.8px">For a non-XO version of Sugar,
there are two easy choices: SOAS and Sugar on Ubuntu. For
Ubuntu, install 14.04 or more recent version (I am using
16.04) and execute sudo apt-get install sucrose. For SOAS,
download the image and dd it to a usb stick. It works as a
livecd. </span></blockquote>
<div><br>
</div>
<div>Thank you for all the information :)</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="m_-7838966876582265289gmail-m_-7717984833789258641innerContainer" style="font-size:12.8px">
<div id="m_-7838966876582265289gmail-m_-7717984833789258641pageProduct" class="m_-7838966876582265289gmail-m_-7717984833789258641product m_-7838966876582265289gmail-m_-7717984833789258641full-product m_-7838966876582265289gmail-m_-7717984833789258641framed-box m_-7838966876582265289gmail-m_-7717984833789258641ebooks">
<div class="m_-7838966876582265289gmail-m_-7717984833789258641clearfix">
<div class="m_-7838966876582265289gmail-m_-7717984833789258641product-information"><cite>Make
Your Own Sugar Activities!</cite> <br>
<div class="m_-7838966876582265289gmail-m_-7717984833789258641author-info"><span class="m_-7838966876582265289gmail-m_-7717984833789258641authors"><a href="http://www.lulu.com/shop/search.ep?contributorId=739770" target="_blank">By <span class="m_-7838966876582265289gmail-m_-7717984833789258641author">James
Simmons</span></a></span></div>
</div>
</div>
</div>
</div>
<p style="font-size:12.8px">Make sure to get the second
edition.</p>
</blockquote>
<div>Specially the book, it's very detailed and comprehensive. </div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Another
alternative is to build the 'development environment'. This
environment is intended for developers who are working
directly on PRs for Sugar modules. </blockquote>
<div><br>
</div>
<div>Yes, I am looking to build the 'development environment',
specially the ASLO server but I am facing some issues. since
sphinx is very old and cannot be compiled (using make)
properly. Wanted to know if there is someone who maintains the
ASLO and can answer this specific query, related to building
ASLO locally and getting started on it</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Jatin Dhankhar</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Apr 1, 2017 at 6:31 AM, Tony
Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> Hi Jatin,<br>
<br>
There are two major elements to Sugar. The desktop
interface - Sugar and the activities. ASLO is a library
of these activities. Build only applies to Sugar. <br>
<br>
For a non-XO version of Sugar, there are two easy
choices: SOAS and Sugar on Ubuntu. For Ubuntu, install
14.04 or more recent version (I am using 16.04) and
execute sudo apt-get install sucrose. For SOAS, download
the image and dd it to a usb stick. It works as a
livecd. <br>
<br>
Another alternative is to build the 'development
environment'. This environment is intended for
developers who are working directly on PRs for Sugar
modules. <br>
<br>
In deploying Sugar, the only fully supported platform is
the XO. The Ubuntu Sugar appears not to connect to
networks and omits some of the essential activities.
These are the essential eight: Browse, Record, Jukebox,
Terminal, Log, Write, Read, and Image Viewer. Several of
these such as Record provide access to hardware features
of the platform such as the camera and microphone.
Naturally, these are more difficult to support on
general platforms. <br>
<br>
There are two programming environments for Sugar
activities: Python and Javascript. HelloWorld and
HelloWeb are simple examples of activities in Python and
Javascript, respectively. There is an excellent text
available for download online: <br>
<div class="m_-7838966876582265289gmail-m_-7717984833789258641innerContainer">
<div id="m_-7838966876582265289gmail-m_-7717984833789258641pageProduct" class="m_-7838966876582265289gmail-m_-7717984833789258641product m_-7838966876582265289gmail-m_-7717984833789258641full-product m_-7838966876582265289gmail-m_-7717984833789258641framed-box m_-7838966876582265289gmail-m_-7717984833789258641ebooks">
<div class="m_-7838966876582265289gmail-m_-7717984833789258641clearfix">
<div class="m_-7838966876582265289gmail-m_-7717984833789258641product-information">
<br>
<cite>Make Your Own Sugar Activities!</cite> <br>
<div class="m_-7838966876582265289gmail-m_-7717984833789258641author-info">
<span class="m_-7838966876582265289gmail-m_-7717984833789258641authors">
<a href="http://www.lulu.com/shop/search.ep?contributorId=739770" target="_blank">By <span class="m_-7838966876582265289gmail-m_-7717984833789258641author">James
Simmons</span></a> </span></div>
</div>
</div>
</div>
</div>
<p>Make sure to get the second edition. <br>
</p>
Tony<br>
<br>
<div class="m_-7838966876582265289gmail-m_-7717984833789258641moz-cite-prefix">On
04/01/2017 12:00 AM, <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:aslo-request@lists.sugarlabs.org" target="_blank">aslo-request@lists.sugarlabs.o<wbr>rg</a>
wrote:<br>
</div>
<blockquote type="cite">
<pre>Send ASLO mailing list submissions to
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:aslo@lists.sugarlabs.org" target="_blank">aslo@lists.sugarlabs.org</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/aslo" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/aslo</a>
or, via email, send a message with subject or body 'help' to
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:aslo-request@lists.sugarlabs.org" target="_blank">aslo-request@lists.sugarlabs.o<wbr>rg</a>
You can reach the person managing the list at
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:aslo-owner@lists.sugarlabs.org" target="_blank">aslo-owner@lists.sugarlabs.org</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ASLO digest..."
Today's Topics:
1. ASLO build and deployment process (Jatin Dhankhar)
------------------------------<wbr>------------------------------<wbr>----------
Message: 1
Date: Fri, 31 Mar 2017 16:57:58 +0530
From: Jatin Dhankhar <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-rfc2396E" href="mailto:dhankhar.jatin@gmail.com" target="_blank"><dhankhar.jatin@gmail.com></a>
To: <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:aslo@lists.sugarlabs.org" target="_blank">aslo@lists.sugarlabs.org</a>
Subject: [ASLO] ASLO build and deployment process
Message-ID:
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-rfc2396E" href="mailto:CAD+LdAF26TWi9uPP0pPZPTFWm3L5HF3=ubc4_TBY9O8v_e=T1Q@mail.gmail.com" target="_blank"><CAD+LdAF26TWi9uPP0pPZPTFWm3L5<wbr>HF3=ubc4_TBY9O8v_e=T1Q@mail.<wbr>gmail.com></a>
Content-Type: text/plain; charset="utf-8"
Hi,
I have few questions about how ASLO is actually build and deployed in
production. Build process is carried out by using Fabfile, I tried using
it and was not successful in building the sphinx ( since version used is
0.9.9.rc2 and current series is 2.x).
Relevant pull request and issue
PR -> <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-freetext" href="https://github.com/sugarlabs/aslo/pull/2" target="_blank">https://github.com/sugarlabs/a<wbr>slo/pull/2</a>
Issue -> <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-freetext" href="https://github.com/sugarlabs/aslo/issues/1" target="_blank">https://github.com/sugarlabs/a<wbr>slo/issues/1</a>
I am using Arch Linux and have installed all the necessary dependencies for
development including mysql and postgres development libraries along with
common development libraries. If anyone can point on how to successfully
build the project that would help a lot.
Some thread points out upgrading to new version of Sphinx but I wanted to
mirror the current instance.
Also project mentions something about Remora
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-freetext" href="https://wiki.mozilla.org/Update:Remora" target="_blank">https://wiki.mozilla.org/Updat<wbr>e:Remora</a> and wiki says it's no longer
maintained.
It quotes
</pre>
<blockquote type="cite">
<pre>Remora is no longer maintained. See AMO:Developers
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-rfc2396E" href="https://wiki.mozilla.org/AMO:Developers" target="_blank"><https://wiki.mozilla.org/AMO:<wbr>Developers></a>.
</pre>
</blockquote>
<pre>Also wanted to know more about how ASLO is deployed in production. What
techniques are used ? What are the pain points that need to be addressed
and tips on how to get started with it. If anyone is familiar with ASLO or
a long time maintainer, can they point out on how to reproduce a successful
build of ASLO (a documentation on how to run would be awesome)
Thanks,
Jatin Dhankhar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-rfc2396E" href="http://lists.sugarlabs.org/archive/aslo/attachments/20170331/12204ccc/attachment-0001.html" target="_blank"><http://lists.sugarlabs.org/ar<wbr>chive/aslo/attachments/2017033<wbr>1/12204ccc/attachment-0001.<wbr>html></a>
------------------------------
Subject: Digest Footer
______________________________<wbr>_________________
ASLO mailing list
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:ASLO@lists.sugarlabs.org" target="_blank">ASLO@lists.sugarlabs.org</a>
<a class="m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/aslo" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/aslo</a>
------------------------------
End of ASLO Digest, Vol 84, Issue 1
******************************<wbr>*****
</pre>
</blockquote>
</div>
______________________________<wbr>_________________
ASLO mailing list
<a href="mailto:ASLO@lists.sugarlabs.org" target="_blank">ASLO@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/aslo" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/aslo</a>
</blockquote></div>
</div></div>
</blockquote>
</div></div></div></blockquote></div><br></div>