[Compcomm] Forum Decision
Kristian Lyngstøl
kristian at beryl-project.org
Fri May 11 13:21:01 EDT 2007
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.
Closed door development, which is what you are advocating, does not
really make sense in a free software project.
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.
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.
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.
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.
Because really, that's what you're doing. Your source may be open, but
not your development method.
--
Regards,
Kristian
More information about the CompComm
mailing list