Tilman Sauerbeck <tilman@crux.nu> wrote:
Matthias-Christian Ott [2007-10-06 13:13]:
Tilman Sauerbeck <tilman@crux.nu> wrote:
Matthias-Christian Ott [2007-10-05 17:51]:
I tried to get a developer account and proper e-mail address on the CRUX server in order to be able to participate in development, maintenance and organisation, but nobody replied, my e-mails were rejected. I contacted Per and told him about my plans, but he could not really help me, because he was not a CRUX developer anymore.
Yeah, contacting Per is moot these days.
btw, I've seen that mail now in which you tried to get a developer account. I suggest you read that mail again yourself and think about whether the *tone* of the text fits with "asking for access".
A developer needs access to primary development repository in order to work effectively. Additionally I am not a native speaker.
Yes, asking for access is fine and encouraged in general. Hint: you could have greatly helped to back up your argument if you had provided links to your personal git clones of core/opt/whatever.
If you have no access to a hosting server, you can not provide links.
Distributed SCMs make it soo easy to contribute even if you don't have access to the main servers... While this isn't always best as a permanent solution, it's a great way to get your feet wet.
Yes, distributed revision control systems are great, but merging changes from the main server is sometimes really annoying.
re your language skills: From your other mails around here it seems you speak English very well. So it seems a bit hypocritical to blame your language skills for that abusive mail TBH.
That e-mail was not abusing; I never tried to abuse someone or something. I just meant that was maybe not aware of the fact that people feel offence when "asking for access" which sounds to me quite neutral
I've worked with several free software projects in the last few years, and I've never seen somebody behave like that when they wanted to contribute.
In comparison to the GNU procedure for developers (which is really necessary), it is quite unusual to ask that directly.
What? I don't understand what you're trying to say.
Working on the GNU project means basically to transfer to the copyright of your source code to the Free Software Foundation which protects the source code for you.
I have been a project primary administrator for a project hosted by berlios and gave commit and write rights to everyone who wanted and never had any problems with this policy.
Good for you, but IMO giving write access to everyone even if you barely had contact with them is a bad idea.
The concept of the patch queue resolves your concerns.
Commanding us to give you access after you supplied two patches is kind of crazy.
It depends on your perspective and opinion.
No, it doesn't! _Commanding_ us to do anything is *not* a good way to achieve your goals! We're not in your debt, you have to earn your privileges here.
It was not meant to be a command.
And of course, it doesn't make sense at all that you didn't subscribe to the developer list in order to be able to post there to ask for access.
Well, I had an e-mail account at yahoo and used it via webmail which made it practically impossible to subscribe to any mailinglist.
Use another account then? Duh.
I did not have one.
Apparently flaming us was enough reason to subscribe to this list after all. Oh well o_O
No, I never intended to start a flame war. I got a better e-mail account
Sure it was, you were proclaiming CRUX' death while it's still active. How'd you think we'd react to that? o_O
I do not know, but I just expressed what I think. -- Matthias-Christian Ott