On Mon, Apr 06, 2009 at 11:53:39AM -0500, Hyrum K. Wright wrote:
>
> On Apr 6, 2009, at 11:45 AM, kmradke_at_rockwellcollins.com wrote:
>
>> Stefan Sperling <stsp_at_elego.de> wrote on 04/06/2009 11:31:54 AM:
>>> tools/ is "supported" and contrib/ is not.
>>> That's the only distinction I am aware of.
>>
>> That does imply there may be a "higher bar" to getting
>> something put into a "supported" directory. This is
>> probably good, but may turn away some potential
>> committers or some scripts/tools...
>
> No, it may turn away potential scripts, but people can still contribute
> to other areas of the project. The whole point here is that, while some
> contrib/ content may be useful for developers personally, they don't have
> specific value for the project. As a project, we should let these
> scripts find homes which best suite them, and our repository isn't it.
Our repository isn't it because ...?
I still think that distributing generally useful and maintained
things in tools/ is a great idea, because it makes it easy for users
to find tools that are known to be useful and maintained.
I just don't see a point in having two directories for this purpose,
one of which contains stuff that is not maintained or with no licence.
I'd even go as far as offering the svn-load and pysvn people to migrate
into our repo, because their stuff is apparently useful and maintained.
Stefan
Received on 2009-04-06 19:02:08 CEST