public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>, <gerald@pfeifer.com>
Subject: Re: [PATCH,WWWDOCS] htdocs: add an Atom feed for GCC news
Date: Thu, 12 Jan 2023 00:59:01 +0100	[thread overview]
Message-ID: <87r0w0r5bu.fsf@oracle.com> (raw)
In-Reply-To: <875ydcskal.fsf@oracle.com> (Jose E. Marchesi's message of "Thu, 12 Jan 2023 00:50:26 +0100")


>> Hi!
>>
>> On 2022-12-23T10:50:13+0100, "Jose E. Marchesi via Gcc-patches" <gcc-patches@gcc.gnu.org> wrote:
>>> This patch adds an Atom feed for GCC news, which can then be easily
>>> aggregated in other sites, such as the GNU planet
>>> (https://planet.gnu.org).
>>>
>>> The feed lives in a file news.xml, and this patch initializes it with
>>> the latest entry in News as an example.
>>
>> I absolutely agree that providing such an RSS feed is a good thing
>> (..., and that we generally should make better use of our News section,
>> and other "PR"...) -- but I'm less convinced by the prospect of manually
>> editing the RSS 'news.xml' file, duplicating in a (potentially) different
>> format what we've got in the HTML News section.  :-|
>>
>> Ideally, there'd be some simple files for News items (Markdown, or
>> similar), which are then converted into HTML News as well as RSS feed.
>> Obviously, there needs to be some consensus on what to use, and somebody
>> needs to set up the corresponding machinery...
>>
>> Or do others think that manual 'news.xml' maintenance is not so bad (for
>> now)?
>
> I would like to point out that I have maintained these kind of feeds for
> my own sites for years, and that in my humble personal experience unless
> there are a lot of updates, like more than a couple of new entries per
> month, any automated schema would be overkill, prone to rot, and not
> really worth the effort.
>
> I strongly suggest to not overengineer here [and nowhere else :)]

I forgot to mention that it is also useful to have fine-grain control of
what you publish on what feed.

Not all the news may be appropriate for all feeds.  For example, I have
a separated feed in my site for entries I want to aggregate in the GNU
Planet.  Other stuff, which is more personal in nature, is included in a
more general feed, or not included in a feed at all.

Not sure if this really applies to the case in hand, which is the GCC
News, but that is another reason why I maintain my feeds manually as
proposed in the patch..

>
>>
>> Grüße
>>  Thomas
>>
>>
>>> ---
>>>  htdocs/index.html |  9 ++++++++-
>>>  htdocs/news.xml   | 28 ++++++++++++++++++++++++++++
>>>  2 files changed, 36 insertions(+), 1 deletion(-)
>>>  create mode 100644 htdocs/news.xml
>>>
>>> diff --git a/htdocs/index.html b/htdocs/index.html
>>> index e91fadf1..2ddee6f6 100644
>>> --- a/htdocs/index.html
>>> +++ b/htdocs/index.html
>>> @@ -6,6 +6,9 @@
>>>  <meta name="google-site-verification" content="FUv_3eEIkimd6LAoWned4TPMqmKKQmw3aA2_PBJ5SAY">
>>>  <title>GCC, the GNU Compiler Collection</title>
>>>  <link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
>>> +<link rel="alternate" type="application/rss+xml"
>>> +      title="News about the GNU Compiler Collection"
>>> +      href="news.xml"/>
>>>  </head>
>>>
>>>  <set-var navigation>
>>> @@ -48,7 +51,11 @@ mission statement</a>.</p>
>>>
>>>  <!-- 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.
>>>  -->
>>>
>>>  <td class="news border0">
>>> diff --git a/htdocs/news.xml b/htdocs/news.xml
>>> new file mode 100644
>>> index 00000000..bebcaa66
>>> --- /dev/null
>>> +++ 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>
>>> +
>>> +    <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
>>> +      </description>
>>> +      <pubDate>Fri, 23 December 2022 11:00:00 CET</pubDate>
>>> +    </item>
>>> +
>>> +  </channel>
>>> +</rss>
>>> --
>>> 2.30.2
>> -----------------
>> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße
>> 201, 80634 München; Gesellschaft mit beschränkter Haftung;
>> Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft:
>> München; Registergericht München, HRB 106955

  reply	other threads:[~2023-01-11 23:55 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 [this message]
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

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=87r0w0r5bu.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=thomas@codesourcery.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).