This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: GNU Cauldron 2016 - The GNU C Library BoF
- From: Siddhesh Poyarekar <siddhesh at sourceware dot org>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 13 Jul 2016 18:46:11 +0530
- Subject: Re: GNU Cauldron 2016 - The GNU C Library BoF
- Authentication-results: sourceware.org; auth=none
- References: <a63e1cb8-2f8f-4aa7-d335-de76f698663d@redhat.com>
On Mon, Jul 11, 2016 at 02:07:45PM -0400, Carlos O'Donell wrote:
> I've organized a glibc BoF at the GNU Cauldron 2016:
> https://gcc.gnu.org/wiki/cauldron2016
>
> The following is the abstract, but in no way represents what
> we can and should actually talk about at the BoF. For those of
> you that can't make it, please don't worry, I'll post the notes
> online after the BoF.
>
> Please feel free to suggest more topic points and I'll aggregate
> them all for the BoF.
Like last time I think it would be great if we either host larger
topics as separate bofs or have multiple time slots.
> * Planning for glibc 2.25 and what work needs to be done
> between the August -> January 2017 timeframe.
>
> * Planning for glibc 2.26 and what work needs to be done
> between January 2017 and July 2017.
>
> * Wrappers for Linux syscalls and making forward progress.
>
> * Tunables.
>
> * New cancellation framework.
>
> * Float128.
* Benchmarking? This has stagnated a bit over the last year and it
would be nice to restart this.
* Pretty printers: Next steps, like merging the gdb-heap project into
glibc, identifying additional modules to pretty-print.
* glibc manual: A group here in Pune is trying to port the manual to
Sphinx for a more modern look and feel and also for a nicer, more
readable markup. This is in the very initial stages (ideas were
thrown around last weekend) so I hope to have something concrete by
Cauldron. The biggest concern with this is that it will likely be
hosted on github and will be lightly governed, so copyright
assignment might get tricky if there are contributions from outside
the group. I am going to try and get copyright assignments done for
the group if this materializes, but the easier way might be to
exempt the manual from an FSF assignment. I had asked a couple of
people about it last year (including you IIRC) and I don't remember
if there was an agreement on the idea.
Siddhesh