Well, the system is becoming unmaintainable due to accumulated technical debt. But infra has David Nalley in charge and he is leading a very significant effort to pay down that debt and rebuild key services in a more maintainable form. I have spoken at length with David and he really impresses me as the right guy to make this all work better.
That said, he has a big task ahead and it won't happen in a moment. It probably won't even be completely done in the next 24 months. Regarding the suggestion to use out-sourced tools like Github, there is established policy at Apache that critical information, notably including the authoritative email record and source code have to be maintained on Apache resources. Period. End of Discussion. That doesn't mean that additional toolsets can be used to drive productivity, but if it doesn't get decided on the mailing list, it didn't get decided. This is critical to the community and longevity mission. The recent problems are significant, but they will be resolved. On Fri, May 16, 2014 at 4:35 PM, Pat Ferrel <pat.fer...@gmail.com> wrote: > 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 <ted.dunn...@gmail.com> wrote: > > On Fri, May 16, 2014 at 10:16 AM, Pat Ferrel <pat.fer...@gmail.com> 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 <ted.dunn...@gmail.com> wrote: > > > > On Fri, May 9, 2014 at 4:17 PM, Pat Ferrel <p...@occamsmachete.com> > 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. > > > > > >
