<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I read the log and didn't see any discussion of either an
activity server or a WikiPort. Most of the discussion seems to
focus on 'activity.info'. <br>
</p>
<p>I interpret <a class="moz-txt-link-freetext" href="https://github.com/sugar-activities">https://github.com/sugar-activities</a> as an attempt to
provide a separate place for Sugar activity repositories based on
download.sugarlabs.org/activities. The number of activities
mentioned is consistent with the current content of ASLO. (see
<a class="moz-txt-link-freetext" href="http://activities.sugarlabs.org/activities/">http://activities.sugarlabs.org/activities/</a>)<br>
</p>
<p>A simple python script can process the activity.info in activity
bundles very quickly. Simply download every activity bundle and
then use import zipfile to read the activity.info file and check
it for whatever is interesting. I generally use ls -1 *.xo >
list to create a file. The python script can easily form a list of
activities from this file. <br>
</p>
<p>Our primary goal must be to provide information and support for
our users and prospective users. There is no reason for a user
ever to know that there is an activity.info file or indeed an
Activities folder. The original design provides the information
needed for Sugar to register and execute the activity within the
activity.py framework. In this spirit, the repository link should
join the website link on ASLO where it is visible to the user. <br>
</p>
<p>In the spirit of view source, wouldn't it be helpful to have
documentation giving the user a map of Sugar and the role of the
various modules? This could start with the information in
activity.py.
(/usr/lib/python2.7/site-packages/sugar3/activity/activity.py).
This could lead in to James Simmons description of how to make a
Sugar activity. The Hello World activity could be used as intended
- as the simplest example. The problem with the wiki pages is not
the mark up method but the organization and content.<br>
</p>
<p>Our priority task is to clean up ASLO. The activity version in
ASLO needs to be released from the github repository with a
meaningful version number (an integer not a real number). The
activities need to be tested to see that they work in the Ubuntu
18.04 environment as well as in 13.2.9. We need to have a clear
picture of the activities which are not working and the cause. It
may be necessary to have different versions for Ubuntu and for
13.2.9. As well there may have to be different versions for the
Intel processors and the Arm processors. ASLO needs to be modified
to accommodate that need. There are activities which probably
should be dropped. The Java activity works well but is not an
activity. It installs Java - a one-time execution. <br>
</p>
<p>We also need to remember that the XO has very limited storage. It
is essential that the installed activity not be git enabled.
Currently the Browse activity not only downloads and installs an
activity, it leaves a copy of the bundle in the Journal. This
doubles the storage cost of an activity. It burdens our user with
the need to switch to the Journal and erase the bundle. As
developers we need to ask what is the effect a proposed change
have on the size of the installed activity. Currently 13.2.9
installed on an XO-1 or on a 2GB XO-1.5 gives the user about 300MB
of available storage.</p>
<p>Tony<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On Monday, 07 May, 2018 02:42 AM, Vipul
Gupta wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALRDm=vHuMdA5CuvHpVWzbtPwM1Pj0sba9HSJ82-wF_UG5Kq7Q@mail.gmail.com">
<div dir="ltr">Hi folks,
<div><br>
</div>
<div>We are just done with our second meeting, of the project
Setting up the activity server and WikiPort. Do refer to the
logs for the updates, all comments and suggestions are
appreciated. The blog with the updates is going to be uploaded
soon on my blog Mixster.</div>
<div> <br>
<b>Logs are here</b> - <a
href="http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-06T16:43:50"
moz-do-not-send="true">http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-06T16:43:50</a><br
clear="all">
<div><b>Tracker (updated)</b> - <a
href="https://docs.google.com/document/d/1VdzjA-DnEBh0ntHY17ktXlp7c2pIofq8458gSCTwiSM/edit?usp=sharing"
moz-do-not-send="true">https://docs.google.com/document/d/1VdzjA-DnEBh0ntHY17ktXlp7c2pIofq8458gSCTwiSM/edit?usp=sharing</a></div>
<div><br>
</div>
<div>Happy Contributing !!</div>
<br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div><font size="1">Cordially, </font></div>
<div><font size="1">Vipul Gupta </font></div>
<div><font size="1"><a
href="https://mixstersite.wordpress.com/"
style="color:rgb(17,85,204)"
target="_blank" moz-do-not-send="true">Mixster</a> | <a
href="https://github.com/vipulgupta2048" style="color:rgb(17,85,204)"
target="_blank" moz-do-not-send="true">Github</a></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>