Re: Personal Attacks [was Re: ChartTransformer 0.0.4 urge a commiter!]

[Stefano Mazzocchi]

Luca Morandini wrote:

-----Original Message-----
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 3:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Personal Attacks [was Re: ChartTransformer 0.0.4 urge a
commiter!]

You had a wonderful chance to accept Nicola's mistakes, appreciate his
regrets and earn a bunch of community respect by doing so.
Instead, you have choosen to keep beating somebody that admitted his
faults and in such a rude and personal way, with the chance of further
spreading negative energy and thus pollute the entire community with a
potential flamewar.

You're right, I acted recklessly, while at 37 I should have been wiser.

Moreover, I needlessy damaged the community in doing so.

To add insult to injury, I sent the notorious message without consulting Piero De Nicola, hence, indirectly damaging that innocent
man as well.

I should have been much wiser than that... indeed Nirvana is ahead of me :(

Since I hold the view that apologies aren't enough, I will try to repair the damage I've done:

1) Bring the JFreeChartTransformer (aka ChartTransformer) under the aegis of CocoonDev... (provided CocoonDev board accepts it, of
course)

2) Start collaborating with the Wings project on a common XML schema for charts, hence letting the user choose which transformer
suits him/her best (provided, of course, Wings committers agree)

3) Setup a new Cocoon-GIS sub-project in CocoonDev (yes, yes, I'll ask CocoonDev  board first)

4) Donate, to the prospective Cocoon-GIS project (see 3), a transformer to connect Cocoon with ArcIMS, a proprietary web-mapping
package

Do you deem it enough to put the relationship back on course ?

Of course!

But even the first line alone would have done it.

Now that the friction is over, let me talk to you about donations:

1) the LGPL issue is a serious concern in apache-land. while you can disagree with the idea and the social impact, there is nothing *I* can do to change this, the inertia of the concept is *way* more than I can handle.

2) cocoon is too big. we need to factor things out. we need blocks for that. blocks are hard to implement and we must get them incrementally right (see my next mail)

3) code donations will be welcome, even if they duplicate functionality, but only if they are 'helpful' for the community... we might decide to 'route' them somewhere else ('sourceforge' 'cocoondev' 'krysalis' you-name-it) before incorporating them into something released from cocoon.apache.org. This should *NOT* be considered offensive, but a way to protect the community from potentially negative impact (like that one we just experienced)

4) the cocoon PMC will work a politically fair solution for block donation and distribution once the block technology will be in place, this will take a while, though.

5) the line between block and non-block will be thin and easy to cross. Please, don't get upset if you think others have been treated differently, for sure, there is no reason to behave 'coldly' to a code donation on purpose. At the same time, I'll work hard to make sure that no code ownership and ego problems get in our way.

Hope this solves the issue.

Thanks everybody for their patience on this.

--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]