<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">You are correct, about 75% of the
activities on ASLO have identified repositories. Interestingly,
there are 250 repositories on git.sugarlabs.org <br>
which may be activity projects with no corresponding bundle on
ASLO. <br>
<br>
I reviewed the Pootle list yesterday and recorded the url to each
repository in the spreadsheet.<br>
<br>
So the question is, when to go for the last resort? No harm is
done by creating a repository from the bundle. <br>
<br>
Since I am traveling in the next two weeks, I doubt there will be
time to work on this until after that. If the community wishes I
can then create a wiki page with the list of these orphans. It
would be essentially the list of 224 minus about 20 where
repositories have been identified by you and others.<br>
<br>
Tony<br>
<br>
<br>
On 05/24/2017 06:06 PM, Gonzalo Odiard wrote:<br>
</div>
<blockquote
cite="mid:CAJ+iPVQ2K3vzDf9diHBPJyzyt6YtoZz2xGpQOYYBi3AXF6F85w@mail.gmail.com"
type="cite">
<div dir="ltr">Most activities certainly had a repository.
<div>I fully agree with creating repositories from bundles only
as a last resource.</div>
<div>Probably is better create a wiki page based in the Pootle
page and add all the project without a known repository,</div>
<div>and other can help to find the most updated repository.</div>
<div><br>
</div>
<div>Gonzalo</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, May 24, 2017 at 6:22 AM, Tony
Anderson <span dir="ltr"><<a moz-do-not-send="true"
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">You repeat
that a repository exists before an activity bundle. I have
listed 200 activities (about 25%) of the activities<br>
on ASLO that probably do not have one. Further, if the
repository cannot be found - we need to go ahead with what
we have.<br>
No matter how the working directory is created, git init
should be applied to create a repository and subsequent
changes documented.<br>
<br>
If there is a problem with an activity, the github
repository should have an issue documenting the problem
pending finding the resources to fix it.<span class="HOEnZb"><font
color="#888888"><br>
<br>
Tony</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
On 05/24/2017 02:29 PM, James Cameron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, May 23, 2017 at 11:23:25AM +0800, Tony
Anderson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, James<br>
<br>
Thank for these details. I am trying to find out
what the standards<br>
are for these repositories.<br>
<br>
Tony Forster contacted me by private email to let me
know that<br>
textdungeon did not have a repository. Version 4 is
version 3 with<br>
the removal of<br>
<br>
import simplejson<br>
<br>
which causes an activity to fail with python 2.7.<br>
</blockquote>
Both of these pieces of information should be in the
commits; please<br>
rewrite them.<br>
<br>
Also, it should not be marked version 4 until you are
ready to do the<br>
later steps in the role of activity maintainer; tag a
release, make a<br>
bundle, and upload to ASLO. As it stands now, there
is no version 4<br>
bundle in ASLO, yet the repository contains a version
4.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
In summary, in making a repository:<br>
<br>
* the commits need<br>
--author<br>
--date<br>
--compiled files such as .pyc should be
deleted<br>
*git history should show each available
version when created<br>
from a bundle<br>
*delete MANIFEST<br>
</blockquote>
The delete of MANIFEST and the GTK+ 3 porting should
be commits made<br>
after the commit of the latest ASLO version; not
including any later<br>
version you release from git.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
*add a .gitignore file (I understand this to
be the same for all<br>
activities)<br>
</blockquote>
No, it won't be the same. It may have some patterns
that are common.<br>
It should have patterns for any files that may be
created by running<br>
or building the source.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Regarding thoughts:<br>
b) how is an installed activity to work
without these files<br>
in the bundle? How is source code for object files
kept in the<br>
repository (e.g. box2d)?<br>
</blockquote>
It will work mysteriously. How and where source code
is kept is up to<br>
the activity author. My point is that you cannot
trust the activity<br>
author to have included source, and so a git
repository built from the<br>
bundle may end up being less useful for source control
purposes.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
c) this is the goal. However, how do you do
this for an<br>
activity for which there is no repository?<br>
</blockquote>
Do this carefully and with the appropriate social
license; as part of<br>
taking on activity maintenance role for an activity.<br>
<br>
What Walter said, I agree with; paraphrasing now;
creating a<br>
repository from a bundle is a last resort action deep
inside a long<br>
process of maintaining an activity, which also
includes upgrading it<br>
to GTK+ 3, testing, and making a release.<br>
<br>
It isn't something to do first on <a
moz-do-not-send="true"
href="http://github.com/sugarlabs" rel="noreferrer"
target="_blank">github.com/sugarlabs</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
d) I don't understand you here. Any
developers will see an<br>
activity with a link to a repository. How is that
confusing?<br>
</blockquote>
Because the repository was built from the bundle,
instead of the<br>
bundle built from the repository.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
e) A repository provides a standard way to
document problems<br>
that prevent the activity from working. Many
activities in github<br>
may not work at a given time in the development,
maintenance<br>
cycle. This has no effect until the bundle is
released to ASLO. We<br>
have a fact that there are many (about one-half)
bundles in ASLO<br>
that do not work. The best I can do is test and
write an issue as to<br>
why they don't work. As volunteers get time, they
can address the<br>
issues.<br>
</blockquote>
Where standard ways to document problems go against
code quality and<br>
maintenance in the project as a whole, then the latter
should win.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I am not a 'maintainer' on ASLO. This
permission would be<br>
helpful.<br>
</blockquote>
I was speaking of being an activity maintainer, rather
than only<br>
developer status on <a moz-do-not-send="true"
href="http://activities.sugarlabs.org"
rel="noreferrer" target="_blank">activities.sugarlabs.org</a>.<br>
<br>
The role of an activity maintainer is to accept
changes from others,<br>
test the activity, iterate with fixes, update version,
tag a release,<br>
make a bundle, upload to ASLO, upload to <a
moz-do-not-send="true"
href="http://download.sugarlabs.org"
rel="noreferrer" target="_blank">download.sugarlabs.org</a>,
and<br>
field any questions that arise.<br>
<br>
I'd like to assess your capability in all those steps
before giving<br>
you any additional permissions on ASLO. On the other
hand, I can't<br>
give you any additional permissions on ASLO because I
don't have them<br>
myself. I'm not the one to convince on that.<br>
<br>
</blockquote>
<br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org"
target="_blank">Sugar-devel@lists.sugarlabs.or<wbr>g</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/sugar-devel</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<table
style="color:rgb(136,136,136);font-size:12.8px;font-family:'Times
New Roman';width:470px" width="470" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr valign="top">
<td
style="padding-left:10px;width:10px;padding-right:10px"><img
moz-do-not-send="true"
src="https://s3.amazonaws.com/ucwebapp.wisestamp.com/a2cdffca-bc96-4966-b4fa-c3fa79edb131/12112365_414949315381645_4106803690337175030_n.format_png.resize_120x.png"
alt="photo"
style="border-radius:4px;width:65px;max-width:120px"
height=" " width="65"></td>
<td
style="border-right-width:0px;border-right-style:solid;border-right-color:rgb(69,102,142)"><br>
</td>
<td
style="font-family:Arial;text-align:initial;font-stretch:normal;font-size:14px;padding:0px
10px">
<div style="color:rgb(100,100,100)"><b>Gonzalo
Odiard</b><br>
Lider de proyecto</div>
<div style="font-size:13px;padding:5px 0px"><a
moz-do-not-send="true"
href="tel:tel.:+4210-7748"
style="color:rgb(141,141,141);text-decoration:none"
target="_blank">tel.: </a><span
style="font-family:arial,sans-serif;font-size:small;background-color:rgb(255,255,255)"><font
color="#666666">2081-6424 y 2082-0312</font></span><font
color="#8d8d8d"> | </font><span
style="color:rgb(141,141,141);text-align:initial;white-space:nowrap;display:inline-block"><a
moz-do-not-send="true"
href="http://www.trinom.io/"
style="color:rgb(141,141,141);text-decoration:none"
target="_blank"><a class="moz-txt-link-abbreviated" href="http://www.trinom.io">www.trinom.io</a></a></span><span
style="color:rgb(141,141,141);text-align:initial"> </span><span
style="color:rgb(141,141,141);text-align:initial"> </span><span
style="color:rgb(141,141,141);text-align:initial"> </span><span
style="color:rgb(69,102,142);text-align:initial;display:inline-block"></span><span
style="color:rgb(141,141,141);text-align:initial"> </span><span
style="color:rgb(141,141,141);text-align:initial;display:inline-block">Av
Calchaqui 4936· 2do Piso. Quilmes</span></div>
<div
style="color:rgb(100,100,100);margin-top:5px"><a
moz-do-not-send="true"
href="http://www.facebook.com/trinomiosrl"
target="_blank"><img
moz-do-not-send="true"
src="https://s3.amazonaws.com/images.wisestamp.com/icons_32/facebook.png"
style="border-radius:0px;border:0px;width:16px" width="16"></a> <a
moz-do-not-send="true"
href="https://www.linkedin.com/company/trinom-io"
target="_blank"><img
moz-do-not-send="true"
src="https://s3.amazonaws.com/images.wisestamp.com/icons_32/linkedin.png"
alt=""
style="border-radius:0px;border:0px;width:16px"
width="16"></a></div>
<div style="color:rgb(100,100,100)"><br>
</div>
</td>
</tr>
</tbody>
</table>
</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>