[Compcomm] Code storage

[Kristian Lyngstøl]

Since I ran a little hot in my last few posts, let me start fresh.

To be able to cooperate, there is necessity for common practices.
Storing code in diffrent places doesn't help us in any way. This
should be obvious for a number of diffrent reasons. The overhead
included both for fellow contributors and the confusion this creates
for users, potential new contributors and packagers should be reason
enough to keep the number of places where code is stored at a minimum.

In fact, this goes for any sort of information, not just code.

There is a common conseus amoung everyone to use git, so at least
that's not a problem.

As for development styles, there are obviously strong opinions on this
that will be difficult to unite. But this shouldn't stop us from
cooperating.

I'll accept that some people don't wish to release their code the
moment they make a local commit. But this doesn't mean there is any
reason not to use the common storage model that opencompositing.org
now offers us.

Using the git services of opencompositing.org lets you easily create
new repositories, and with git 1.5 you can do pretty much all tasks
you wish on these repositories remotely. If you wish to release your
code once a day, once a week or once a month, this can still be done
within the git service at opencompositing.org.

This service also gives you complete control: As long as it is your
repository, you are going to be the only one who can commit directly
to that repository.

So I ask everyone to kindly rethink their reasons for not using
opencompositing.org for their git repositories. I realise some people
feel very strongly that this merge is not a good thing, or that parts
of it is not going well. But consider using a common place for
releasing code as a gesture of good will. You will still retain
complete control both over your release cycle, and your commit
permissions. And you will make things easier for the people around
you.

If it is a matter of who owns the domain or control the server, I am
disappointed. Letting such things get the better of us will not lead
anywhere we want to be. But even if that is your reason, remember that
with git, you still have a complete local copy. In fact, there is
nothing stopping you from pushing your code to multiple remote
repositories. So there is no real way for the administrator to commit
a coup of your repository.

Last; Let me apologise for my offensive tone. I am frustrated by our
lack of cooperation. I don't have much patience for these sort of
things. I shouldn't have let that get the better of me. I hope you can
forgive me, yet again.

-- 
Regards,
Kristian