[yocto-ab] eglibc - move under yocto?

[Anderson, Paul]

Wind River has been a staunch supporter of eglibc over time, and has stuck to it through thick and thin.  All along, our singular goal was to come up with a scalable glibc solution that is broadly appropriate for a broad set of embedded devices, and for that solution to be widely adopted across the industry.

I think seeing this be part of Yocto would be a great thing.

Regards,

-pja

-- 
 
Paul J. Anderson
Vice President, Marketing & Strategy, Linux Products
WIND RIVER 500 Wind River Way  Alameda, CA 94501 
direct: +1 612.940.4992      mobile: +1 612.940.4992


-----Original Message-----
From: yocto-ab-bounces at yoctoproject.org [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Philip Balister
Sent: Monday, September 26, 2011 3:48 PM
To: Cherry, John
Cc: yocto-ab at yoctoproject.org
Subject: Re: [yocto-ab] eglibc - move under yocto?



On 09/26/2011 06: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?

Remind me, Mentor bought Codesourcery? I just want to make sure we all know who is who :)

My main concern are the maintainers and the eglibc community, are they OK with this?

Other than that, I think it is a reasonable idea.

Philip
_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-ab