Re: [cowiki-dev] Managing change

Hi,

please guys: calm down a bit. I like the work of Goosh coding coWiki. I 
also like the work of Paul managing the project.

Goosh, we all know, that most of the coding is from you. I like the 
idea to have a maintainer of the project, so the coders can do what 
they really like: write code. Do you want to be involved in every 
feature request issue, in every bug verifying?

If Paul should be the manager of the project, then you Goosh should 
respect his ideas/needs. If he wants changes to be documented, than 
please document it.

Remember, when you wanted transaction support for the database. Paul 
did not liked the idea, but after explaining him the details he was not 
against it anymore.

If you want to ride a one-man-show, than do it. But this is/was a 
project of a group of people. So please consider the efforts of the 
group.


Quoting Paul Hanchett <[email protected]>:

> Daniel T. Gorski wrote:
>
>> On 21 Sep 08:45, Paul Hanchett wrote:
>>
>> I'll keep it short.
>>
>>
>>> Daniel T. Gorski wrote:
>>>
>>
>>
>>> First, the feature is not scheduled for this milestone.  It should 
>>> not have been touched.  There were other features that were more 
>>> important.  By adding an unapproved feature, the usability of 
>>> coWiki has been compromised-- at least for some users.
>>>
>>> Second, we have had no requests for such a feature from users.  Sy 
>>> (originator of the request) is/was a member of the development team 
>>> and was on an idea generating binge.  Such things are useful, but 
>>> descretion needs to be applied to the results.  I marked it for a 
>>> future release (Character) for a reason.
>>>
>>
>> Syeed was the only massive user, whos experiences mean to me.
>>
> Syeed is *not* a user.  He has declaimed any number of times that he 
> is _not_ using coWiki any more.
>
>>
>>> Finally you made a change in functionality/fixed an issue without 
>>> marking it thus in the issue database.  How are we supposed to 
>>> track the changes made to the next release?  This is very important 
>>> for testing and also announcing changes and new features to our 
>>> users.
>>>
>>
>> The process was not finished yet.
>>
> The change is checked into CVS, the issues are not marked "Started" 
> and they are assigned to *me* and scheduled for a future release.  
> Your approach does not reflect the discipline required to build a 
> quality product.
>
>>
>>> You say that I am the Maintainer
>>>
>>
>> Anyway, you did not contributed any code nor functionality. I need to earn
>> money with the software and will branch the CVS for me the next time my
>> customers need a functionality.
>>
> Well, OK-- I've attempted to do exactly what I told you I would do 
> when I became Maintainer, which is to identify a 'market' for coWiki 
> and pursue it; I said I would not contribute much code.  It sounds 
> like you really just wanted someone else to work so you could make 
> money.  Sorry, that's not me.  I have tried to help improve coWiki 
> but I'll admit I feel unappreciated.
>
> You don't need to mess things up with another branch.  If you want to 
> be Maintainer, just say so and I'll set you up as owner at tigris.  
> Have you talked with the rest of the team about it? What do they say?
>
> Paul
>
>


Regards, Hakan
-- 
Hakan Kuecuekyilmaz


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.