From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [RFCv2 00/15] RFCv2: Consolidated userspace RDMA library repo Date: Tue, 6 Sep 2016 12:34:05 -0600 Message-ID: <20160906183405.GA27914@obsidianresearch.com> References: <20160828182715.GA12783@obsidianresearch.com> <004e01d20203$156edc30$404c9490$@opengridcomputing.com> <20160829161902.GB23557@obsidianresearch.com> <20160830060842.GJ594@leon.nu> <20160830071716.GA3098@infradead.org> <20160830073521.GM594@leon.nu> <20160830163033.GC26778@obsidianresearch.com> <4b791de5-0d6e-fd94-8a31-2fe833ca72db@grimberg.me> <20160906070102.GA23248@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160906070102.GA23248-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Christoph Hellwig Cc: Sagi Grimberg , Leon Romanovsky , Steve Wise , 'Yishai Hadas' , 'Doug Ledford' , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, 'Devesh Sharma' , 'Hal Rosenstock' , 'Mike Marciniszyn' , 'Moni Shoua' , 'Sean Hefty' , 'Tatyana Nikolova' , 'Vladimir Sokolovsky' , 'Yishai Hadas' , 'Majd Dibbiny' , liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org, talal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org, yarong-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Tue, Sep 06, 2016 at 12:01:02AM -0700, Christoph Hellwig wrote: > On Sun, Sep 04, 2016 at 11:18:02AM +0300, Sagi Grimberg wrote: > > I think that having a maintainer per provider makes perfect sense > > and as long as you Jason (or anyone else) are committed to merging it > > all together and produce standard releases we are pretty much set. > > > > What I think it missing is a release schedule, stable fixes > > methodology and merge cycles. I think once we can agree on that > > a lot of the concerns will be addressed. > > So let's keep the maintainers as-is, e.g. each previous project > keepts it's own maintainer similar to driver maintainers in the > kernel. This is certainly what I imagined. Nobody else has the domain expertise for these sub components. However, there is a lot of work just to keep everything ticking over, compilers change, build tooling changes, distros need hand holding, boring patches need accepting. That is where all maintainers should see value in this approach. > We'll add Jason as a global maintainer for the build system or any > non-controverial fixes and we should be much better setup than the > current situation. I was hoping a team including Doug would handle the general patch stream. Most of the patch flow today is for libibverbs and related anyhow. If Leon wants to handle the boring patches and provider pulls then that seems like a good combination. > Combine that with kernel-like major releases plus minor release on > demand and we should have a winning setup. I think the release cadence should be driven more by the distros, but following the kernel cadence is a sane place to start. Not much point in making a release if nobody is out there wanting to use it. I expect the distros will want to go to a more stable maintenance footing so we many want to offer to co-maintain a public LTS branch... > Now we just need to bikeshed on a good name for the repo, because > honestly rdma-plumbing sucks as a name :) Let the painting commence! Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html