My first thought would be to have a "dev-tools" repo which individual
contributors could fork and vc their tools in. If a tool became widely
used, it could be merged into the primary branch. Using this
structuring of repos, GitHub will automatically keep track of the
fork'ed repos for us.
Maybe this isn't quite right though if the forked repos will vary
wildly from the original one. Maybe the best bet would be to have a PA
organization on github and then you could access the individual
developers' pages directly.
--
Dan King
College of Computer and Information Science
Northeastern University
Absolutely. We're all going to be flinging spaghetti at the walls;
eventually something will stick and at that point we can think about
higher level organization.
> Or would it be better/more appropriate to have something like a dev-tools
> sub directory in the main repo, and we put our "figuring things out" tools
> in there? That doesn't seem as appealing to me, but I'm fine with whatever.
> I just would like to see what we all have available, no matter how
> incomplete/hackish/ugly or whatever.
>
> Am I way off base? What do you all think?
Produce, announce to the list and if something comes along well enough
to be exciting go from there.
> --Scott
--
Brian L. Troutwine