<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"> "I am not in favor of creating repos
from the bundles as the git history is lost. "<br>
<br>
The point is that these bundles do not have a repository and hence
have no git history. <br>
<br>
'For example, when an activity is upgraded to GTK3, we add it to
GH/sugarlabs.'<br>
<br>
Currently about half of the activities do not work independent of
upgrade to GTK3. Many of these non-working activities can be fixed
with minor changes. <br>
To provide git history, the changes should be made through a git
repository. <br>
<br>
So I can give priority to making repositories for those bundles
with no repository and which do not work. Then use git to make a
history of the changes required to get them working. This will
require help from someone who can update the activities directory
in download.sugarlabs.org. <br>
<br>
So my question to James. What harm is done by making a repository
for an activity where there is none? <br>
<br>
Tony<br>
<br>
<br>
On 05/23/2017 08:59 AM, Walter Bender wrote:<br>
</div>
<blockquote
cite="mid:CADf7C8saC1M5o5pWVpo4nYxea++a9WaHBytEZEwrWVr+h+6xdA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, May 22, 2017 at 4:05 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">I
thought we were past this discussion. Walter has requested
the creation of repositories for activities for at least
two years. We devoted a full GCI opportunity to porting
activities to gtk3 and creating repositories for them. You
sound like you are still in fundamental disagreement with
this.<br>
</blockquote>
<div><br>
</div>
<div>Tony,</div>
<div><br>
</div>
<div>I think there is a bit of a miscommunication going on
here. First, as you know, I am not in favor of creating
repos from the bundles as the git history is lost. As far
as migrating repos, the idea, as James says, is to do that
as part of the maintenance process. For example, when an
activity is upgraded to GTK3, we add it to GH/sugarlabs.</div>
<div><br>
</div>
<div>-walter </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think a decision needs to be made. A lot of time and
effort (and discussion) has gone on based on the idea of
maintaining activities from repositories. If we continue
with the current use of bundles and metadata, a developer
will need to make a bundle from his repository and submit
it to the Developer Hub to be moderated before release on
ASLO. With the release the devloper will need to update
the metadata through the Developer Hub. If an activity is
taken over by a new developer, someone will need to enable
the devloper to get permission to submit the changes.<br>
<br>
My understanding remains that our goal is to have each
activity on ASLO be based on a repository (with a
back-link in <a moz-do-not-send="true"
href="http://activity.info" rel="noreferrer"
target="_blank">activity.info</a>).<br>
<br>
Let me ask the question this way, what's wrong with having
a repository for each activity and moving the metadata to
<a moz-do-not-send="true" href="http://activity.info"
rel="noreferrer" target="_blank">activity.info</a>?<span
class="HOEnZb"><font color="#888888"><br>
<br>
Tony</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 05/22/2017 03:19 PM, James Cameron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
That's no reason to create repositories.
Repositories should be<br>
created for source code development and maintenance,
and they do not<br>
need to be created until such time as development
and maintenance<br>
occurs.<br>
<br>
What's wrong with using the bundles and the existing
database of metadata?<br>
<br>
On Mon, May 22, 2017 at 02:46:25PM +0800, Tony
Anderson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Github is for developers and maintainers. This is
where repositories should<br>
be for activities, working or not. Making the
changes to get the activity to<br>
work are then documented and the activity can be
released for publishing in<br>
ASLO when ready.<br>
<br>
The purpose of the email was to determine if there
is a repository already<br>
which should be the basis for changes and to avoid
the firestorm of people<br>
fearing that their git history will be destroyed.
Of course, there is no<br>
real risk since a repository from the bundle
touches no one's repository.<br>
<br>
Tony<br>
<br>
On 05/22/2017 02:13 PM, James Cameron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Why create repositories? It seems a waste of
time.<br>
<br>
Instead, continue to use the bundles. There is
everything needed in<br>
the bundle for running the activity.<br>
<br>
Repositories should not be made for an activity
that does not work<br>
with the current verson of Sugar; the activity
should be ported first.<br>
<br>
</blockquote>
______________________________<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>
</blockquote>
</blockquote>
<br>
______________________________<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><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a moz-do-not-send="true"
href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</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>