Naturally, this sounds great. FWIW my only but significant worry about Spark is scaling up to meet unprecedented demand in the form of questions and contribution. Clarifying responsibility and ownership helps more than it hurts by adding process.
This is related but different topic, but, I wonder out loud what this can do to help clear the backlog -- ~*1200* open JIRAs and ~300 open PRs, most of which have de facto already fallen between some cracks. This harms the usefulness of these tools and processes. I'd love to see this translate into triage / closing of most of it by maintainers, and new actions and strategies for increasing 'throughput' in review and/or helping people make better contributions in the first place. On Thu, Nov 6, 2014 at 1:31 AM, Matei Zaharia <matei.zaha...@gmail.com> wrote: > Hi all, > > I wanted to share a discussion we've been having on the PMC list, as well as > call for an official vote on it on a public list. Basically, as the Spark > project scales up, we need to define a model to make sure there is still > great oversight of key components (in particular internal architecture and > public APIs), and to this end I've proposed implementing a maintainer model > for some of these components, similar to other large projects. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
