[yocto-ab] eglibc - move under yocto?

[Kridner, Jason]

My instant thought was a +1.  Checking around with the right folks at TI have pretty well confirmed it.  Just hope to see the existing maintainers stay engaged.


________________________________
From: yocto-ab-bounces at yoctoproject.org [yocto-ab-bounces at yoctoproject.org] on behalf of Osier-mixon, Jeffrey [jeffrey.osier-mixon at intel.com]
Sent: Tuesday, September 27, 2011 6:48 PM
To: Dan Cauchy
Cc: yocto-ab at yoctoproject.org
Subject: Re: [yocto-ab] eglibc - move under yocto?

+1 from me! Fantastic synergy.

John, if the eglibc project maintainers have someone whose role includes a community manager function, please put them in touch with me and I'll make sure the project is represented well on the Yocto Project website.


On Tue, Sep 27, 2011 at 11:35 AM, Dan Cauchy <dcauchy at mvista.com<mailto:dcauchy at mvista.com>> wrote:
John,

I think this is a good idea. No objections here.

Dan.

Dan Cauchy
VP of Marketing and Business Development
MontaVista Software
Email: dcauchy at mvista.com<mailto:dcauchy at mvista.com>
Office: +1-408-572-7918<tel:%2B1-408-572-7918>
Mobile: +1-408-623-4789<tel:%2B1-408-623-4789>


On Sep 26, 2011, at 3:18 PM, Cherry, John wrote:

Hi all,

As  you may know, EGLIBC was created to be an embedded version of the GNU C Library (GLIBC).  It was developed to achieve some goals that were not possible via a server-based C library.  EGLIBC is intended specifically for embedded systems, so it would make sense for the EGLIBC project to move under the Yocto project.  So, the proposal on the table for the Yocto AB is to move the EGLIBC project under Yocto and to host the project at the Linux Foundation.

The EGLIBC project was kicked off a few years ago with a set of four primary sponsors and Code Sourcery administering the development and management of the project.   The scope and usage of EGLIBC has obviously grown beyond these original members.  The EGLIBC project currently resides on CodeSourcery servers.   This proposal would move the EGLIBC repo and infrastructure from a CodeSourcery server to a Linux Foundation server and place it under the Yocto project.  The mailing lists and issue tracker could be maintained as is, or ported to the Yocto domain and the Yocto defect tracking system.  I would envision that the current maintainers would remain in their roles as EGLIBC maintainers, but that the Yocto advisory board would be able to appoint future maintainers as it makes sense.  The main benefits of moving EGLIBC under Yocto would be to expand the developer base for EGLIBC and to strengthen Yocto as the center of the embedded Linux universe.

The proposal to move the EGLIBC project under Yocto obviously requires the approval of the Yocto AB.  If the Yocto AB approves, I’ll put the wheels in motion to make the transition of EGLIBC from the CodeSourcery server to the Linux Foundation server.

Feedback? Comments? Concerns?

Thanks,
John

_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto-ab


_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto-ab




--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org<http://yoctoproject.org/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20110927/9c0ec79b/attachment.html>