From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] gentoo cluster project
Date: Thu, 16 Oct 2014 14:19:36 +0000 [thread overview]
Message-ID: <20141016141936.GA4203@gentoo.org> (raw)
In-Reply-To: <543C1B01.2040900@tampabay.rr.com>
On Mon, Oct 13, 2014 at 01:33:37PM -0500, wireless wrote:
> There is an active gentoo cluster project located here:
>
> https://www.gentoo.org/proj/en/cluster/
>
> I have had correspondences with them.
>
> However they are not listed here:
>
> http://wiki.gentoo.org/wiki/Category:Gentoo_Projects
>
>
> Suggestions as to where to request adding the historical
> gentoo cluster project to the wiki are most appreciated.
They will need to create a project page on the wiki itself, then it will be
automatically listed on that page.
> Also, there has been much discussion about "herds" both organization
> and usefulness. It'd be great if when the dust settles someone with
> keen insight documents just how "herds" (if they survive) and
> "projects" are to be defined and used by the gentoo community.
>
I agree ;)
> Last question/point of clarification: You have to be a dev to be
> in a herd. Do you have to be a dev to be listed on a gentoo project?
> Is there a sub-status for projects, like receiving email to the group?
> Surely anyone can join an irc channel or discussion group. An
> overarching semantic and documents explaining these and other related
> semantics would be very useful to the gentoo user community, imho.
I believe you need to be a member to be part of a project, but some projects
have an additional "table" on their wiki page to reflect active contributors
and their assistance as well.
Wkr,
Sven Vermeulen
prev parent reply other threads:[~2014-10-16 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 18:33 [gentoo-doc] gentoo cluster project wireless
2014-10-16 14:19 ` Sven Vermeulen [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=20141016141936.GA4203@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
/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