From: Alexis <firstname.lastname@example.org>
To: "Caleb M." <email@example.com>
Subject: Re: patch to add mailing list to website
Date: Fri, 03 Jul 2020 17:09:50 +1000 [thread overview]
Message-ID: <87eeptgjlt.fsf@ada> (raw)
Caleb M. <firstname.lastname@example.org> writes:
> It made sense to have a "Forum" heading back when it was
> because it was hosted by the project and felt more like part of
> When the "Forum" heading started linking to the subreddit it
> weird to me because the subreddit is not part of the site, and
> people would call it a subreddit rather than a forum.
> If we are linking to the mailing list from the website, it feels
> more weird to leave the heading there. If we are adopting a
> expansive definition of the word "forum" that includes the
> then the google group is a forum too. At that point the "Forum"
> heading is more confusing than helpful, in my opinion.
Okay. Certainly my experience is that many people seem to have a
very specific idea of what a "forum" is, so i take your points in
that regard. On that basis, the use of the word "forum" on the
"Join Us" page should also be changed, to e.g. "... or on the
> The inactivity of the mailing list could be due to the lack of
> mention of it on the website, or the fact that you and others
> point people to it.
When i started using Void last year, the mailing list was
mentioned in a few different places, and so i immediately joined
it. Despite the fact that the mailing list /was/ being mentioned,
i found that people weren't using it. Which doesn't surprise me -
although i prefer mailing lists, it seems many people nowadays
really don't like using them. So i'm not sure that the inactivity
of the mailing list is primarily due to it not being mentioned.
> It sounds like some members of the community
> have decided the mailing list is dead, while some are still
> it as a place to ask for help and submit patches. Perhaps we
> have a broader discussion about whether the mailing list is an
> official communication channel?
Yes, i agree it would be good to be clear on this, as i raised
this issue myself here:
If it's decided that the mailing list is still an official
communication channel, then it should certainly be mentioned on
the "Join Us" page.
> 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
> is still true.
i don't have a commit bit for that particular repo, so it's up to
those who do. :-)
W.r.t. the void-docs repo, for which i /do/ have a commit bit, i
am personally happy to take contributions in a variety of forms:
not only diffs, but also comments (either here or on r/voidlinux)
which simply describe the suggested changes.
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/87eeptgjlt.fsf%40ada.
next prev parent reply other threads:[~2020-07-03 7:10 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
2020-07-03 7:09 ` Alexis [this message]
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
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 \
* 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).