Void Linux discussion
 help / color / mirror / Atom feed
From: "'Caleb M.' via voidlinux" <voidlinux@googlegroups.com>
To: Alexis <flexibeast@gmail.com>
Cc: voidlinux@googlegroups.com
Subject: Re: patch to add mailing list to website
Date: Fri, 3 Jul 2020 02:14:19 -0400	[thread overview]
Message-ID: <20200703021419.5a3b3dc0247460d8d45b0bc5@sdf.org> (raw)
In-Reply-To: <87h7upgorh.fsf@ada>

On Friday, July 3, 2020 1:18:26 AM EDT, Alexis wrote:
>> It also removes the "Forum" heading on the nav bar.
> Sorry, i don't understand why you'd do that? That's a link to
> the r/voidlinux subreddit, which is thriving, and which is one
> of the two primary places we suggest people ask for help (the
> other being #voidlinux on Freenode). This mailing list has been
> inactive for a while.

It made sense to have a "Forum" heading back when it was Discourse,
because it was hosted by the project and felt more like part of the

When the "Forum" heading started linking to the subreddit it seemed
weird to me because the subreddit is not part of the site, and most
people would call it a subreddit rather than a forum.

If we are linking to the mailing list from the website, it feels even
more weird to leave the heading there.  If we are adopting a more
expansive definition of the word "forum" that includes the subreddit,
then the google group is a forum too.  At that point the "Forum"
heading is more confusing than helpful, in my opinion.

The inactivity of the mailing list could be due to the lack of any
mention of it on the website, or the fact that you and others don't
point people to it.  It sounds like some members of the community
have decided the mailing list is dead, while some are still suggesting
it as a place to ask for help and submit patches.  Perhaps we should
have a broader discussion about whether the mailing list is an
official communication channel?

At any rate, it's not all that important, but I hope I have conveyed
why I think the Forum heading is increasingly misplaced.

> More generally, though, the best thing to do would probably be
> to submit your patch in the form of a PR to
> https://github.com/void-linux/void-linux.github.io/.

I don't have a GitHub account, and a few people on IRC have said
the project will accept patches via the mailing list.  I hope that
is still true.


You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/20200703021419.5a3b3dc0247460d8d45b0bc5%40sdf.org.

  reply	other threads:[~2020-07-03  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 21:29 'Caleb M.' via voidlinux
2020-07-03  5:18 ` Alexis
2020-07-03  6:14   ` 'Caleb M.' via voidlinux [this message]
2020-07-03  7:09     ` Alexis
2020-07-12  9:09       ` 'Quentin Rameau' via voidlinux
2020-07-12  9:40         ` Đoàn Trần Công Danh
2020-07-21 19:42           ` 'Caleb M.' via voidlinux
2020-07-21 20:50             ` 'Quentin Rameau' via voidlinux
2020-07-21 20:59               ` Juan Romero Pardines

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:

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

  git send-email \
    --in-reply-to=20200703021419.5a3b3dc0247460d8d45b0bc5@sdf.org \
    --to=voidlinux@googlegroups.com \
    --cc=cm@sdf.org \
    --cc=flexibeast@gmail.com \


* 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 NNTP newsgroup(s).