Hyrum K. Wright wrote:
> I propose that we remove the contrib/ directory from our repository,
> and from our distribution. A couple of reasons for this:
>
> * Some of the scripts have licensing issues.
>
> * We don't even keep the webpage claiming to describe these tools up-
> to-date.
>
> * We don't claim to support them, yet they are hosted and shipped by
> the project. (In the early days of the project, it was useful to give
> these unsupported scripts a place to host and a way to ship. With the
> ubiquity of Subversion, and the availability of external hosting
> sites, we should get out the business of providing project hosting for
> these scripts.)
>
> Thoughts?
First, we shouldn't just talk about removing, but where to move it to. Removing
it without finding a new location for it is a disservice to the svn community.
We don't know how many of the scripts get used, so I don't want to delete them.
Also, I don't think we should just blow all the little scripts to the wind,
there's value in having them all in one spot. Do I want to host a whole project
for this single GPL script at some other repo, no, not really:
http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn_export_empty_files.py
So let's move contrib as a whole somewhere, such as
- up out of trunk into http://svn.collab.net/repos/contrib
- into a new Google Code project, say called svn-contrib or svn-scripts
svnmerge.py deserves to be in tools or its own separate project at Google Code,
but the rest don't.
Blair
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1568533
Received on 2009-04-07 03:14:18 CEST