The additional factor is that github doesn't provide sufficient control over access to individual projects. If it were possible to ensure that only committers had access to the github mirror, it would be plausible to handle pull requests more directly, even with SVN as the primary repo. We could handle the pull request using github and use git svn to push back to SVN.
Until github does that (and there is no motion in that direction), then patches will rule. On Sun, May 12, 2013 at 1:50 PM, Stevo Slavić <[email protected]> wrote: > I understand, thanks. This seems to be general ASF infra/policies and > GitHub pull requests issue. > Will continue to submit both pull requests on github and svn compatible > patches attached to JIRA, and close pull requests by myself once patches > get integrated/merged. > > Kind regards, > Stevo Slavic. > > > On Sun, May 12, 2013 at 7:43 PM, Ted Dunning <[email protected]> > wrote: > > > > > > > We talked about this but it is difficult to switch the user base except > at > > the beginning if a project. For drill, as an example, we started with > git. > > > > Unfortunately that still doesn't solve the pull problem since the apache > > source on GitHub is just a mirror and can't push updates back to apache. > > > > The only good news is that enough of use git that git formatted patches > > are ok. > > > > On May 12, 2013, at 2:05, "Stevo Slavic (JIRA)" <[email protected]> wrote: > > > > > I wish Mahout used git as primary scm. > > >
