Well since it’s come up (I guess I’m bringing it up) Maybe Apache is getting too big to manage all it’s own list servers (down for several groups last week), repos, bug trackers, wikis (cwiki looks like it’s down)
Have we thought about Github (repo, bug tracking, Jenkins) + Google or Yahoo Groups + Stackoverflow? Replacing, er, most Apache infra? I’m super grateful for the guys who work on all this but is it becoming unmaintainable? With every new thing we ask for (git + svn integration? plus running git repos) they can probably do it but it adds more moving parts until some day... On May 16, 2014, at 3:37 PM, Ted Dunning <[email protected]> wrote: On Fri, May 16, 2014 at 10:16 AM, Pat Ferrel <[email protected]> wrote: > Agree 100% but there is seems to be an extra level of indirection here. > > 1) do your work in your personal github repo, probably using a branch > Exactly. > 2) issue a pull request to ??? the github Mahout repo or Apache Mahout git > repo? > To the github Mahout mirror. Otherwise, yes. > 3) respond to the request somewhere to make sure the merge goes well. > exactly. > It would be nice if we only had to deal with github imo. They will trigger > a Jenkins build on repo changes. > Well... yes. It would be nice to use the pretty green button on the github site, but it isn't much more work to do the merges manual. For merges that are clean, there are 3 or 4 commands required to merge the PR and github provides them. Doing the JIRA is additional effort. > > On May 15, 2014, at 3:33 PM, Ted Dunning <[email protected]> wrote: > > On Fri, May 9, 2014 at 4:17 PM, Pat Ferrel <[email protected]> wrote: > >> But pull requests would just be for contributors, right? Committers > should >> be able to push to the master directly, right? >> > > Not necessarily. Pull requests are so lovely nice to work with no matter > who you are. > > I can easily imagine using them myself for a long-lived change. > >
