From: Patrick McLean <chutzpah@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 15:24:23 -0800 [thread overview]
Message-ID: <20170119152345.2482018c@patrickm> (raw)
In-Reply-To: <assp.0192c6e541.46431746.K7Gl2XPWsO@wlt>
On Thu, 19 Jan 2017 17:50:38 -0500
"William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> > All my framing concerns itself with is assigning the responsibility
> > for this interaction towards the recipient, and making it clear
> > from the nature of the interaction that feedback is regularly
> > wanted, but not mandatory.
>
> I am suggesting projects should have a mandatory requirement to
> provide monthly status. If they meet, they have this already in any
> minutes or log. May require a summation. If they do not meet, someone
> can gather the info up to each project/team. It would take
> considerably less time for someone on the project/team to provide a
> summary. Than for another person to come poll each person in the team
> for the same information. It will take less time to come from within.
This is an all volunteer organization, we should refrain from making
any sort of regular "mandatory" actions. Since no one is paid, we can't
have any specific expectations of when people have time to spend on
Gentoo. I would also have someone with limited time spending their time
working on bugs etc rather than writing a monthly report.
Even at companies, where people are paid to work, engineers are not
generally expected to provide status reports to management. That is
generally the job of a _paid_ project manager or _paid_ manager.
next prev parent reply other threads:[~2017-01-19 23:24 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 [this message]
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=20170119152345.2482018c@patrickm \
--to=chutzpah@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