Date: Sun, 22 Feb 1998 19:44:33 -0500 (EST) From: Chuck Robey <chuckr@glue.umd.edu> To: Greg Lehey <grog@lemis.com> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Nate Williams <nate@mt.sri.com>, Terry Lambert <tlambert@primenet.com>, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Message-ID: <Pine.BSF.3.96.980222193605.14406b-100000@localhost> In-Reply-To: <19980223104605.49121@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Feb 1998, Greg Lehey wrote: > > I think Jordan and Greg both have points they are correct about. What > > about making a web page that the offender gets put on ... nothing > > incredibly horrible, just a rogues gallery (I broke current on 00/00/00 > > with a commit to " ... ". You figure that the list is pretty quickly > > going to get some names on it, so it won't be so embarrassing as to turn > > people off, but most people wouldn't want to show up on it, so they'd > > avoid doing things to get themselves so honored. > > > > Folks like John Dyson would show up a lot ... most of us know why that'd > > be, and I _wouldn't_ want to unduly embarrass John ... but if John could > > take it as sort of a left-handed compliment, it'd probably be a real > > deterrent to most of the rest of us. Think of it as minimal punishment. > > If it turns out to be too negative, a little editing of the web page could > > either soften (or harden) the impact, as needed. > > Hmmm. I think this is a little drastic. I certainly wouldn't > recommend anything unless the person in question is a repeat offender. > And in John's case, as I said before, I don't think he has offended. > There's a difference between committing a file that won't build and > committing a change that causes the VM system to die in certain very > specific circumstances. The reason why I wouldn't want the bar raised for getting on the list is because it would hurt much less if there were 20 other names there to begin with. No particular badge of honor, so folks would avoid it, but neither would one single person look like a complete idiot. I used to care about making mistakes and getting blamed for it, until a New Yorker (I was in LA at the time) started a publicly posted "awshit" list, and added names liberally. Pretty soon, I got over the onus of blame (for which I'm endlessly grateful) but I still made the attempt not to get on the list. Make it hurt less, but make it public (more public and permanent than mailing list flames). I think I'd get on that list, I've broken too many ports. > > > I don't want to be as drastic as I think Greg is proposing, but I think > > ignoring it isn't probably the best way to go either. > > Wait, what are you talking about? OK, maybe it wasn't perfect in reference. 1 awshit. I didn't propose *any* particular > punishment in my suggestion. I'm just trying to find a way to keep > -CURRENT usable at least some of the time by channeling the commits. > I know my suggestion isn't perfect, and the objections people have to > it are valid. I just wish that somebody would come up with something > better. > > Nate (I think) brought up the fact that people can't always commit > when it would be suitable for my model. Would anybody care to think > about a two-phase commit model: commit to the bleeding edge whenever > you want, commit things that roughly work within a week? > > Greg > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980222193605.14406b-100000>