If the issue is that of plugins, then I would concur, though tangentially there still seems to be some work to harmonize how projects produce their artifacts. Dividing things into projects has the neat property that those whose maintainers become negligent cause the project to wither on the vine and naturally die off.
Not having witnessed the discussion on the VPP call that started this though (I’m out this week[1]) what is it that is driving this discussion? I really want to avoid protracted hierarchy, which I doubt will solve the problem and worse may give the appearance of solving it. I dislike the accompanying bureaucracy that, for example, some OpenStack projects exhibit. It is my observation that in such projects the discussion becomes more the politics of a change than the merit of it. I do not have the time for such games. Cheers, Chris. [1] Which today involves a story about my arm being up-to-the-elbow in my furnace… but a tale of misadventure for another time perhaps. :) From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Florin Coras Sent: Wednesday, December 21, 2016 15:44 To: Damjan Marion <dmarion.li...@gmail.com> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Committer / Maintainer model. Wouldn’t it be better to have separate projects for each plugin (or maybe groups of them) and thereby have maintainers automatically become committers within their respective projects? As far as I can see this diminishes load on VPP committers and gives the required ‘power' to the interested parties. Just my 0.02$ Florin On Dec 21, 2016, at 10:25 AM, Damjan Marion <dmarion.li...@gmail.com<mailto:dmarion.li...@gmail.com>> wrote: On 21 Dec 2016, at 18:49, Kinsella, Ray <ray.kinse...@intel.com<mailto:ray.kinse...@intel.com>> wrote: If somebody submits plugin change + 3 lines of new code in critical ip4 path, I will greatly benefit from +1 received from plugin maintainer and i will focus on this 3 lines. If I don’t have +1 from plugin maintainer, i will just left whole diff in the gerrit, simply because i don't have a clue about that plugin. But really, the committer will have nothing to add about the plugin in this case. A more efficient process would be to let an IPv4 committer review and commit the IPv4 change, with the Plugin committer separately doing likewise. Many open source project require that patches be made separately for component. Yes, and hire one guy to bitch with people who are not following that rule... _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
