It would be logical to make contribution to an open source project easy,
right?
Well, in bigger projects some burocracy is inevitable, but usually has some
valid reasons behind it.

When I made some commits to Spec (while it was on github), it was as easy as
fork->commit->create pull request.
In Pharo, it's already more complicated: you have to register yourself in
SmalltalkHub, in fogbugz, in mailing lists. Slices system is also not very
intuitive. Then CI system spits out some completely unrelated errors.

But OK, I understand that Pharo is unlike, and the team maybe doesn't have
time to migrate to some integrated bugtracker/repository/whatever.

Then people began asking me of my real name - which is already wierd - why
would they need it?

And then someone suggested that I must sign license agreement (which is also
wierd - MIT license doesn't demand anything like that). 

I looked at that agreeement. It requires you to provide name, address (???),
sgin it and send it via snail mail (WTF???).

No, guys, that is beyond good and evil.
Either we skip this stupid formality and continue working on the code, or
I'm out of this.



--
View this message in context: 
http://forum.world.st/License-agreement-are-you-kidding-me-tp4865853.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Reply via email to