<br>> >> The problem with a restricted-access repository is we would <br>> >> probably have the same issues we have now: you need to ask for <br>> >> access, which would not be granted to you until you are <br>
> >> "well-known" and/or you've got some really interesting <br>> >> contribution. Not a big improvement, IMHO.<br>> >><br>> ><br>> > You don't know how git works, don't you? You can send a patch or let<br>
> > the maintainer pull from YOUR repository. It's much easier than svn or<br>> > cvs.ep<br>> <br>> I know how git works (and mercurial, too, by the way) but I don't see <br>> people setting up their own git repositories just for other people to <br>
> pull two FindWhaterEver.cmake.<br>> <br>> * Search: while searching for a FindXXXX.cmake, you would visit a lot <br>> of repositories one by one<br>> <br>> * Quality: as you don't know how many people downloaded that <br>
> particular finder, you've got no way to know if that particular <br>> FindXXXX.cmake is good or bad because you would not know how many <br>> people downloaded it.<br>> <br><br>Another option is to use Gitorious. <a href="http://gitorious.org/">http://gitorious.org/</a><br>
<br>You do not have to put the effort in making your own repository-- just sign up for<br>an account. We can put all the modules in one place, but the 'lead' repository<br>will stay with the person giving the most time and effort. The 'lead' repository<br>
can easily change<br>at any time.<br><br>It takes away the burden and faults of reviewing modules. Sometimes a central<br>source doesn't make good review decisions, but more often they just don't have<br>the time. Code will get validated if it get used and pulled in. If it is<br>
not all that good, it is trivial to make improvements and immediately share<br>those improvements with the world.<br>