<div dir="ltr">Hi,<div><br></div><div>I am setting up Django now and going through some tutorials. I will setup the code with a very basic and barebones version of what we want to achieve and put it in a private repo. We can even host it online, since I have some DigitalOcean credit left. Will keep you posted. </div><div><br></div><div>Thanks.</div><div>Jatin Dhankhar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 6, 2017 at 7:11 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi, Jatin<br>
<br>
In setting up Django, I think you will do it on your computer not on
a separate server. Django handles that through its own server and
has sgqlite as a database built-in. A good first start would be to
set up the tutorial app (<a class="m_6069057648541672779moz-txt-link-freetext" href="https://www.djangoproject.com/" target="_blank">https://www.djangoproject.<wbr>com/</a>).
Essentially you will need to install django and then set up the
tutorial app 'poll'. Working through this tutorial will help a lot
later on. The key point is that after initial setup, there are three
important elements: url.py which defines the urls to access the
application, views.py which is the python code that responds to a
request by accessing the db and delivering the relevant information
to a template. The template is an html file with variables of the
form {{ <a href="http://activity.name" target="_blank">activity.name</a> }} transferring information from the view to
the template.<br>
<br>
What I have is an application: aslo. Once you have Django installed
and have run the tutorial app through Django's server, you'll be
ready. Essentially, you will only need to add aslo as a second app
in the settings. One possible confusion is that DJango lives in a
project - essentially a directory containing its manage.py admin
interface. In the directory is another directory of the same name
with the settings.py and url.py. The poll app is a directory in the
top-level alongside the inner directory with the project name.<br>
<br>
For example, my project is schoolsite. So my setup looks like:<br>
<br>
/library/schoolsite/schoolsite<br>
/library/schoolsite/aslo<br>
<br>
Meanwhile my code links directly to an activity page with no index.
I'll add an index so the essential structure will be there. I'll
also include the 'fixtures' to set up a 25 activity capability.
Fixtures are csv files from which the database (metadata) can be
loaded. <br><span class="HOEnZb"><font color="#888888">
<br>
Tony</font></span><div><div class="h5"><br>
<br>
<div class="m_6069057648541672779moz-cite-prefix">On 04/06/2017 03:22 AM, Jatin Dhankhar
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Tony,
<div>Hope you had a nice trip/travel.</div>
<div>Sugar labs is really awesome and good looking, but I
presume it's still under development, login and sign up
section is a placeholder. </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">Your example has each activity
occupying a large part of the screen, my current
implementation shows the activities about like an ls
listing. Sugar network is a compromise between. </span></blockquote>
<div>Sorry to ask, but which example ? We can work with someone
from the design team and go through some mockups to decide,
but we can do it later, since frontend should be easy to
modify/</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">One part of the challenge is that
we want an interface which is easy for school children to
use (generally with minimal English literacy). This is the
basis for an emphasis on icons. </span></blockquote>
<div>Yes this should be enforced as part of guideline, all the
way down to the activity itself (I see some popular activities
lean heavy on icons) </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 want to get your feet wet, I
can send you the current django code and we could work
together in adding capabilities - step by step</span></blockquote>
<div>Yes, count me in. </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"> So there are three strategies. One
is to download the </span><a href="http://download.sugarlabs.org/" style="font-size:12.8px" target="_blank">download.sugarlabs.org</a><span style="font-size:12.8px"> <wbr>repository (it should be open to
anonymous ftp). The second is to take only the current
working activities (I am guessing about 200-300 to start).
But I would recommend a selection of 25 or so that you can
use to test the code. </span></blockquote>
<div>Third approach is fine by me. First approach would include
all activities,including those which are incompatible. </div>
<div><br>
</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">This is handled by a Pull Request
system. Essentially, there is a select team that merges PRs
into the git commits. So I anticipate that this team would
'release' updated or new activities into the 'master' branch
and then deploy them to ASLO.</span></blockquote>
<div>Yes, we can add a bot in between which would
pre-process/test activity once it's been merged and generate a
new ASLO activity index (not necessary at such an early
stage.)</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 Wed, Apr 5, 2017 at 3:17 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>
Sorry, I was traveling and did not have access to the
internet. I made some comments below. <br>
<br>
One alternative format to ASLO is sugar-network (<a class="m_6069057648541672779m_-7168158273221375910moz-txt-link-freetext" href="http://school-network.org/hub/?view=Catalog&workspace=activity&tab=toprated" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-freetext" href="http://school-network.org/" target="_blank">http://school-network.org/</a>hub<wbr>/?view=Catalog&workspace=activ<wbr>ity&tab=toprated).
I see this as the top-level page (here all activities
could be seen by scrolling). I would see this page as
allowing the user to input one or more tags and see a page
in the same format with just those activities with the
tag. <br>
<br>
A click on an activity would open the second-level (one
activity per page) with the full metadata and the download
link. <br>
<br>
Your example has each activity occupying a large part of
the screen, my current implementation shows the activities
about like an ls listing. Sugar network is a compromise
between. <br>
<br>
One part of the challenge is that we want an interface
which is easy for school children to use (generally with
minimal English literacy). This is the basis for an
emphasis on icons. So rather than describing activities,
there should be an attractive background image that gives
a clue as the the nature of the activity. So, ideally
descriptions should be localizable. <br>
<br>
If you want to get your feet wet, I can send you the
current django code and we could work together in adding
capabilities - step by step. I am reviewing the ASLO
library to see which activities work with the current
release of Sugar (about two out of three so far). I hope
to finish the first pass tomorrow. So there are three
strategies. One is to download the <a href="http://download.sugarlabs.org" target="_blank">download.sugarlabs.org</a>
repository (it should be open to anonymous ftp). The
second is to take only the current working activities (I
am guessing about 200-300 to start). But I would recommend
a selection of 25 or so that you can use to test the code.
We can always add the rest as needed (probably to set up
an online site: <a href="http://activities3.sugarlabs.org" target="_blank">activities3.sugarlabs.org</a>.
I recommend this approach because we can put the project
on Github/Sugar Labs and can deploy the project on the
same Sugar Labs server as ASLO (make turnover easy). <br>
<br>
Tony<span><br>
<br>
<br>
<div class="m_6069057648541672779m_-7168158273221375910moz-cite-prefix">On
04/05/2017 02:41 PM, Jatin Dhankhar wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,<br>
Where should I start? Should I start working on the
new ASLO ?</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Thanks,</div>
<div>Jatin Dhankhar</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Apr 2, 2017 at 4:28
PM, Jatin Dhankhar <span dir="ltr"><<a href="mailto:dhankhar.jatin@gmail.com" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-abbreviated" href="mailto:dhankhar.jatin@gmail.com" target="_blank">dhankhar.jatin@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Tony,
<div><br>
</div>
<div>Based on our suggestions I updated the
proposal, thanks a lot for your inputs. <a href="https://docs.google.com/document/d/1wECi_gtxyar3MWbC8ly6bjdW8SSLYe5YNcXPiTUUlkg/edit?usp=sharing" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-freetext" href="https://docs.google.co" target="_blank">https://docs.google.co</a><wbr>m/document/d/1wECi_gtxyar3MWbC<wbr>8ly6bjdW8SSLYe5YNcXPiTUUlkg/ed<wbr>it?usp=sharing</div>
<span>
<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 new
version assume the master source
repository is github and that bundles
are installed and updated via setup.py
from github</span><br style="font-size:12.8px">
<span style="font-size:12.8px">
(the build and deployment
methodologies). This means the new
system does not need to implement the
Developer Hub. </span></blockquote>
</span>
<div>That seems a nice idea but won't there be
need for moderation/approval of activities.
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</span> This is handled by a Pull Request system.
Essentially, there is a select team that merges PRs into
the git commits. So I anticipate that this team would
'release' updated or new activities into the 'master'
branch and then deploy them to ASLO. <br>
<div>
<div class="m_6069057648541672779h5">
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><span>
<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 id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033gmail-m_3726298898718276124docs-internal-guid-193d56a3-2cc4-41b7-f40b-f4fc11973a5e" style="font-size:12.8px"><span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033gmail-m_3726298898718276124docs-internal-guid-193d56a3-2cc4-8575-861e-4acc7fc20da8">Add
recommendation engine</span></span><span style="font-size:12.8px"> - I think
this is a distraction. How can a
program know the interests and needs
of a user to provide a useful
recommendation? I also think the
Review system is a distraction. The
problem is that no reviews come from
actual users of the activities but are
similar to the sponsored reviews at
Amazon. A better approach would be to
strengthen the
tags/collections/category system.</span></blockquote>
</span>
<div>This can be useful if we want to show
user, programs similar to what user
already installed or suggestions based on
what users installed along with following
app but that is quite a work, we need to
add analytics and stuff.
Tags/collections/category is a simple way
to achieve this nicely.</div>
<span>
<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 id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033gmail-m_3726298898718276124docs-internal-guid-193d56a3-2cc3-cf4b-5d34-cb59074d105d" style="font-size:12.8px">Improve
look/theme of ASLO</span><span style="font-size:12.8px"> - Naturally,
this should be done in the context of
the project. </span><span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033gmail-m_3726298898718276124docs-internal-guid-193d56a3-2cc3-cf4b-5d34-cb59074d105d" style="font-size:12.8px"> </span></blockquote>
</span>
<div>Yes, I am looking at <a href="http://beautifulopen.com" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-freetext" href="http://beautifulopen.com" target="_blank">http://beautifulopen.com</a>,
for awesome examples. I am liking these
so far <a class="m_6069057648541672779m_-7168158273221375910moz-txt-link-freetext" href="http://rouge.jneen.net/" target="_blank">http://rouge.jneen.net/</a> an<wbr>d <a class="m_6069057648541672779m_-7168158273221375910moz-txt-link-freetext" href="http://www.gnu.org/" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-freetext" href="http://www.gnu.org/" target="_blank">http://www.gnu.org/</a>software/<wbr>guile/.<br>
</div>
<div><br>
</div>
<div>I want to get started with discussion
of potential design and tools for
deploying activities. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>Jatin Dhankhar</div>
</div>
<div class="m_6069057648541672779m_-7168158273221375910HOEnZb">
<div class="m_6069057648541672779m_-7168158273221375910h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Apr 2,
2017 at 9:58 AM, Tony Anderson <span dir="ltr"><<a class="m_6069057648541672779m_-7168158273221375910moz-txt-link-abbreviated" href="mailto:tony_anderson@usa.net" target="_blank"></a><a class="m_6069057648541672779moz-txt-link-abbreviated" 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 most important thing to keep
in mind is that ASLO manages a
library of independent programs
(Sugar activities). These are
updated asynchronously from the
Sugar releases. Sugar is in
desperate need of build management
- as best I can tell at the moment
we have none. However, this
problem does not directly apply to
the activities. <br>
<br>
The 'build' process for the
activities is accomplished by
'python setup.py dist_xo' executed
in the bundle root. The generated
xo file is then 'deployed' to the
appropriate directory in <a href="http://download.sugarlabs.org" target="_blank">download.sugarlabs.org</a>
as the latest version. <br>
<br>
<br>
Since development time in GSOC is
limited, it is critical to define
a doable project. In my experience
proposals set unachievable
expectations and result in
partially complete and
disappointing results. <br>
<br>
<span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc3-cf4b-5d34-cb59074d105d">Improve
look/theme of ASLO</span> -
Naturally, this should be done in
the context of the project. <span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc3-cf4b-5d34-cb59074d105d">
</span><br>
<span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc4-41b7-f40b-f4fc11973a5e"><br>
Maintain ASLO</span> - I am
proposing that this project build
a replacement for ASLO which can
be used immediately offline by
school servers. During the GSOC
period, the community should be
expected to judge whether the
development forms a base for
future replacement of ASLO. <br>
<span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc4-41b7-f40b-f4fc11973a5e">
</span>
<p><span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc4-41b7-f40b-f4fc11973a5e"><span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc4-8575-861e-4acc7fc20da8">Add
recommendation engine</span></span>
- I think this is a distraction.
How can a program know the
interests and needs of a user to
provide a useful recommendation?
I also think the Review system
is a distraction. The problem is
that no reviews come from actual
users of the activities but are
similar to the sponsored reviews
at Amazon. A better approach
would be to strengthen the
tags/collections/category
system. <br>
</p>
<p><span id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124docs-internal-guid-193d56a3-2cc4-f548-de81-7ce94367e330">Improve
Transactional emails</span> -
I think this is also a
distraction. The user
communication is clicks on
links. The response is public. <br>
</p>
So I would propose something like:<br>
<br>
- develop a new ASLO as <a href="http://activities3.sugarlabs.org" target="_blank">activities3.sugarlabs.org</a>
based on Django (to this end I can
supply my current minimal working
version).<br>
<br>
- the new version assume
the master source repository is
github and that bundles are
installed and updated via setup.py
from github<br>
(the build and
deployment methodologies). This
means the new system does not need
to implement the Developer Hub. <br>
<br>
- the core activities
(Journal, Record, Log, Terminal,
Write, Jukebox, Image Viewer,
Browse, and Read) be excluded from
ASLO and handled through the
Sugar release cycle).
These activities are installed in
a Sugar release and the ability to
erase them is disabled. <br>
<br>
- for simplicity, the
initial version could be limited
to two templates: an index page
showing icons and names of
activities and a page per activity
with the download button.<br>
<br>
- There should be a simple
and transparent 'CRUD' capability
for the metadata - perhaps in the
first commit based on Django's
admin feature. I think the first
commit db could consist of a
single table: one row per
activity. <br>
<br>
- Do whatever can be done
to improve the attractiveness of
the site.<br>
<br>
- Do not base development
on emulation of any other project:
Mozilla add-ons or Play Store or
.... Certainly the project can and
should be take inspiration
from any source. However,
it will be enough to attempt to
provide the essential current
functionality of ASLO. <br>
<br>
What I visualize is the project be
installed on github at the point
of a first working commit. The
project could then be installed as
<a href="http://activities3.sugarlabs.org" target="_blank">activities3.sugarlabs.org</a>
for community testing and advice.
Development would be using git
locally using localhost or a local
server. Commits would be pushed to
GitHub at appropriate points in
the development and the resulting
version would then be used to
update the online version. The
project would work with the
current <a href="http://download.sugarlabs.org" target="_blank">download.sugarlabs.org</a>
as the source of bundles.
(therefore, keeping the addition
of activities to GitHub as a
separate project). <br>
<br>
Keep in mind, I am speaking for
myself. While, if your project
were selected, I would probably be
a mentor - this gives me no
special voice in the selection.
Normally we have several proposals
for each available slot and many
worthy proposals are not selected.
<br>
<span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033HOEnZb"><font color="#888888"> <br>
Tony</font></span>
<div>
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033h5"><br>
<br>
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-cite-prefix">On
04/01/2017 09:29 PM, Jatin
Dhankhar wrote:<br>
</div>
<blockquote type="cite">
<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" target="_blank">http://wiki.mozilla.org<wbr>/Update:Remora</a> )
which old and deprecated now in favor of AMO (<a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-txt-link-freetext" href="https://wiki.mozilla.org/AMO:Developers" target="_blank">https://wiki.mozilla.org/AMO:<wbr>Developers</a>)
.</div>
<div>
</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>
</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/" target="_blank">http://open.qa/</a>) for more
comprehensive suite. </div>
<div>
</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>
</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>
</div>
<div>Yes more like a Manifest, similar to what Play Stores does
for Android. </div>
<div>
</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>
</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">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>
</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.
</div>
<div>
</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 class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-txt-link-freetext" href="https://docs.google.com/document/d/1wECi_gtxyar3MWbC8ly6bjdW8SSLYe5YNcXPiTUUlkg/edit?usp=sharing" target="_blank">https://docs.google.com/d<wbr>ocument/d/1wECi_gtxyar3MWbC8ly<wbr>6bjdW8SSLYe5YNcXPiTUUlkg/edit?<wbr>usp=sharing</a></div>
<div>
</div>
<div>
</div>
<div>Thanks,</div>
<div>Jatin Dhankhar</div>
</div>
<div class="gmail_extra">
<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:
<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
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).
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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-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.
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.
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.
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).
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.
I hope you will consider this challenging and not
discouraging.
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.
<span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124HOEnZb"><font color="#888888">
Tony
</font></span>
<div>
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124h5">
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289moz-cite-prefix">On
04/01/2017 04:00 PM, Jatin Dhankhar wrote:
</div>
<blockquote type="cite">
<div dir="ltr">Hi Tony,
<div>
</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>
<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>
</div>
<div>Thank you for all the information :)</div>
<div>
</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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641innerContainer" style="font-size:12.8px">
<div id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641pageProduct" class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641product m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641full-product m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641framed-box
m_-7838966876582265289gmail-m_-7717984833789258641ebooks">
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641clearfix">
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641product-information"><cite>Make
Your Own Sugar Activities!</cite>
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641author-info"><span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641authors"><a href="http://www.lulu.com/shop/search.ep?contributorId=739770" target="_blank">By <span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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>
</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>
</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>
</div>
<div>Thanks,</div>
<div>Jatin Dhankhar</div>
<div class="gmail_extra">
<div class="gmail_quote">On Sat, Apr 1, 2017 at
6:31 AM, Tony Anderson <span dir="ltr"><<a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-txt-link-abbreviated" href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:
<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,
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.
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.
Another alternative is to build the
'development environment'. This
environment is intended for developers who
are working directly on PRs for Sugar
modules.
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.
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:
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641innerContainer">
<div id="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641pageProduct" class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641product m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641full-product m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641framed-box
m_-7838966876582265289gmail-m_-7717984833789258641ebooks">
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641clearfix">
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641product-information">
<cite>Make Your Own Sugar
Activities!</cite>
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641author-info">
<span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641authors">
<a href="http://www.lulu.com/shop/search.ep?contributorId=739770" target="_blank">By <span class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641author">James
Simmons</span></a> </span></div>
</div>
</div>
</div>
</div>
<p>Make sure to get the second edition.
</p>
Tony
<div class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641moz-cite-prefix">On
04/01/2017 12:00 AM, <a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124moz-txt-link-abbreviated" href="mailto:aslo-request@lists.sugarlabs.o" target="_blank">aslo-request@lists.sugarlabs.o</a><wbr>rg
wrote:
</div>
<blockquote type="cite">
<pre>Send ASLO mailing list submissions to
<a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-rfc2396E" href="mailto:dhankhar.jatin@gmail.com" target="_blank"><dhankhar.jatin@gmail.com></a>
To: <a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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.gm<wbr>ail.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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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.htm<wbr>l></a>
------------------------------
Subject: Digest Footer
______________________________<wbr>_________________
ASLO mailing list
<a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-7838966876582265289gmail-m_-7717984833789258641moz-txt-link-abbreviated" href="mailto:ASLO@lists.sugarlabs.org" target="_blank">ASLO@lists.sugarlabs.org</a>
<a class="m_6069057648541672779m_-7168158273221375910m_3798839159488843033m_3726298898718276124m_-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>
</div>
</blockquote>
</div></div></div></blockquote></div>
</div>
</div></div></blockquote></div>
</div>
</blockquote>
</div></div></div></blockquote></div>
</div>
</blockquote>
</div></div></div></blockquote></div><br></div>