[Compcomm] Forum Decision

[Mike Dransfield]

Kristian Lyngstøl wrote:
> On 5/11/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
>   
>> Ive already seen people upset with changes being made to
>> their plugins/code without their knowledge or approval.
>>     
>
> The fact that I was upset about an update was never related to Danny's
> write access to the project. Because the code was available, he could
> port my plugins. If my work wasn't public, he couldn't know wether he
> was working on the most recent version or not. And it is very likely
> that he wouldn't have ported it at all. Sure, we disagree, but that's
> what happen when multiple people cooperate.
>   

I was not talking about you

> Closed door development, which is what you are advocating, does not
> really make sense in a free software project.
>   

Please can we stop with the closed * accusations?  Its what got us here
in the first place.

> Packing up a git repo and requiring your fellow devs to manually
> download this every time you make an update is just kicking your
> contributors in the nuts. I know I would never put out with bullshit
> stuff like that, when it takes about half a moment to set up a public
> git repo for everyone to use. And I'm not even talking about write
> access.
>   

Its easy to set one up, but its hard to maintain one.

You obviously do not use git much.  There is no reason to have an
upto date tree before preparing a patch, it can be months old and it
will still apply.

> You seem very afraid to reveal to others that you, like everyone else,
> fucks up their own code from time to time. You also seem to think not
> letting people see this will make the situation better.
>   

Type git-log and you will see everything.  Feel free to criticize whatever
you like.

Even if it was held in a public repository then I would still develop 
'behind
closed doors' as you say and then only push to the public repo when I was
happy.  It is the same as pushing up the tarball, nobody would see any
different code.  Even developers would not see anything different because
at any one time there will be unknown local changes anyway.

Its just basic quality control to make my own life easier.

> All I can say, is that you seem very insecure about your own work.
> You've been building this huge self image on these mailinglists by
> bashing everyone and everything around you, and it seems to me you're
> terrified to let anyone see that you too make mistakes.
>   

There is lots of my code available publicly, people are free to
criticize whatever they like.

> The support requests you speak of is a non-issue, too. It's just
> stretching for excuses to not let people activly participate in the
> development.
>   

Right... And everyone willing to help please form a line...

Nobody?  Oh well... Ill put off the rush to get it into a public repo.
The code is there if you want to have a look without committing
anything yet.  Once you decide you want to help then let me know
what you are planing and I will be as helpful as I can, to avoid
timewasting.

RYX has shown an interest but its all adding functions so I have
not pressed for git format.  If there were major changes I would
insist on a git formatted patch (you know - the same type you send
to the compiz mailing list)

> Because really, that's what you're doing. Your source may be open, but
> not your development method.
>   

Here we go again, we have given up with the troll and fud
accusations, now we are onto the 'you are closed' accusations.