On Mon, 2016-06-20 at 11:49 +0200, Johannes Thumshirn wrote: > On Thu, Jun 16, 2016 at 09:56:12AM -0700, Vasu Dev wrote: > > Intel enabled open-fcoe support in the kernel back in 2007, since > > then > > it has maintained that code as an open source project hosted at > > open- > > fcoe.org and at the OSU Open Source Lab. Today, the software > > enabling > > FCoE is very mature and self-sufficient. Due to the maturity of the > > project, a less active "hands on" approach is needed by Intel in > > its > > maintenance. As a result, Intel is moving away from actively > > maintaining the project including the mailing list, git > > repositories, > > and project maintainership. > > > > If someone from the open-fcoe community with a confirmed > > contribution > > history comes forward with a desire to pick up the mantle of > > maintainership, then please reply to this message and I can pass on > > maintainership to them. Otherwise open-fcoe will lack a current > > maintainer when I remove my name from the MAINTAINERS file, and it > > will > > become an orphaned project. > > A fair coin toss between Hannes and me decided I'll volunteer to take > over the > maintainership of open-fcoe. > > If noone disagrees with that, of cause. > Good and works for me, I'll send offlist open-fcoe.org access info. Go ahead and update maintainer file with your contact replacing my name.
//Vasudev _______________________________________________ fcoe-devel mailing list [email protected] http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
