Re: [cowiki-dev] Managing change

Yo people,

The project can only be managed by one person, and that person needs  
to know every single thing that is going on if they are going to be  
responsible.

There's nothing wrong with dtg adding features as he sees fit, just  
don't check them into the main branch so everyone gets them! Branch  
it off!

Paul needs to know what goes on - no one needs surprises ;)

To progress coWiki, there's things that need to be done long before  
features, and one of those is documenting the code - the more people  
understand it, the more likely they'll be developing features for me,  
you, customers, everyone.

cowiki.org - will be upgraded the moment I get the go-ahead from the  
maintainer ;)

vv



On 22 Sep 2005, at 08:09, Hakan Kuecuekyilmaz wrote:

> 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.
>