[gentoo-dev] Thanks for the rescue! Was: Last rites: net-nntp/inn
Jeroen Roovers posted on Tue, 12 Jan 2010 03:22:05 +0100 as excerpted: net-nntp/inn-2.5.1 is in the tree and fixes many (QA) issues. [ etc] Thanks! =:^) (Not to be an aoler and metoo, but I asked some time ago and the consensus seemed to be that thanks were good even if they meant an extra email or two, and this package is worth it, so... Yes! Thanks!) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
[gentoo-dev] Thanks
My thanks to nattfodd and KingTaco for processing the votes in the recent Trustee election. Thanks also go to Seemant who got the election rolling, agriffis who wrote the votify/countify software and who was nice enough to generate the previous roster of Foundation members, infra who generated a list of eligible voters for the current election, and codergeek42, fmccor, and gustavoz, who are the other election officials (and who, presumably, will be providing independent confirmations of the election results). -g2boojum- -- Grant Goodyear Gentoo Developer [EMAIL PROTECTED] http://www.gentoo.org/~g2boojum GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76 pgp5JW4KI6B1G.pgp Description: PGP signature
Re: [gentoo-dev] Thanks
Ditto :) I'd also like to thank Grant for taking care of the counting etc at the end of the election, and for being my rock in Gentooland. And big thanks to Ciaran for jump-starting the movement to have another round of nominations and elections -- they were certainly successful the second time :) Finally, thanks to all those who stepped up as nominees. Thanks, -- Seemant Kulleen Developer, Gentoo Linux -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Thanks for your feedback
Everybody thanks for the feedback to my GLEP(35). The discussion about it started on 2005/03/13. What I figured out so far is that some proposed changes are already covered in repoman.That is even better because some of the work is already done then. But how come that there are still trivial errors if half of the GLEP is covered and everybody is using repoman? I agree that changes on ebuilds should be done only by the developers. I will change this point in the GLEP. To post errors to a website and send some mails is just a form of implementation that I do not worry about right now. To use both and let dev`s choose from it would be a good thing though. Somebody mentioned that I am not aware of gentoo dev practices. That`s right. I tried to become aware of it but I could not find anything useful. Maybe I have not found the right documents or there are none i.e. I do not want to read portage source to figure out what is going on. Maybe I should also add some motivation why to do this: There have been some talks about bringing Gentoo to the enterprise. For me this is not important and I do not care but this will never work if the quality is not checked at least to some degree. Also I do not like the mentality somebody put up that was like this: I don`t mind fixing wrong URL`s - it is a matter of seconds. If you work for some customer (i.e. gentoo users) and they find simple errors that they might fix by themselves. What might they think ? Why not kill all these errors faster and take upon the hard things? I hat to open a root shell, fix the error, run the command again (find another error ?), start up firefox, login to bugs, check if somebody caught the error, file a bug hope you get the point. It might be possible that i.e. for ONE week one developer is responsible for fixing ALL broken URL`s of all packages (does he really need to know about the ebuild`s content ?). Although I don`t know how many broken URL`s there might be ... Please do not get me wrong like: somebody from outside tries to change the system. I love Gentoo and I think it is a great system but there are things I would like to improve. Adrian Lambeck -- gentoo-dev@gentoo.org mailing list
