From: Gerald Pfeifer <gerald@pfeifer.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
"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:31:58 +0100 (CET) [thread overview]
Message-ID: <d0a35099-fd34-352e-3286-d9c278fe8f72@pfeifer.com> (raw)
In-Reply-To: <875ydcskal.fsf@oracle.com>
On Wed, 11 Jan 2023, Thomas Schwinge wrote:
> 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).
> 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. :-|
Agreed, yet...
> 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...
...how are we going to get to that?
On Thu, 12 Jan 2023, Jose E. Marchesi wrote:
> 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.
That is a bit of a concern. I'd love having a single source that feeds
both the News section on our main page, rolls over into news.html, and
also feeds the Atom feed (no pun intended).
On the other hand, with less than a dozen entries per year, even if
manually converting form one to the other takes 5 minutes, creating
such a machinery wouldn't amortize anytime soon
> I strongly suggest to not overengineer here [and nowhere else :)]
I am tempted to agree (even if the engineer in me would prefer to avoid
duplication). Jose, might you be willing to help others create Atom feed
entries?
What do others think?
Gerald
next prev parent reply other threads:[~2023-01-17 9:32 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 [this message]
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=d0a35099-fd34-352e-3286-d9c278fe8f72@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jose.marchesi@oracle.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).