[Scons-dev] Repo not wiki for tools and add-ons

[Bill Deegan]

Russel,

I've created:

https://bitbucket.org/scons/scons-contrib/admin/access

I've given you admin access to this repo as well.

Please add feel free to start populating.

Would it be worth having 3 base dirs:
tools
scripts
docs
?

Or just have tools live in the root of the repo?

-Bill

On Sat, Jul 4, 2015 at 8:45 AM, Russel Winder <russel at winder.org.uk> wrote:

> There seemed to be consensus that only having per project DVCS for
> tools was not enough, that there ought to be a curated central repo for
> various tools and add-ons that pass some notion of quality and utility.
>
> This implies someone setting up such a repository, which probably ought
> to be owned by the SCons user on BitBucket so it is clear it is the
> official repository. I am assuming Mercurial rather than Git.
>
> We then need to set up a process for populating that with some of the
> separate DVCS tools that are deemed to have reached an good stage of
> maturity.
>
> I think tools should start out seperate and need to get approval of
> some sort to shift to being in the managed repository, particularly if
> we use Mecurial rather than Git.
>
> --
> Russel.
>
> =============================================================================
> Dr Russel Winder      t: +44 20 7585 2200   voip:
> sip:russel.winder at ekiga.net
> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150704/95cfc248/attachment.html>