<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I wish you would respond to my emails. Simply repeating this false
accusation is not helpful.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/23/2017 09:24 AM, Walter Bender
wrote:<br>
</div>
<blockquote
cite="mid:CADf7C8soSz+LriyVfbop8t6Rj_1Y8DWHRfXUubxfAAA_8O3x6w@mail.gmail.com"
type="cite">
<div dir="ltr">Tony,
<div><br>
</div>
<div>I can not speak for every contributor, but there is a lot
more to contributing to a project than the end result. Many
contributors take pride in their contributions and these days,
one's GitHub contributions have value in the job market. A
wholesale removal of the git history by Sugar Labs does not
send a very welcoming message to past or future contributors.
On a more mundane level, the lack of history means as a
developer I have no way of knowing whom to ask for help.</div>
<div><br>
</div>
<div>-walter</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Apr 22, 2017 at 9:17 PM, 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">
<div text="#000000" bgcolor="#FFFFFF"> The process for
installing repositories requires that the target
repository be empty. <br>
<br>
I would appreciate someone who could itemize what needs to
be in a repository such as the license, .gitignore,
README.md, and so on. Much of that can probably be done by
a script using the information available from ASLO.<br>
<br>
My sense is that PRs are appropriate for changes to an
activities functions (such as a port to gtk3) but not for
housekeeping.<span class="HOEnZb"><font color="#888888"><br>
<br>
Tony</font></span><span class=""><br>
<br>
<div class="m_8222172837798268816moz-cite-prefix">On
04/23/2017 07:27 AM, Love Mehta wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>There are many activities lacking a description
at <a moz-do-not-send="true"
class="m_8222172837798268816moz-txt-link-freetext"
href="https://github.com/sugar" target="_blank">https://github.com/sugar</a>-activ<wbr>ities/
and it is hard to know the name and purpose of the
activity specially in the web activities where one
has to open the index.html file. I think we should
add the descriptions from <a
moz-do-not-send="true"
class="m_8222172837798268816moz-txt-link-freetext"
href="https://activities.sugarlabs"
target="_blank"><a class="moz-txt-link-freetext" href="https://activities.sugarlabs">https://activities.sugarlabs</a></a>.o<wbr>rg
for each activity to the readme markdown file. I
thought of doing this but this will lead to a
large number of pull requests. Should I go ahead
with it?<br>
</div>
</div>
</blockquote>
<br>
</span></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>
<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>