Hi Walter,
On github as far as I can tell, the developer is only acknowledged as a
contributor. So the loss of this information seems a byproduct of the
move to github. I would appreciate advice as how the developer can be
promoted short of them becoming a contributor and making some update to
an activity.
Tony
On 04/23/2017 09:24 AM, Walter Bender wrote:
Tony,
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.
-walter
On Sat, Apr 22, 2017 at 9:17 PM, Tony Anderson <tony_ander...@usa.net
<mailto:tony_ander...@usa.net>> wrote:
The process for installing repositories requires that the target
repository be empty.
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.
My sense is that PRs are appropriate for changes to an activities
functions (such as a port to gtk3) but not for housekeeping.
Tony
On 04/23/2017 07:27 AM, Love Mehta wrote:
There are many activities lacking a description at
https://github.com/sugar-activities/ 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 https://activities.sugarlabs.org 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?
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
