From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: GLEP - Require Projects to report to Council Monthly
Date: Sat, 21 Jan 2017 14:11:53 +1300 [thread overview]
Message-ID: <20170121141153.2e45b9d9@katipo2.lan> (raw)
In-Reply-To: <assp.0193865e66.9864873.r3X9HPUQ9q@wlt>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Thu, 19 Jan 2017 21:45:13 -0500
"William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> Your also missing entire that such reporting can help people outside of Gentoo
> gain more interest in Gentoo. If they know what is going on. You want bugs
> fixed? Would more people not potentially mean more bugs are fixed faster? Or
> rather expect more time from the existing pool?
>
> This is in part to grow Gentoo.
I'm ok with some plan having a fringe benefit of increasing public awareness.
I just want to make sure this is not a primary objective.
Popularity through a reputation of quality is preferred over attempting to gain
quality through a reputation of popularity.
The latter does make you grow faster, but I have no interest in something popular
but substandard, which usually happens.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-21 1:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 18:45 [gentoo-project] RFC: GLEP - Require Projects to report to Council Monthly William L. Thomson Jr.
2017-01-19 20:32 ` Johannes Huber
2017-01-19 20:47 ` William L. Thomson Jr.
2017-01-19 20:49 ` Johannes Huber
2017-01-19 21:00 ` William L. Thomson Jr.
2017-01-20 12:13 ` Johannes Huber
2017-01-20 15:00 ` William L. Thomson Jr.
2017-01-22 15:39 ` Rich Freeman
2017-01-22 16:16 ` William L. Thomson Jr.
2017-01-22 17:44 ` Rich Freeman
2017-01-22 17:55 ` William L. Thomson Jr.
2017-01-22 19:27 ` Rich Freeman
2017-01-22 19:45 ` William L. Thomson Jr.
2017-01-22 19:55 ` Rich Freeman
[not found] ` <8541344.yooe8zxigj@wlt>
2017-01-20 15:14 ` William L. Thomson Jr.
2017-01-19 21:19 ` Kent Fredric
2017-01-19 21:27 ` William L. Thomson Jr.
2017-01-19 21:39 ` Kent Fredric
2017-01-19 21:59 ` William L. Thomson Jr.
2017-01-19 22:21 ` Kent Fredric
2017-01-19 22:50 ` William L. Thomson Jr.
2017-01-19 23:24 ` Patrick McLean
2017-01-20 2:45 ` William L. Thomson Jr.
2017-01-21 1:11 ` Kent Fredric [this message]
2017-01-22 7:27 ` Daniel Campbell
2017-01-22 16:27 ` William L. Thomson Jr.
2017-01-23 9:01 ` Daniel Campbell
2017-01-21 1:04 ` Kent Fredric
2017-01-21 3:27 ` Dean Stephens
2017-01-21 5:12 ` William L. Thomson Jr.
2017-01-21 5:30 ` NP-Hardass
2017-01-21 15:04 ` William L. Thomson Jr.
2017-01-23 9:06 ` Daniel Campbell
2017-01-21 15:53 ` Kent Fredric
2017-01-21 17:03 ` William L. Thomson Jr.
2017-01-26 1:57 ` Kent Fredric
2017-01-26 15:45 ` William L. Thomson Jr.
2017-01-26 23:45 ` Kent Fredric
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=20170121141153.2e45b9d9@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-project@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