Hi Justin, I've started on a project named Lagerstätte with similar concepts. You might want to checkout the initial announcement here: https://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg20003.html
Cheers. - Vikrant On 17 April 2015 at 17:11, <jus...@postgresql.org> wrote: > Random idea, and not sure where to put it... ;) > > With the GlusterFS project, we do our patch reviewing and > stuff using a system called Gerrit. (not that impressed > with it tbh) > > A large problem is that Gerrit needs to control the source > code repo itself. This has stopped us from having our > primary source code repo on GitHub - where the largest > Open Source dev Community is. > > Note - We do have a mirror repo there... but Pull Requests > aren't accepted through it, and it's more of a "tick the > box" kind of presence than driving growth. > > ... but now we've discovered "GerritHub". This is a system > that uses GitHub for the backend repo storage, but with a > Gerrit front end. People can submit patches through either > GitHub OR the Gerrit front end, and they go into Gerrit > properly. It uses a Gerrit-GitHub plugin for part of this > integration. > > The thought occurred that some Fossil users probably have > a similar problem (but with Fossil, not Gerrit). If so, > it might be nifty idea for someone (not me ;>), to create > a Fossil-GitHub plugin, which actively keeps patch sets > in sync between the two systems too. > > This would let people have their repos on GitHub - a source > of much potential growth - but use Fossil too. > > Crap idea or not? :) > > Regards and best wishes, > > Justin Clift > _______________________________________________ > fossil-dev mailing list > fossil-dev@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev >
_______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
