Hi Ben,
You are raising a very good question: how should the maintainers
accept code contributions in an open-source project? We try to keep a
reasonable high-bar for contributions, and sometimes the code-review
process delays the merge significantly. Bu the way, it's great to have
others in the community looking at the code, so thank you for that!
You can also just add comments on the pull-request, and start a
discussion on a relevant piece of code. The more feedback, the better
we become.
Regarding blame and praise, I think they (should) go to the authors.
We're trying to promote the IDE project as an open-source, independent
project, even though the biggest contributor right now *is* Typesafe.
Whenever we accept patches, we implicitly accept supporting that part
of the code, but people tend to stick around, and we're happy to have
long-time contributors like Mirko and Matt maintaining their code.
In this specific case, Mirko answered already: there are no UI tests
in the IDE (that's another discussion), and almost all the code in
this pull request is a GUI over the scala-refactoring library. As with
any external library, we implicitly 'trust' it, and if we find bugs,
we'll report them in the library's issue tracker. And indeed, when
reviewing a contribution I usually build that branch and give it a try
for a day or two. That tends to find not only bugs, but also usability
issues (or performance regressions). Not ideal, but has some
advantages.
cheers,
iulian
--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais