all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: sirgazil <sirgazil@zoho.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Publishing news about Guix on a weekly basis
Date: Sat, 09 Nov 2019 18:33:38 +0100	[thread overview]
Message-ID: <87y2wp7y4t.fsf@gnu.org> (raw)
In-Reply-To: <16e47e550c8.d7a7b31e8461.1692456426007496507@zoho.com> (sirgazil@zoho.com's message of "Thu, 07 Nov 2019 17:04:01 -0500")

Hello,

sirgazil <sirgazil@zoho.com> skribis:

>  > > I have one question, though; couldn't these news be posted as entries 
>  > > in the current blog, tagged as "News" entries? 
>  >  
>  > Right, that's something I didn't really consider. 
>  >  
>  > Thinking about it now, I think it's worth considering though. What 
>  > advantages and disadvantages do you think they'd be for integrating this 
>  > in to the website? 
>  >  
>  > For advantages, I can think of: 
>  >  
>  >  - Easier to have a consistent visual style 
>  >  - Easier to provide a combined Atom feed for regular and weekly posts 
>
> Yes, I was thinking about these too. People already subscribed to Guix blog wouldn't have to subscribe to another news feed.
>
>
>  > As for disadvantages: 
>  >  
>  >  - Might make the website more complicated, doing partially automated 
>  >  weekly news stuff as well 
>
> No, I mean, your news application could be independent of the static website code in https://git.savannah.gnu.org/cgit/guix/guix-artwork.git. But I was thinking that maybe it could push the generated news to the posts directory in guix-artwork.git so that  your application wouldn't have to worry about the presentation part...

Sounds like an nice idea.

A potential concern for me is that these posts might be of relatively
“low quality” compared to the articles we usually publish (since they’d
be partially generated), and they would also outnumber those articles.
I wonder if this could leave a bad impression when visiting
guix.gnu.org/blog.

Or perhaps we just need to display those entries separately from those
that do not have the GWN tag or something?

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2019-11-09 17:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 12:19 Publishing news about Guix on a weekly basis Christopher Baines
2019-11-04  6:41 ` L p R n d n
2019-11-05  8:17   ` Christopher Baines
2019-11-04 12:44 ` Pjotr Prins
2019-11-04 13:04   ` Pierre Neidhardt
2019-11-05  8:37     ` Christopher Baines
2019-11-09 17:26       ` Ludovic Courtès
2019-11-05  8:36   ` Christopher Baines
2019-11-05 11:48     ` Pjotr Prins
2019-11-05 16:13       ` zimoun
2019-11-07 19:34         ` Christopher Baines
2019-11-07 18:28       ` Christopher Baines
2019-11-06 16:17 ` Ludovic Courtès
2019-11-07 19:41   ` Christopher Baines
2019-11-09 17:26     ` Ludovic Courtès
2019-11-06 17:53 ` sirgazil
2019-11-07 19:52   ` Christopher Baines
2019-11-07 22:04     ` sirgazil
2019-11-09 17:33       ` Ludovic Courtès [this message]
2019-11-11 16:09         ` sirgazil

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=87y2wp7y4t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=sirgazil@zoho.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.