[OSM-dev] OSM software repositories -- git and svn

[Jochen Topf]

On Fri, May 23, 2014 at 03:19:07PM +0200, Frederik Ramm wrote:
> 2. discoverability
> 
> I know that there are people who create a github repository for
> everything, even if it's just a 30-line text file to maintain. Doing
> that for all the conceptually different things that we now have in our
> SVN would probably yield something between 200 and 500 "repositories",
> and it would be (correct me if I am wrong please) a big step backwards
> in discoverability because git(hub) repositories cannot be arranged in
> trees - in SVN I can, for example, go to "applications/rendering" or
> "applications/utils/export" and do an "ls" there to see.
> 
> Would that mean that we'd essentially have to create one big repository
> that can hold a ton of completely separate stuff like our SVN does
> today? Or would we create hundreds of mini repos and then have a
> separate index for them, e.g. a wiki page or a 101st repo? Maybe there's
> some state of the art solution for this kind of problem?

Lots of little repositories and a 101st with repo with list of repo URLs
sound good to me. This would also allow different ownership/rights for
all of the little repos. Why a one-size-fits-all solution when some repos
could be free-for-all and some more managed. Just allow everybody to add
any repository to your 101st "list repo".

If you want to, you could ask people to add some standardized meta.json
file or so that you can then crawl to build some kind of index to make
it even easier to find repos by keyword or whatever.

Jochen
-- 
Jochen Topf  jochen at remote.org  http://www.jochentopf.com/  +49-721-388298