From: Johannes Huber <johu@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: GLEP - Require Projects to report to Council Monthly
Date: Thu, 19 Jan 2017 21:49:25 +0100 [thread overview]
Message-ID: <1937299.r3ENHUtASn@rioja> (raw)
In-Reply-To: <assp.01920c6e05.3289144.3AjPhJzHrx@wlt>
Am Donnerstag, 19. Januar 2017, 15:47:46 CET schrieb William L. Thomson Jr.:
> On Thursday, January 19, 2017 9:32:57 PM EST Johannes Huber wrote:
> > And when the projects are not doing it, projects get disbanded. Meaning
> > packages go to single maintainer only. Which means reporting goes away.
> > Great plan!
>
> If projects are not doing it, and packages fall to a single maintainer. Then
> should it even really be a project? A project/team ideally is more than
> just one person. If it is just one person, it is not really a project or
> team. Just someone scratching their itches.
>
> Any developer can work on anything. It does not have to be a project. If you
> are going to create a project, it should be taken some what seriously and
> reporting should be a part of that. Not to mention should consist of more
> than one. They should be seeking others to be part of the project team. If
> not seeking others, its a solo mission.
>
> Without such reporting from projects how does the Council or anyone have a
> clue what is going on in Gentoo overall? Short of stopping by each project
> and doing research into each.
>
> That said, NOTHING in the GLEP says projects are punished or dis-banned for
> failing to report. Developers are required, or recommended to use repoman.
> Does that mean someone who does not is removed as a developer?
>
> At the same time Council should have authority and reason to end a project
> it if is not going anywhere, understaffed, etc. Again not having a project
> does not mean you cannot work on that stuff. So a project and the work an
> individual is doing is not related. If its individuals, plural, then a
> project make sense.
We are not a company.
Best regards,
Johannes
next prev parent reply other threads:[~2017-01-19 20:49 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 [this message]
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
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=1937299.r3ENHUtASn@rioja \
--to=johu@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