Alfred Perlstein <[EMAIL PROTECTED]> writes:
> If this is how the rest of the CVS developers feel then...
>
> Action should be taken to ensure that Greg Woods doesn't continue
> to mis-represent the project as a whole and developers should keep
> a bit closer tabs on the lists to ensure that this sort of thing
> doesn't happen in the future.
Why? Greg Woods is not misrepresenting anyone -- his posts reflect
only his own opinions, and since this is an unmoderated list, no one
has any right to stop him from posting. You can filter out his posts
automatically, if you want.
This is not a developer's list. There is a developer's list, but it
hasn't (for a long time) been open to the public. Frankly, I'm not
sure it's good that it be invisible to the user community, but at
least this way traffic is low, posts are to the point, and there are
no time-wasting flamewars on it.
> Basically, if this is the official CVS list, then a real developer
> presense is nessesary, maybe not to answer questions, but to make
> sure that people have the right kind of idea about your project.
This is not the "official CVS list" in any sense except that it is
designated for posts (from anyone on the Internet) related to CVS.
There is deliberately no quality control of any sort.
> If it's the opinion that the list has 'degraded' over the last
> couple of months, then steps should be taken that _official and
> active_ CVS developers attempt to occasionally stick thier heads
> into the fray to correct people that are fostering false representation
> of the CVS project's goals.
Well, that was only _my_ opinion, Your Mileage May Vary.
The *really* active developers (say, Larry Jones) are too busy fixing
bugs to make corrective posts to this list. :-) I haven't done much
with CVS for a while, but here I am sticking my head in as you
requested -- instead of working on CVS tonight.
See the problem? :-)
> Basically, if this is the official CVS list, then a real developer
> presense is nessesary, maybe not to answer questions, but to make
> sure that people have the right kind of idea about your project.
If anyone here knows what the "right kind of idea" about CVS is, I
hope they'll tell me. I certainly don't know, heh...
> If certain parts of the system are officially broken, and have been
> broken for AT LEAST A YEAR then action needs to be taken to either
> officially mark them as 'broken' or remove them entirely, so that
> they don't sit there as potential traps for the unwary!
>
> Either
> a) fix it.
> b) mark it as broken.
> b) chop it out.
> c) allow patches to go in to address it.
As far as I know, everything that is broken is so marked in the
manual. If you know of something that's undeclaredly broken, please
submit a bug report and a documentation patch to [EMAIL PROTECTED] --
doc patches tend to get applied pretty quickly.
> Stop letting this junk stagnate.
>
> I appreciate your effort with trying to clear things up for me, it seems
> there's a lot of work involved to get things back on track.
>
> best of luck,
> -Alfred
My final post on this subject, I promise. Alfred, the last word is
yours if you want it,
Best,
-Karl
