Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Mon, May 15, 2000 at 09:21:54PM -0700, Jordan K. Hubbard wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? I think it's a genuinely stupid idea. It was sufficiently stupid that my previously stated opinion on the topic was in anger so hastily written and fired-off that only its immediate target understood quite how rude I was being, rather than the broad audience I had been hoping for. -- Signature withheld by request of author. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
"Jordan K. Hubbard" wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? I think it's a genuinely stupid idea. - Jordan I nominate HIM to be the keeper of the funds. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
Darren Reed wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? Isn't this the "FreeBSD" project ? There is no such thing as a "free beer". -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "I agree whole heartily! Who am I to disagree with a wacko like you?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
Darren Reed wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? Isn't this the "FreeBSD" project ? There is no such thing as a "free beer". If there are enough bad committs, we can start thinking in terms of parties with Free Beer and Pizza 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? I think it's a genuinely stupid idea. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Sun, May 14, 2000 at 10:19:21AM +0930, Greg Lehey wrote: I'd go along with that. What do the other committers think? Can I drink pop instead? I'm underage, and I don't like alcohol anyway. :) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Sun, May 14, 2000 at 11:06:50AM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Greg Lehey writes: : Maybe the comitters ought to take an idea from many software companies and : contribute $5 to the beer fund every time they break the build. Have it : all come due at the next BSDcon to fund a committer beer bash. :-) I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. I think this'd be a great idea, provided we also implemented some sort of scheme that paid for committer time that was wasted as a result of reading needless crossposts that add little to one of the lists and nothing to the other. -- Signature withheld by request of author. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
In some email I received from Greg Lehey, sie wrote: On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote: On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. Or perhaps we should tie it to the time it takes the security officer to fix, either with his own patches or by inviting patches from others, security holes that have been reported in certain libraries. If it takes the committer longer to fix the world breakage than it takes the security officer to deal with the hole, then the committer may be fined. In all other cases, the security officer can be fined. At committer's discretion. We can then add bonuses. Say, for example, I fix someone else's world breakage fast enough that they are able to avoid the fine, then they have to pay me either $5.00, $10, or $20. In cases where more than one committer was responsible, either indirectly or directly, then all involved should be fined. I think you're missing the point. The intention was the equivalent of the pointy hat, just with the additional benefit that others might have something out of it as well, no more. Just one other thing to add here... How often is it that the actions of just one person make the build fail ? I imagine if one person commits code, it works and bulids cleanly for them, but it's when it's imported into a source tree that others have changed that the previous compile-testing can be rendered useless. If anything, such moves as this will make people less likely to commit code and hence further impede the development of FreeBSD. I know I personally do not have the resources (both physical and otherwise) to maintain a FreeBSD-current system to test any change I might want to commit. I see this money scheme as an extension of the "finger pointing" which does nothing to build team spirit. Darren p.s. since there was no currency specified, I imagine "$5 local", wherever that maybe, so the Italians would get off light at 5Lire :) p.p.s. for those of you that live inside the USA, sending such small amounts of money to the USA will cost more than the penalty, more than likely. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
In message [EMAIL PROTECTED] Greg Lehey writes: : Maybe the comitters ought to take an idea from many software companies and : contribute $5 to the beer fund every time they break the build. Have it : all come due at the next BSDcon to fund a committer beer bash. :-) : : I'd go along with that. What do the other committers think? I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. BTW, if the committer fixes this before N amount of time has passwed (say an hour or two), then there should be no fine. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. Or perhaps we should tie it to the time it takes the security officer to fix, either with his own patches or by inviting patches from others, security holes that have been reported in certain libraries. If it takes the committer longer to fix the world breakage than it takes the security officer to deal with the hole, then the committer may be fined. In all other cases, the security officer can be fined. At committer's discretion. We can then add bonuses. Say, for example, I fix someone else's world breakage fast enough that they are able to avoid the fine, then they have to pay me either $5.00, $10, or $20. In cases where more than one committer was responsible, either indirectly or directly, then all involved should be fined. -- Signature withheld by request of author. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Monday, 15 May 2000 at 13:48:19 +1000, Darren Reed wrote: In some email I received from Greg Lehey, sie wrote: On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote: On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. Or perhaps we should tie it to the time it takes the security officer to fix, either with his own patches or by inviting patches from others, security holes that have been reported in certain libraries. If it takes the committer longer to fix the world breakage than it takes the security officer to deal with the hole, then the committer may be fined. In all other cases, the security officer can be fined. At committer's discretion. We can then add bonuses. Say, for example, I fix someone else's world breakage fast enough that they are able to avoid the fine, then they have to pay me either $5.00, $10, or $20. In cases where more than one committer was responsible, either indirectly or directly, then all involved should be fined. I think you're missing the point. The intention was the equivalent of the pointy hat, just with the additional benefit that others might have something out of it as well, no more. Just one other thing to add here... How often is it that the actions of just one person make the build fail ? In nearly every case. I imagine if one person commits code, it works and bulids cleanly for them, but it's when it's imported into a source tree that others have changed that the previous compile-testing can be rendered useless. I'd suggest it's more normally superficial testing. If anything, such moves as this will make people less likely to commit code and hence further impede the development of FreeBSD. I know I personally do not have the resources (both physical and otherwise) to maintain a FreeBSD-current system to test any change I might want to commit. I see this money scheme as an extension of the "finger pointing" which does nothing to build team spirit. That depends very much on the way it's taken. At the moment, people take the pointy hat voluntarily, not because it's forced on them. It's my expectation that the $5 should be in the the same spirit. On Sunday, 14 May 2000 at 23:50:08 -0400, Kent Hauser wrote: Hi all, I think I might have an even better solution. Continue passing the pointy hat around I'll buy the committer's keg at the next BSDcon. I for one appreciate the exceptional funcitionality of FreeBSD (especially the IPSec support). And also, if I buy the key, maybe I'll also be invited. Everybody's invited. And yes, we'll gratefully accept the keg. But that has nothing to do with the original idea :-) Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote: On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I think that we should make it $5.00 the first time. $10 the second time. $20 the third time, etc. Or perhaps we should tie it to the time it takes the security officer to fix, either with his own patches or by inviting patches from others, security holes that have been reported in certain libraries. If it takes the committer longer to fix the world breakage than it takes the security officer to deal with the hole, then the committer may be fined. In all other cases, the security officer can be fined. At committer's discretion. We can then add bonuses. Say, for example, I fix someone else's world breakage fast enough that they are able to avoid the fine, then they have to pay me either $5.00, $10, or $20. In cases where more than one committer was responsible, either indirectly or directly, then all involved should be fined. I think you're missing the point. The intention was the equivalent of the pointy hat, just with the additional benefit that others might have something out of it as well, no more. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? Isn't this the "FreeBSD" project ? Haven't you heard? We renamed it "FreeBeerSD". John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
In some email I received from Greg Lehey, sie wrote: On Saturday, 13 May 2000 at 9:53:40 -0700, Brian W. Buchanan wrote: On Fri, 12 May 2000, Stephen Hocking wrote: For the past few days, current has not compiled, owing to problems (in no particular order) with more, vinum and various INET options in the GENERIC kernel. Can people please check things before they commit them? I like a working compile at least *once* a week. Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? Isn't this the "FreeBSD" project ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
