[cowiki-dev] Managing change
Paul Hanchett <[email protected]> Wed, 21 Sep 2005 08:45:37 -0700
| Newsgroups | gmane.comp.php.cowiki.devel |
|---|---|
| Message-ID | <[email protected]> |
--------------030109000903020204090108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Daniel T. Gorski wrote:
>On 20 Sep 17:51, Paul Hanchett wrote:
>
>
>
>>So, when did "Change log" get added to coWiki
>>
>>
>
>Recently.
>
>
>
>>and why?
>>
>>
>
><http://cowiki.tigris.org/issues/show_bug.cgi?id=62>
><http://cowiki.tigris.org/issues/show_bug.cgi?id=157>
>
>
>
>>I understand why a programmer familiar with CVS might want it, but in my
>>opinion *having* to make a change log entry is a pain.
>>
>>
>
>So what now? Should I remove it again?
>
>
>
OK Daniel, so I have three problems here.
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.
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.
You say that I am the Maintainer and should make decisions and get more
people to work on the project, but you do not allow me the respect of
that position. You say that everyone should be able to do what they
want but that is anarchy, not a project.
So how should we resolve this? Am I to be Maintainer and the guiding
force for the project, or will you continue to be undisciplined in your
efforts? I do not see that you can have it both ways, Daniel.
Team, I am serious about this. This project is floundering, partly
because I haven't paid the attention to it that I should. But also
because development efforts are not focused on providing the big
features that coWiki needs to make it competetive in the OSS Wiki
marketplace.
In the spirit of "openness" I have refrained from doing what I could to
keep out changes I haven't approved. I am not anxious to begin now, but
I also do not want *my* name associated with a poor quality product, nor
should you.
Not only do I want to manage allowed changes, but I want us to implement
features that will put coWiki on a par with other projects. (Actually
we will still have a ways to go, but it's a start...) Part of my job is
to represent the needs of the customer to the team. Let me do it!
There are 27 issues listed for Fullerene that need to be addressed. You
can see them here:
http://cowiki.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&component=cowiki&issue_status=NEW&target_milestone=Fullerene_FC&target_milestone=Fullerene&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=List+All+Open+Issues&newqueryname=&order=Reuse+same+sort+as+last+time
<http://cowiki.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&component=cowiki&issue_status=NEW&target_milestone=Fullerene_FC&target_milestone=Fullerene&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=List+All+Open+Issues&newqueryname=&order=Reuse+same+sort+as+last+time>.
Please focus on issues scheduled for this release.
In the future issue numbers in the check-in comments with every update
to CVS. If there is no issue number, I will ask you to revert your
changes. If the issue you have addressed has not been scheduled (by
myself) for the current release, I reserve the right to reject the
change. If you think an existing issue should be added to this list,
let me know and I will consider it. If you find a bug, write it up and
enter it in the issue database for scheduling.
Also, when you fix an issue, please update the status in the issue database!
/Failure to conform to these rules will result in a loss of CVS checkin
rights./
We need to get back on track, folks!
Paul Hanchett
coWiki Maintainer
--------------030109000903020204090108
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="mid20050921140845.GE12122@bantha" type="cite">
<pre wrap="">On 20 Sep 17:51, Paul Hanchett wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So, when did "Change log" get added to coWiki
</pre>
</blockquote>
<pre wrap=""><!---->
Recently.
</pre>
<blockquote type="cite">
<pre wrap="">and why?
</pre>
</blockquote>
<pre wrap=""><!---->
<a class="moz-txt-link-rfc2396E" href="http://cowiki.tigris.org/issues/show_bug.cgi?id=62"><http://cowiki.tigris.org/issues/show_bug.cgi?id=62></a>
<a class="moz-txt-link-rfc2396E" href="http://cowiki.tigris.org/issues/show_bug.cgi?id=157"><http://cowiki.tigris.org/issues/show_bug.cgi?id=157></a>
</pre>
<blockquote type="cite">
<pre wrap="">I understand why a programmer familiar with CVS might want it, but in my
opinion *having* to make a change log entry is a pain.
</pre>
</blockquote>
<pre wrap=""><!---->
So what now? Should I remove it again?
</pre>
</blockquote>
OK Daniel, so I have three problems here.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
<br>
You say that I am the Maintainer and should make decisions and get more
people to work on the project, but you do not allow me the respect of
that position. You say that everyone should be able to do what they
want but that is anarchy, not a project.<br>
<br>
So how should we resolve this? Am I to be Maintainer and the guiding
force for the project, or will you continue to be undisciplined in your
efforts? I do not see that you can have it both ways, Daniel.<br>
<br>
<br>
Team, I am serious about this. This project is floundering, partly
because I haven't paid the attention to it that I should. But also
because development efforts are not focused on providing the big
features that coWiki needs to make it competetive in the OSS Wiki
marketplace.<br>
<br>
In the spirit of "openness" I have refrained from doing what I could to
keep out changes I haven't approved. I am not anxious to begin now,
but I also do not want *my* name associated with a poor quality
product, nor should you. <br>
<br>
Not only do I want to manage allowed changes, but I want us to
implement features that will put coWiki on a par with other projects.
(Actually we will still have a ways to go, but it's a start...) Part
of my job is to represent the needs of the customer to the team. Let
me do it!<br>
<br>
There are 27 issues listed for Fullerene that need to be addressed.
You can see them here: <a
href="http://cowiki.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&component=cowiki&issue_status=NEW&target_milestone=Fullerene_FC&target_milestone=Fullerene&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=List+All+Open+Issues&newqueryname=&order=Reuse+same+sort+as+last+time">http://cowiki.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&comp
onent=cowiki&issue_status=NEW&target_milestone=Fullerene_FC&target_milestone=F
ullerene&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=List+All+Open+Issues&newqueryname=&order=Reuse+same+sort+as+last+time</a>.
Please focus on issues scheduled for this release.<br>
<br>
<font color="#000099">In the future issue numbers in the check-in
comments with every update to CVS. If there is no issue number, I will
ask you to revert your changes. If the issue you have addressed has
not been scheduled (by myself) for the current release, I reserve the
right to reject the change. If you think an existing issue should be
added to this list, let me
know and I will consider it. If you find a bug, write it up and enter
it in the issue database for scheduling. <br>
<br>
Also, when you fix an issue, please update the status in the issue
database!<br>
<br>
<i>Failure to conform to these rules will result in a loss of CVS
checkin rights.</i><br>
</font><br>
We need to get back on track, folks!<br>
<br>
Paul Hanchett<br>
coWiki Maintainer<br>
<br>
</body>
</html>
--------------030109000903020204090108--