From: Cassie B <cass...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: How can we help?
Date: Tue, 17 Mar 2015 22:35:22 -0700 (PDT) [thread overview]
Message-ID: <67b48d21-cd7f-44d0-bab0-4770512dc402@googlegroups.com> (raw)
In-Reply-To: <ae779aa7-133b-44be-9d77-4d76838b71d5@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]
Getting on linuxquestions.org would be nice
On Wednesday, January 7, 2015 at 5:09:17 PM UTC-8, Logen Kain wrote:
>
> This is intended to be a continuation of
> https://plus.google.com/u/0/+LogenKain/posts/LxkBfWqscxy
> <https://plus.google.com/u/0/+LogenKain/posts/LxkBfWqscxy>
>
> So what can we do to make life easier for contributors and users?
>
> Should we have a mailing list? Just use Google communities? (does anyone
> actually use communities?)
> Set up a discourse forum? It's fairly easy to do on a Digital Ocean
> server for $10 a month. Might need to upgrade at some point but $10
> wouldn't be too bad to start with.
> Is google groups good enough? Or does it make Void look bad? Personally
> I think Void should have a forum that promotes Voidlinux more than Google.
>
> Things I know of that we can do to help void:
> Raise awareness - more people = more potential contributors
> Contribute package builds
> Contribute code to the package manager
> Documentation, I still use the Arch WIki whenever I have a Linux related
> question.
> If we could convince some North American Universities to host a void repo
> that would be wonderful.
>
> Anyway, discuss.
>
[-- Attachment #1.2: Type: text/html, Size: 1753 bytes --]
prev parent reply other threads:[~2015-03-18 5:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 1:09 Logen Kain
2015-01-09 18:22 ` Stefan Mühlinghaus
2015-01-10 0:40 ` Logen Kain
2015-01-16 9:28 ` Justin moore
2015-01-16 19:42 ` Stefan Mühlinghaus
2015-01-16 20:03 ` Juan RP
2015-01-17 2:09 ` Logen Kain
2015-02-27 5:42 ` JD Robinson
2015-03-03 18:20 ` bougyman
2015-03-18 5:35 ` Cassie B [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=67b48d21-cd7f-44d0-bab0-4770512dc402@googlegroups.com \
--to="cass..."@gmail.com \
--cc=voidlinux@googlegroups.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 NNTP newsgroup(s).