This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [ Guidance ] Preparing for Contribution
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: JeanHeyd Meneide <phdofthehouse at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 27 Dec 2019 06:59:48 -0500
- Subject: Re: [ Guidance ] Preparing for Contribution
- References: <CANHA4OjzJd3PcqV0sP_92WLu=pqTKtKv9tEckq2Qy+cQcg93hw@mail.gmail.com> <CANHA4OgeGRynATCRihMR669Vzv=EVQVpU+CQT8XKcpaTq+15Eg@mail.gmail.com>
On Fri, Dec 27, 2019 at 3:32 AM JeanHeyd Meneide
<phdofthehouse@gmail.com> wrote:
>
> On Thu, Dec 26, 2019 at 12:04 PM JeanHeyd Meneide
> <phdofthehouse@gmail.com> wrote:
> >
> > Dear glibc Maintainers and Contributors,
> > ... I am
> > interested in developing a few fast routines for text encoding for
> > musl ...
>
> Oops: glibc* -- I am interested in developing a few fast routines for
> text encoding for glibc.
No worries! I read it like you intended it; that you wished to
contribute to glibc and musl.
You need to follow the same process you did for contributions to gcc,
but for glibc.
The simplest "next step" is to do a futures assignment for glibc:
http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
Once you have an assignment in place for glibc we can start looking at
your patches.
My only suggestion would be that it may be beneficial to get an
assignment in place for binutils and gdb in the event you need to do
any work there.
You can see the specific part of the glibc contribution checklist:
https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment
You can see the whole contribution checklist here:
https://sourceware.org/glibc/wiki/Contribution%20checklist
I hope that helps!
Cheers,
Carlos.