Paul this is not a problem. I understand what keith is saying but we have a bootstrap problem: how can people help building better extensions. stef On Feb 12, 2009, at 12:21 PM, Provoost, P (Paul) wrote:
Keith,
I think that you should not raise your voice the way you do in this mailing list. Please don't be rude in this list, it spoils the positive and friendly atmosphere of it. If you want to quarrel with Stef, then please do it in private mails.
Thanks,
Paul
Keith wrote:
You still dont get it do you. *** really look at it *** means pick over the carcass. Adopting it means JOINING IN AND MAKING EVERYTHING BETTER FOR EVERY ONE.
You guys have the expertise to fix things I dont, and test things that I dont. I dont have the skill to meet your high coding standards. I am working on comercial projects and I need something that WORKS not something that looks pretty. I used a code formatter for 6 years, so when I see code I dont see that it needs formatting. It looks ok to me.
If you adopt it, then your whole team of testers and experts get to contribute, and everyone benefits.
The reason I am causing trouble, and raising my voice is not that you wont use my stuff, its that you will not participate in any collaborative attitude AT ALL. Monticello IS NOT YOUR PROJECT, it is EVERYONES. It is the PEOPLES MONTICELLO. Your approach is killing that vision, and taking NEEDED (according to you private emailer) expertise away from that vision.
Keith
p.s. It doesnt matter if the code is crap, un-formatted crap. It cant possibly be worse than MC1.0 and the amount of cruft I refactored.
_____________________________________________________________
This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project