From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EdaBE-0007qM-UR for garchives@archives.gentoo.org; Sat, 19 Nov 2005 21:23:29 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAJLMkBl024129; Sat, 19 Nov 2005 21:22:46 GMT Received: from centrmmtao03.cox.net (centrmmtao03.cox.net [70.168.83.81]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAJLL0BC028141 for ; Sat, 19 Nov 2005 21:21:01 GMT Received: from [10.3.1.3] (really [68.102.201.166]) by centrmmtao03.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051119211935.VXHO21645.centrmmtao03.cox.net@[10.3.1.3]> for ; Sat, 19 Nov 2005 16:19:35 -0500 Message-ID: <437F9739.4060501@gentoo.org> Date: Sat, 19 Nov 2005 15:20:57 -0600 From: Lance Albertson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Email subdomain References: <1132333748.8524.9.camel@localhost> <200511182022.00662.cshields@gentoo.org> <437EAABE.5050502@gentoo.org> <200511182042.30961.cshields@gentoo.org> <437F93A3.9080808@gentoo.org> In-Reply-To: <437F93A3.9080808@gentoo.org> X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFF24C5D77BF4045070C8AC37" X-Archives-Salt: 8b6a4f7a-895c-4deb-9658-544aaf7d61ec X-Archives-Hash: 900028258dd5eb33170edda11472cb6d This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFF24C5D77BF4045070C8AC37 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Danny van Dyk wrote: > Please have a look at the council's meeting log. They said: > a) the changes had been minor and exactly what the changes they wanted > in in the first meeting. Minor? What you're asking for will cause a lot of administrative nightmare for infra to manage those subdomain addresses among other things. I would have preferred that the people involved with this could have directly asked infra if this would work for us. That's a simple request that I did not see from these folks. > b) they stated that this is the first and the last time that a GLEP will > be voted on if that hasn't been discussed sufficiently long enough on -dev Good, so lets please fix this current GLEP before we implement it. I don't like the answer of "they voted on it, so do it". To me, they voted upon it without following their new mandate on discussion of GLEPs before the meeting. The whole point of GLEPs is discussion to make sure we don't make mistakes, especially if revisions were made. Just because it follows the mandates of what the council wanted doesn't mean it shouldn't be discussed again on -dev. I trust the council's decisions and commonsense, but there still needs to be input from the masses to ensure details are worked out BEFORE they are voted upon. Simply saying "we'll have a subdomain for new email addresses" without asking infra about it first negates the vote in my eyes because we weren't properly involved in the discussion process which was skipped for the revision. We're the ones that will be put on the task to implement it, yet never got any direct input from the people who wrote this GLEP. > c) that new limitations for a vote are: send (revised) glep to > gentoo-dev (at least) 14 days before the next council meeting, ask (at > least) 7 days before the meeting for vote. (For this you can also read > seemants mail announcing the availability of the logs) Great, so lets negate the vote and do the right thing for this current GLEP. I don't see the point of letting this one pass by especially since the GLEP folks even said themselves they could wait. All I'm after is doing this the right way instead of shoving it under a table and just forcing the issue. I would prefer this be corrected as stated above with proper discussion instead of saying that its already be decided on so do it. Can some of the council members please comment on this? I'm curious their thoughts on this. Maybe I'm just barking up the wrong tree, I just see this as a terrible miscommunication between the GLEP authors, the council, and infra. The council and GLEP authors were in line, but weren't in line with infra. I would just like the vote to be reconsidered or postponed until we properly come up with a logistical solution that will work for infra. -- Lance Albertson Gentoo Infrastructure | Operations Manager --- GPG Public Key: Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net --------------enigFF24C5D77BF4045070C8AC37 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDf5c5QW+hXSf0t0IRAitpAJ9ad83+/u2iLmBpuJ07LN+1JDf/OQCaAv2p 9pcktoGgUyeYEluXZDbSwQI= =MmQD -----END PGP SIGNATURE----- --------------enigFF24C5D77BF4045070C8AC37-- -- gentoo-dev@gentoo.org mailing list