xen-cim

[Top] [All Lists]

[Xen-cim] CIM provider maintainer

from [Jim Fehlig]

[Permanent Link][Original]

To:	<xen-cim@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-cim] CIM provider maintainer
From:	"Jim Fehlig" <jfehlig@xxxxxxxxxx>
Date:	Tue, 28 Mar 2006 11:40:45 -0500
Delivery-date:	Tue, 28 Mar 2006 16:42:05 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id:	xen-cim mailing list <xen-cim.lists.xensource.com>
List-post:	<mailto:xen-cim@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

It was very distracting calling in from a conference booth last week so
I didn't quite get the issues with selecting a maintainer for the
project.  I assume there is nothing unique about being the maintainer of
CIM provider project over any other open source project.  Although I
have never taken on this role, I have had commit rights to other
projects and worked closely with their respective maintainers.  It
didn't appear to be a burdensome task but they were rather confined
projects - 2 to 3 core developers and occasional patch from the
community.  I see the CIM provider falling into this category and would
be happy to take on maintainer responsibility.

Jim





_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-cim] CIM provider maintainer, Jim Fehlig <=

Next by Date:	[Xen-cim] Re: new xen-cim callin info, Gareth S Bestor
Next by Thread:	[Xen-cim] Re: new xen-cim callin info, Gareth S Bestor
Indexes:	[Date] [Thread] [Top] [All Lists]