public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: GLEP - Require Projects to report to Council Monthly
Date: Thu, 19 Jan 2017 16:27:15 -0500	[thread overview]
Message-ID: <assp.01928ded7c.22870030.u6MpjrvfOB@wlt> (raw)
In-Reply-To: <20170120101914.43923e6b@katipo2.lan>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On Friday, January 20, 2017 10:19:14 AM EST Kent Fredric wrote:
> On Thu, 19 Jan 2017 15:47:46 -0500
> 
> "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> >  If it is just one person, it is not really a project or team. Just
> > 
> > someone scratching their itches.
> 
> A project reducing itself to one person is not grounds for dissolution
> of a project.

There is nothing in the GLEP that suggests such. I am not proposing such or 
seeking to even discuss. That would be another GLEP as to rules for formation 
and dissolution of projects. The furthest I went was maybe, for many of the 
reasons you stated. I am simply talking about reporting, not dissolution.

> Not a structure to rap us over the knuckles. ( Though sometimes both
> happens, its important to know which one happens in service of the other )

This has nothing to do with that. It is simply information being disseminate. 
Just like some of what used to be in the GWN.

Example

"Important changes within the Java Project
-----------------------------------------
A number of significant changes have happened within Gentoo's Java team...."
https://archives.gentoo.org/gentoo-gwn/message/
ae1382e71f3d57fd971e004e5950d4d0

-- 
William L. Thomson Jr.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-01-19 21:27 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. [this message]
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=assp.01928ded7c.22870030.u6MpjrvfOB@wlt \
    --to=wlt-ml@o-sinc.com \
    --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