GCC Rust monthly call

[Philip Herron]

Hello,

On the first Friday of every month, GCC Rust has a community call. The
next one will be on the 4th of June 2021, at 10am utc+1 (I am based in
Northern Ireland). We use our zulip server
(https://gcc-rust.zulipchat.com/), which provides a jitsi integration to
facilitate the video call. I want to invite people from the GCC
community to join if they wish.

These monthly calls have associated meeting notes for those who cannot
attend. Here is an example from our last meeting: 
https://github.com/Rust-GCC/Reporting/blob/main/2021-05-07-community-call.md

The agenda for this next call is currently being set up in a
collaborative document here: https://hackmd.io/rBFlwl_9TkWLox-X6jyxDg

Please find the monthly report for May 2021 for more information:
https://github.com/Rust-GCC/Reporting/blob/main/2021-05-monthly-report.org

Thanks

--Phil



OpenPGP_signature
Description: OpenPGP digital signature

GCC documentation: porting to Sphinx

[Martin Liška]

Hello.

I've made quite some progress with the porting of the documentation and
I would like to present it to the community now:
https://splichal.eu/scripts/sphinx/

Note the documentation is automatically ([1]) generated from texinfo with a 
GitHub workflow ([2]).
It's built on the devel/sphinx GCC branch which I periodically with the master 
branch. One can
see the current source .rst files here: [3].

Changes made since the last time:
- a shared content is factored out ([4])
- conditional build is fully supported (even for shared parts)
- manual pages look reasonable well
- folders are created for files which have >= 5 TOC tree entries
- various formatting issues were resolved
- baseconf.py reads BASE-VER, DEV-PHASE, .. files

I've got couple of questions:

1) Do we have to you the following cover text?
   Copyright (c) 1988-2020 Free Software Foundation, Inc.

   Permission is granted to copy, distribute and/or modify this document under 
the terms of the GNU Free Documentation License, Version 1.3 or any later version 
published by the Free Software Foundation; with the Invariant Sections being 
"GNU General Public
   License" and "Funding Free Software", the Front-Cover texts being (a) 
(see below), and with the Back-Cover Texts being (b) (see below).  A copy of the license is 
included in the gfdl(7) man page.

   (a) The FSF's Front-Cover Text is:

A GNU Manual

   (b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU
software.  Copies published by the Free Software Foundation raise
funds for GNU development.

2) Do we want to generate fsf-funding, gpl and gfdl manual pages?
3) Do we want to preserve the current strange copy mechanism for 
./gcc/doc/tm.texi.in ?
4) Do we want a copyright header for the created .rst files?

Thoughts?
Thanks,
Martin

[1] https://github.com/davidmalcolm/texi2rst
[2] https://github.com/davidmalcolm/texi2rst/actions
[3] https://github.com/marxin/texi2rst-generated/tree/master/sphinx
[4] https://github.com/marxin/texi2rst-generated/tree/master/sphinx/share

Re: GCC documentation: porting to Sphinx

[Michael Matz]

Hello Martin,

On Mon, 31 May 2021, Martin Liška wrote:

> I've made quite some progress with the porting of the documentation and
> I would like to present it to the community now:
> https://splichal.eu/scripts/sphinx/
>  
> Note the documentation is automatically ([1]) generated from texinfo with a
> GitHub workflow ([2]).

One other thing I was recently thinking about, in the Spinx vs. texinfo 
discussion: locally available documentation browsable/searchable in 
terminal with info(1) (or equivalents).  I think the above (i.e. 
generating .rst from the texinfo file) would immediately nullify all my 
worries.  So, just to be extra sure: your proposal now is to generate the 
.rst files, and that .texinfo remains the maintained sources, right?


Ciao,
Michael.