Re: [cowiki-dev] Managing change

Paul Hanchett <[email protected]> Wed, 21 Sep 2005 23:38:09 -0700
Newsgroups gmane.comp.php.cowiki.devel
Message-ID <[email protected]>
--------------060209090209030107070808
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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


--------------060209090209030107070808
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Daniel T. Gorski wrote:
<blockquote cite="mid20050922031543.GL12122@bantha" type="cite">
  <pre wrap="">On 21 Sep 08:45, Paul Hanchett wrote:

I'll keep it short.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Daniel T. Gorski wrote:
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Syeed was the only massive user, whos experiences mean to me.
  </pre>
</blockquote>
Syeed is *not* a user.&nbsp; He has declaimed any number of times that he is
_not_ using coWiki any more.<br>
<blockquote cite="mid20050922031543.GL12122@bantha" type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The process was not finished yet.
  </pre>
</blockquote>
The change is checked into CVS, the issues are not marked "Started" and
they are assigned to *me* and scheduled for a future release.&nbsp; Your
approach does not reflect the discipline required to build a quality
product.<br>
<blockquote cite="mid20050922031543.GL12122@bantha" type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">You say that I am the Maintainer
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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.
  </pre>
</blockquote>
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.&nbsp; It sounds like you
really just wanted someone else to work so you could make money.&nbsp;
Sorry, that's not me.&nbsp; I have tried to help improve coWiki but I'll
admit I feel unappreciated.<br>
<br>
You don't need to mess things up with another branch.&nbsp; If you want to
be Maintainer, just say so and I'll set you up as owner at tigris.&nbsp;
Have you talked with the rest of the team about it? What do they say?<br>
<br>
Paul<br>
<br>
</body>
</html>

--------------060209090209030107070808--