public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH,WWWDOCS] htdocs: add an Atom feed for GCC news
Date: Tue, 17 Jan 2023 10:41:49 +0100 (CET)	[thread overview]
Message-ID: <2db18a30-75c8-a55a-fde3-58d6eba1d48e@pfeifer.com> (raw)
In-Reply-To: <20221223095013.3630-1-jose.marchesi@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]

On Fri, 23 Dec 2022, Jose E. Marchesi via Gcc-patches wrote:
> This patch adds an Atom feed for GCC news

I was going to approve, would like to see a bit consensus with others 
though.


For now some review:

>  <!-- Note: We usually want to rotate news to the "old news" page when
>       it's more than 12 months old or the News pane on this page has
> -     become longer than the parallel one, whatever happens first. 
> +     become longer than the parallel one, whatever happens first.
> +
> +     Note: There is an Atom feed in news.xml, which is aggregated by
> +     some news aggregators and "planets".  It is likely you want to
> +     add a new item there with the good news.
>  -->

I recommend switching the two notes. The one on the feed feels more 
important since that aspect is easier to miss than the required rotation 
(which visually presents itself when one looks at our web site).

> +++ b/htdocs/news.xml
> @@ -0,0 +1,28 @@
> +<?xml version="1.0" encoding="UTF-8"?>
> +
> +<rss version="2.0">
> +  <channel>
> +    <title>News about the GNU Compiler Collection</title>
> +    <link>https://gcc.gnu.org</link>
> +    <description>
> +      The GNU Compiler Collection includes front ends for C, C++,
> +      Objective-C, Fortran, Ada, Go, and D, as well as libraries for
> +      these languages (libstdc++,...). GCC was originally written as
> +      the compiler for the GNU operating system. The GNU system was
> +      developed to be 100% free software, free in the sense that it
> +      respects the user's freedom.
> +    </description>

Looks like we should think of updating our description (though that's 
beyond the scope of your patch), for example talking more about the many 
platforms supported and less about history.

> +    <item>
> +      <title>GCC BPF in Compiler Explorer</title>
> +      <link>https://godbolt.org</link>
> +      <description>
> +        Support for a nightly build of the bpf-unknown-none-gcc
> +        compiler has been contributed to Compiler Explorer (aka
> +        godbolt.org) by Marc Poulhiès

Would this be full sentences (with a full stop)?

When one adds additional entries, do those come at the beginning or the 
end? (Could there be a comment?)

> +      <pubDate>Fri, 23 December 2022 11:00:00 CET</pubDate>

On the web site we use ISO dates - any issues with that?

And does the feed require time of day, or could we omit that? (Especially 
with different timezones we all are in?)

Gerald

      parent reply	other threads:[~2023-01-17  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  9:50 Jose E. Marchesi
2023-01-11 22:11 ` Thomas Schwinge
2023-01-11 23:50   ` Jose E. Marchesi
2023-01-11 23:59     ` Jose E. Marchesi
2023-01-17  9:31     ` Gerald Pfeifer
2023-01-17 10:11       ` Jose E. Marchesi
2023-01-17 14:03         ` Arsen Arsenović
2023-01-17  9:41 ` Gerald Pfeifer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2db18a30-75c8-a55a-fde3-58d6eba1d48e@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jose.marchesi@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).