Re: [gentoo-dev] gentoo-dev-announce list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec Warner wrote: I vote no, because someone has to. -Alec PS: Thanks to be keeping the packages in the tree up to date. So that's only one negative vote :) and others IIRC positive. Time to fill some infra bug until it's forgotten again? Or do we need a GLEP and/or council approval? (just kidding) ((hopefully)) - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGfmeVtbrAj05h3oQRAuQLAKCT7ePtnoD3mUW+y1H/eDIJc4x9mQCeM9vO 19m8qWAuAiF/WN9Q5HMyzNk= =Y0o3 -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
I vote no, because someone has to. -Alec PS: Thanks to be keeping the packages in the tree up to date. On 6/22/07, Wernfried Haas [EMAIL PROTECTED] wrote: I think the council discussed/decided something about mailing lists in their last meeting, there doesn't seem to be a log/summary out though. cheers, Wernfried -- Wernfried Haas (amne) - amne (at) gentoo.org Gentoo Forums - http://forums.gentoo.org forum-mods (at) gentoo.org #gentoo-forums (freenode) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Seemant Kulleen wrote: FWIW, I like this idea a lot. A lot of devs would rather just read the good stuff happening in -dev and discard the other 85%. I vote yes. Thanks, Seemant +1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGe5VmdXakryvz8lgRApFRAJ4y1oCPSdwqYOr6XKJ/YEQQ3Hpo7QCfS5Yb vlEwq4uGXS7u5/s3/cP6s6I= =Hck1 -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
On Thu, 2007-06-21 at 20:02 -0700, Daniel Ostrow wrote: On Thu, 2007-06-21 at 14:09 -0700, Donnie Berkholz wrote: Hi all, I'm back for my yearly posting about creating a gentoo-dev-announce list [1]. Fedora recently created a fedora-devel-announce list with a great description of how it works, what's posted to it, etc [2], which got me excited about making this happen in Gentoo. Last time the issue came up, numerous people supported it, but nobody followed through to get the list created. This time, I'm going to file a bug to the infra team to make it happen. What's this mean for you? If you want to ignore -dev, you can just subscribe to -dev-announce. But you will lose your ability to participate in discussions leading toward decisions. If you have an announcement relevant to development, post it to both -dev and -dev-announce. Replies will go only to -dev. Can I get an 'AMEN'! Sure --- AMEN I like it. ++ ++ ++ some more ... oh and ++ --Dan -- Ferris McCormick (P44646, MI) [EMAIL PROTECTED] Developer, Gentoo Linux (Devrel, Sparc) signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
I think the council discussed/decided something about mailing lists in their last meeting, there doesn't seem to be a log/summary out though. cheers, Wernfried -- Wernfried Haas (amne) - amne (at) gentoo.org Gentoo Forums - http://forums.gentoo.org forum-mods (at) gentoo.org #gentoo-forums (freenode) pgpeeL21EhRFt.pgp Description: PGP signature
Re: [gentoo-dev] gentoo-dev-announce list
Donnie Berkholz wrote: Hi all, I'm back for my yearly posting about creating a gentoo-dev-announce list [1]. Fedora recently created a fedora-devel-announce list with a great description of how it works, what's posted to it, etc [2], which got me excited about making this happen in Gentoo. Last time the issue came up, numerous people supported it, but nobody followed through to get the list created. This time, I'm going to file a bug to the infra team to make it happen. What's this mean for you? If you want to ignore -dev, you can just subscribe to -dev-announce. But you will lose your ability to participate in discussions leading toward decisions. If you have an announcement relevant to development, post it to both -dev and -dev-announce. Replies will go only to -dev. Thanks, Donnie 1. http://archives.gentoo.org/gentoo-dev/msg_136761.xml 2. https://www.redhat.com/archives/fedora-devel-announce/2007-June/msg0.html or you could ask infra to work it's magic making any post to -dev-announce post to -dev as well and set the replt-to address for -dev-announce to -dev. that way it's all automagic. --taco -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
Mike Doty wrote: or you could ask infra to work it's magic making any post to -dev-announce post to -dev as well and set the replt-to address for -dev-announce to -dev. that way it's all automagic. I hope you meant the List-Post header... unless we would like to have another discussion on the merits/evils of reply-to munging :) -- Jim Ramsay Gentoo/Linux Developer (rox,gkrellm) signature.asc Description: PGP signature
Re: [gentoo-dev] gentoo-dev-announce list
Jim Ramsay wrote: Mike Doty wrote: or you could ask infra to work it's magic making any post to -dev-announce post to -dev as well and set the replt-to address for -dev-announce to -dev. that way it's all automagic. I hope you meant the List-Post header... unless we would like to have another discussion on the merits/evils of reply-to munging :) As an announce list, you're NEVER EVER supposed to reply to the list, so reply-to munging in this case is appropriate IMO. --taco -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
This sounds promising. One problem I see, however, is that this would require announcements to get posted to *both* lists and for people to remember this rule. Posting only to -dev, of course, makes sense, but posting only to -dev-announce would cause strangeness (as all devs who want more mail would miss these mails and end up *not* getting all of the mail). There are two ways around this: 1) Make -dev-announce an umbrella list that always goes to both lists (this can be done by having two sublists - each dev subscribes to one or the other, depending on preference, but not directly to -dev-announce; or it can be done by having -dev-announce include the [EMAIL PROTECTED] address plus the individuals who only want announcements). 2) Mailman has a feature called topics. It can be set up so that each subscriber can set whether they want to only get announcements or get all messages. Posters wanting to hit everyone put a keyword in the subject like Announce: Not sure if the mlm users here has such a feature. I've done it both ways, and there are pros and cons. Just be wary of having the requirement that announcements are sent to both lists by the sender in order for the system to work right. -Joe . Donnie Berkholz wrote: Hi all, I'm back for my yearly posting about creating a gentoo-dev-announce list [1]. Fedora recently created a fedora-devel-announce list with a great description of how it works, what's posted to it, etc [2], which got me excited about making this happen in Gentoo. Last time the issue came up, numerous people supported it, but nobody followed through to get the list created. This time, I'm going to file a bug to the infra team to make it happen. What's this mean for you? If you want to ignore -dev, you can just subscribe to -dev-announce. But you will lose your ability to participate in discussions leading toward decisions. If you have an announcement relevant to development, post it to both -dev and -dev-announce. Replies will go only to -dev. Thanks, Donnie 1. http://archives.gentoo.org/gentoo-dev/msg_136761.xml 2. https://www.redhat.com/archives/fedora-devel-announce/2007-June/msg0.html -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
Mike Doty wrote: Jim Ramsay wrote: Mike Doty wrote: or you could ask infra to work it's magic making any post to -dev-announce post to -dev as well and set the replt-to address for -dev-announce to -dev. that way it's all automagic. I hope you meant the List-Post header... unless we would like to have another discussion on the merits/evils of reply-to munging :) As an announce list, you're NEVER EVER supposed to reply to the list, so reply-to munging in this case is appropriate IMO. Reply-To is supposed to let you reply to the author, in case they need to use a different return address than what is in the From header. Which I grant is very rare for Gentoo developers. But I do agree with you that if reply-to munging is done it should indeed point at -dev and never the -announce list. -- Jim Ramsay Gentoo/Linux Developer (rox,gkrellm) signature.asc Description: PGP signature
Re: [gentoo-dev] gentoo-dev-announce list
On Thu, 2007-06-21 at 14:37 -0700, Mike Doty wrote: Jim Ramsay wrote: Mike Doty wrote: or you could ask infra to work it's magic making any post to -dev-announce post to -dev as well and set the replt-to address for -dev-announce to -dev. that way it's all automagic. I hope you meant the List-Post header... unless we would like to have another discussion on the merits/evils of reply-to munging :) As an announce list, you're NEVER EVER supposed to reply to the list, so reply-to munging in this case is appropriate IMO. Correct. This actually *is* a good case for it, but, as you said, List-Post is probably still better, if it weren't for some very popular clients have abysmal list support. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
Donnie Berkholz wrote: Hi all, I'm back for my yearly posting about creating a gentoo-dev-announce list [1]. Fedora recently created a fedora-devel-announce list with a great description of how it works, what's posted to it, etc [2], which got me excited about making this happen in Gentoo. Last time the issue came up, numerous people supported it, but nobody followed through to get the list created. This time, I'm going to file a bug to the infra team to make it happen. What's this mean for you? If you want to ignore -dev, you can just subscribe to -dev-announce. But you will lose your ability to participate in discussions leading toward decisions. If you have an announcement relevant to development, post it to both -dev and -dev-announce. Replies will go only to -dev. Thanks, Donnie 1. http://archives.gentoo.org/gentoo-dev/msg_136761.xml 2. https://www.redhat.com/archives/fedora-devel-announce/2007-June/msg0.html ++ here. Heck, I'm aiming for a -project list, and I see benefits in this too (details of reply-to munging discussions aside). So what's the harm in subscribing to a few more MLs? --Kumba -- Gentoo/MIPS Team Lead Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere. --Elrond -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo-dev-announce list
FWIW, I like this idea a lot. A lot of devs would rather just read the good stuff happening in -dev and discard the other 85%. I vote yes. Thanks, Seemant signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
On Thu, 2007-06-21 at 14:09 -0700, Donnie Berkholz wrote: Hi all, I'm back for my yearly posting about creating a gentoo-dev-announce list [1]. Fedora recently created a fedora-devel-announce list with a great description of how it works, what's posted to it, etc [2], which got me excited about making this happen in Gentoo. Last time the issue came up, numerous people supported it, but nobody followed through to get the list created. This time, I'm going to file a bug to the infra team to make it happen. What's this mean for you? If you want to ignore -dev, you can just subscribe to -dev-announce. But you will lose your ability to participate in discussions leading toward decisions. If you have an announcement relevant to development, post it to both -dev and -dev-announce. Replies will go only to -dev. Can I get an 'AMEN'! ++ ++ ++ some more ... oh and ++ --Dan signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
On 6/25/06, Donnie Berkholz [EMAIL PROTECTED] wrote: This topic has come up in the past, and I'd like to revive it once again. The gentoo-dev list has gotten a lower and lower signal to noise ratio over the past year or two, and it's difficult to dig out the stuff that's truly required reading. What's noise to you is signal to others. For example, my interest is servers, so all of your X.org posts are mostly noise to me, but to others it's essential signal. Same goes for the scientific re-org recently discussed. And I'm sure the same goes for PHP webapp stuff. I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. I think a -dev-announce ML is a good idea, with reply-to set to -dev. But I also think you're over-exaggerating the situation by a long way, sorry. Best regards, Stu -- PS: If anyone needs anything posting on -announce, I'm one of the people you can bribe :) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
* Stuart Herbert [EMAIL PROTECTED] schrieb: On 6/25/06, Donnie Berkholz [EMAIL PROTECTED] wrote: This topic has come up in the past, and I'd like to revive it once again. The gentoo-dev list has gotten a lower and lower signal to noise ratio over the past year or two, and it's difficult to dig out the stuff that's truly required reading. What's noise to you is signal to others. For example, my interest is servers, so all of your X.org posts are mostly noise to me, but to others it's essential signal. Same goes for the scientific re-org recently discussed. And I'm sure the same goes for PHP webapp stuff. ACK. So it seems more worth, splitting off several larger topics, ie. X.org development to separate lists, or even better discuss things that are not really gentoo specific (ie. bug-fixing within the package) on the upstream's list(s). (At this point, I'd like to remind you on my distro independent QM project ...) I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. I think a -dev-announce ML is a good idea, with reply-to set to -dev. ACK. Such an list could be useful. *BUT*: it doesn't make any sense just talking about it. Simply do it or forget it. Only talking is nonsense. If I was admin @gentoo.org, I would have set it up even before writing this mail. cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49 174 7066481 - -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops -- - -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
Stuart Herbert wrote: But I also think you're over-exaggerating the situation by a long way, sorry. I don't think so. As I understand it, it's not the amount of threads that makes the noise, it's mainly all the sub-sub-sub-sub-threads. -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
Lance Albertson wrote: I'd rather not create a -core-announce. The amount of times those types of things come up on the list are rare. It would be easier to have an standard subject heading (maybe ANNOUNCEMENT:) that people can use in their filters. If devs start abusing it, then we'll vote them off the island :) Bad idea, IMHO. That people are unable to change the subject line even when we're no longer discussing an upcoming project but choice of pet doesn't have to be proved again. Please, create a seperate announcement list, it would make things helluvalot nicer. -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
On 6/27/06, Enrico Weigelt [EMAIL PROTECTED] wrote: (At this point, I'd like to remind you on my distro independent QM project ...) Never heard of it, sorry. *BUT*: it doesn't make any sense just talking about it. Simply do it or forget it. Only talking is nonsense. If I was admin @gentoo.org, I would have set it up even before writing this mail. That's not the way we like to do things, when they affect all of our developers. We prefer to sound out opinion first before acting. Best regards, Stu -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
On 6/27/06, Simon Stelling [EMAIL PROTECTED] wrote: I don't think so. As I understand it, it's not the amount of threads that makes the noise, it's mainly all the sub-sub-sub-sub-threads. As long as they're about Gentoo, they're not 'noise' to everyone. I confess I don't read every email on -dev, but I haven't seen all that many emails that are completely off-topic. Best regards, Stu -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
On Mon, 2006-06-26 at 13:10 -0700, Donnie Berkholz wrote: Chris Gianelloni wrote: - Create a new list (gentoo-core-announce ?) Reading: dev-only Posting: dev-only, reply-to set to gentoo-core This is the reference list of things (policy, decisions and discussions in progress) all developers must know about. Agree with -(core|dev)-announce. - Keep -core and -dev, as non-required reading Agree, but with the caveat that devs must still be at least subscribed to -core even if they choose not to read it. This way, you could have a -dev-announce that also refers to something private on -core if need be. Now, do we really need it to be -core-announce? Not really. In fact, at one point we'd come up with both a -core-announce and a -dev-announce, with -core-announce being for more sensitive information. I'm having a tough time thinking of sensitive information that all devs must know about (i.e., that would qualify for -core-announce). Same here, which was why we eventually dropped to only a single announce list in our discussions. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
Stuart Herbert wrote: On 6/25/06, Donnie Berkholz [EMAIL PROTECTED] wrote: This topic has come up in the past, and I'd like to revive it once again. The gentoo-dev list has gotten a lower and lower signal to noise ratio over the past year or two, and it's difficult to dig out the stuff that's truly required reading. What's noise to you is signal to others. For example, my interest is servers, so all of your X.org posts are mostly noise to me, but to others it's essential signal. Same goes for the scientific re-org recently discussed. And I'm sure the same goes for PHP webapp stuff. Exactly. More stuff you don't care about is more noise. I agree with that too. Rather than reading 50 posts about X crap, wouldn't you rather just look at a single announcement? I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. I think a -dev-announce ML is a good idea, with reply-to set to -dev. But I also think you're over-exaggerating the situation by a long way, sorry. I'm glad you have your opinion. I don't have the time to sit and browse through all the arguments between 2-3 people that go on for 50-100 posts or more as they fall more and more off-topic, so I would like to know if there's any conclusion without wasting my time on that. My options are either missing important announcements or creating this list. I would prefer the list. Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo-dev-announce list
On Sun, 2006-06-25 at 05:54 +0200, Marius Mauch wrote: On Sat, 24 Jun 2006 22:30:31 -0500 Lance Albertson [EMAIL PROTECTED] wrote: Donnie Berkholz wrote: I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. Hopefully, this will also help to give more focus to discussions on gentoo-dev because the goal will be to get a real decision to send to gentoo-dev-announce. Outside if this being more centered around dev-only announcements, could the current -announce list suffice? I'd hate to need to subscribe to yet-another-announcement-list (or make our developers/users). Our -announce list certainly has the historical presence where the most of our user-base would see something. I guess if this isn't the case, then I don't see a problem with the new list. The main problem with -announce is that noone has a clue how to get stuff posted there, similar situation as with the frontpage. Not really convenient if you have to bug people just to get a hint who to bribe to get stuff posted. If you need something posted somewhere, bug PR. Even if they don't have access or don't know who needs to do what, we'll find out. It's really our job to know who does this stuff, and it means we'll know for the next time someone asks. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
On Sat, 2006-06-24 at 22:38 -0700, Donnie Berkholz wrote: Ned Ludd wrote: I would be in favor of a gentoo-dev-announce list if it allowed me to unsubscribe from this list. Sure, if you want to just accept any decisions rather than participate in making them. The -dev-announce list should be for finalized decisions. It should be too late to dispute them once they're sent to it. For important discussions, it may be worth announcing that they're starting -- e.g., for a GLEP -- so people could then be sure to pay attention to that discussion on -dev. At one point, a long time ago, a few of us had actually started discussing a mailing list reorganization. It somewhat died out simply because we didn't keep up with it. However, it went something like this: - Create a new list (gentoo-core-announce ?) Reading: dev-only Posting: dev-only, reply-to set to gentoo-core This is the reference list of things (policy, decisions and discussions in progress) all developers must know about. - Keep -core and -dev, as non-required reading - Confirm the role of gentoo-announce as the official reference list of things all users must know about (especially difficult upgrades just before they reach stable). Posting is moderated. Now, do we really need it to be -core-announce? Not really. In fact, at one point we'd come up with both a -core-announce and a -dev-announce, with -core-announce being for more sensitive information. Some other ideas that were tossed about was changing gentoo-announce into gentoo-security-announce (since it is currently GLSA-only, really) with reply-to set to gentoo-security and create a gentoo-user-announce with reply-to set to gentoo-user, where we would put more information, such as the information that would be given via the portage tree in GLEP42. However, it was also brought up that anyone interested in security is probably also interested in things that might break their system (heh) so instead of splitting it to two lists, it would remain a single list. As you can guess, we never got around to actually writing up a GLEP for this or anything. We didn't reach any kind of impasse, we just quit working on it. I just thought I would pass this along so people know what was discussed previously and would also like to apologize for being one of the slackers who let this die a while back without so much as sending it to the list for discussion. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo-dev-announce list
Chris Gianelloni wrote: - Create a new list (gentoo-core-announce ?) Reading: dev-only Posting: dev-only, reply-to set to gentoo-core This is the reference list of things (policy, decisions and discussions in progress) all developers must know about. Agree with -(core|dev)-announce. - Keep -core and -dev, as non-required reading Agree, but with the caveat that devs must still be at least subscribed to -core even if they choose not to read it. This way, you could have a -dev-announce that also refers to something private on -core if need be. Now, do we really need it to be -core-announce? Not really. In fact, at one point we'd come up with both a -core-announce and a -dev-announce, with -core-announce being for more sensitive information. I'm having a tough time thinking of sensitive information that all devs must know about (i.e., that would qualify for -core-announce). Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo-dev-announce list
Donnie Berkholz wrote: Agree, but with the caveat that devs must still be at least subscribed to -core even if they choose not to read it. This way, you could have a -dev-announce that also refers to something private on -core if need be. Now, do we really need it to be -core-announce? Not really. In fact, at one point we'd come up with both a -core-announce and a -dev-announce, with -core-announce being for more sensitive information. I'm having a tough time thinking of sensitive information that all devs must know about (i.e., that would qualify for -core-announce). I'd rather not create a -core-announce. The amount of times those types of things come up on the list are rare. It would be easier to have an standard subject heading (maybe ANNOUNCEMENT:) that people can use in their filters. If devs start abusing it, then we'll vote them off the island :) -- Lance Albertson [EMAIL PROTECTED] Gentoo Infrastructure | Operations Manager --- GPG Public Key: http://www.ramereth.net/lance.asc Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo-dev-announce list
Donnie Berkholz wrote: I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. Hopefully, this will also help to give more focus to discussions on gentoo-dev because the goal will be to get a real decision to send to gentoo-dev-announce. Outside if this being more centered around dev-only announcements, could the current -announce list suffice? I'd hate to need to subscribe to yet-another-announcement-list (or make our developers/users). Our -announce list certainly has the historical presence where the most of our user-base would see something. I guess if this isn't the case, then I don't see a problem with the new list. -- Lance Albertson [EMAIL PROTECTED] Gentoo Infrastructure | Operations Manager --- GPG Public Key: http://www.ramereth.net/lance.asc Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo-dev-announce list
On Sat, 2006-06-24 at 20:06 -0700, Donnie Berkholz wrote: This topic has come up in the past, and I'd like to revive it once again. The gentoo-dev list has gotten a lower and lower signal to noise ratio over the past year or two, and it's difficult to dig out the stuff that's truly required reading. I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. Hopefully, this will also help to give more focus to discussions on gentoo-dev because the goal will be to get a real decision to send to gentoo-dev-announce. I would be in favor of a gentoo-dev-announce list if it allowed me to unsubscribe from this list. -- Ned Ludd [EMAIL PROTECTED] Gentoo Linux -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] gentoo-dev-announce list
Marius Mauch wrote: On Sat, 24 Jun 2006 22:30:31 -0500 Lance Albertson [EMAIL PROTECTED] wrote: Donnie Berkholz wrote: I propose that all need-to-know announcements and decisions be posted to a separate, moderated (or restricted posting) gentoo-dev-announce list to ensure that no developers lose track of what really matters. Hopefully, this will also help to give more focus to discussions on gentoo-dev because the goal will be to get a real decision to send to gentoo-dev-announce. Outside if this being more centered around dev-only announcements, could the current -announce list suffice? I'd hate to need to subscribe to yet-another-announcement-list (or make our developers/users). Our -announce list certainly has the historical presence where the most of our user-base would see something. I guess if this isn't the case, then I don't see a problem with the new list. The main problem with -announce is that noone has a clue how to get stuff posted there, similar situation as with the frontpage. Not really convenient if you have to bug people just to get a hint who to bribe to get stuff posted. Those are issues that can be delt with. I wondered if this was one of the reasons behind the idea. If we need to work out a better process, just let us know :) I don't recall someone asking us lately about it. I don't know all the specifics, but I know we can fix it or make it work. -- Lance Albertson [EMAIL PROTECTED] Gentoo Infrastructure | Operations Manager --- GPG Public Key: http://www.ramereth.net/lance.asc Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo-dev-announce list
Ned Ludd wrote: I would be in favor of a gentoo-dev-announce list if it allowed me to unsubscribe from this list. Sure, if you want to just accept any decisions rather than participate in making them. The -dev-announce list should be for finalized decisions. It should be too late to dispute them once they're sent to it. For important discussions, it may be worth announcing that they're starting -- e.g., for a GLEP -- so people could then be sure to pay attention to that discussion on -dev. Thanks, Donnie signature.asc Description: OpenPGP digital signature
