Ngewi Fet <nge...@gmail.com> writes:
> On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins <warl...@mit.edu> wrote:
>
> John Ralls <jra...@ceridwen.us> writes:
>
> > Why can't we set up commit hooks on each that immediately push to the
> > other? Yes, there's a small chance of a conflict if two people push
> > changes of the same file to each repository at the same moment, but
> > the team is so small that that likelihood is infinitesimal.
>
> My main concern is that code.gnucash.org winds up with changes that
> weren't pushed by an 'authorized' developer.
>
> My knowledge on these matters may be limited, but I was just wondering:
> if Gnucash is setup as an organization on Github and the core devs have
> access to this repo, then nothing would ever get into it which was not pushed
> or merged by a core dev right? So the sync b/w GitHub and code.gnucash.org
> would only deal with commits from core devs.
> So how would the scenario you describe occur?
For example, if someone breaks into github.. again? (Yes, it has been
done before). I'd rather be in control of my own destiny rather than
depending on some other organization.
I understand that with git it is much harder to manipulate the sources
than with something like SVN or CVS, but I'd still rather limit the
exposure.
> Cheers,
> Ngewi
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
