On Thu, Sep 29, 2011 at 4:07 PM, NeilBrown <neilb@xxxxxxx> wrote: >> What if as a starting point we could get a Patchwork queue hosted >> somewhere so you could at least start formally delegating incoming >> patches for an apprentice to disposition? > > I don't know much about Patchwork ... what sort of value does it add? It just makes things more transparent. It allows a submitter to have a web interface to view the state of a patch: accepted, rejected, under review. Allows a maintainer or a group of maintainers to see the backlog and assign (delegate) patches between them. It also automates the collection of Acked-by, Reviewed-by, etc tags. > But I don't think much of the idea of delegation. I don't see a thriving > developer community full of people who want work delegated to them. So I only meant "delegate" in the Patchwork parlance to make "who is merging this md/mdadm patch" clear as the apprentice ramps up. But this is probably too much mechanics. It simply sounds like you want a similar situation like what happened with git. I.e. a "Junio" to take over but you'll still be around to course correct and send patches. -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
