public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] getting-help: update mailing list links to lore.proxmox.com
Date: Fri, 29 Nov 2024 14:24:45 +0100	[thread overview]
Message-ID: <csbke43mwblwiwpvyipwaova4snc7hyw6q3oz3p25cefkmibkt@h23bgrpj2snc> (raw)
In-Reply-To: <D5YOXEPBMIEG.204VS8O6S7XQ7@proxmox.com>

On Fri, Nov 29, 2024 at 02:18:25PM +0100, Shannon Sterz wrote:
> On Fri Nov 29, 2024 at 2:08 PM CET, Christoph Heiss wrote:
> > [..]
> > @@ -27,14 +27,13 @@ Mailing Lists
> >  This is a fast way to communicate with the {pve} community via email.
> >
> >  * Mailing list for users:
> > -  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user[{PVE} User List]
> > +  https://lore.proxmox.com/pve-user[{PVE} User List]
> >
> >  {pve} is fully open source and contributions are welcome! The primary
> >  communication channel for developers is the:
> >
> >  * Mailing list for developers:
> > -  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel[{PVE} development
> > -  discussion]
> > +  https://lore.proxmox.com/pve-devel[{PVE} development discussion]
> >
> >
> >  Commercial Support
>
> while i think it would be nice to also send more people towards
> lore.proxmox.com, they can't sign up for the mailing list there. so
> maybe we should either have two links here (sign up here & archive, or
> something like that) or maybe have a link over at lore.proxmox.com that
> points people towards lists.proxmox.com. maybe both.

Thanks, great catch!

I'd probably go the route of having both the archive link (to lore) and
a separate sign-up link (to mailman) in the documentation, since it
isn't really that much of an uncommon pattern anyway IMO.

Also, don't know if & how the lore homepage could be modified to include
such a link - although that would have merits on it's own, I think.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2024-11-29 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 13:08 Christoph Heiss
2024-11-29 13:18 ` Shannon Sterz
2024-11-29 13:24   ` Christoph Heiss [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=csbke43mwblwiwpvyipwaova4snc7hyw6q3oz3p25cefkmibkt@h23bgrpj2snc \
    --to=c.heiss@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal