http://opensourcedba.wordpress.com/2013/07/05/mysql-is-looking-for-external-contributions
My reply: Allow me to contribute code with a BSD (3-clause) license without having to sign anything new and then we can talk.
Don’t tell me that it can’t be done: Oracle already has some code of mine in another product which was contributed under a BSD (3-clause) license.
2 comments:
Being able to work against a current / up-to-date VCS source tree instead of one that just gets updated on releases (and even that process breaks every once in a while ): would also be nice ...
Or being able to pick a bug or feature request to work on from the bug database, knowing that if the status only says "verified" without any further info that indeed nobody is working on it yet ...
Or architectural planning not happening "in the dark" so that you may know that doing patches against a certain region of code may not be a good idea at this point in time as there will be substantial changes on it down the near term road anyway ...
But yes, contributor agreements are the main show stopper, especially for those of us where this might require eployers agreement ... the process has improved a lot over old MySQL AB days around the time when i joined, when things included signing actual paper and accepting a one time symbolic payment of AFAIR 100$, but still ...
Hartmut,
I'd +1 your comment if I could.
I had contributed as long as 5 years before being contracted by MySQL AB and at no time in that period do I remember having to sign some contributor agreement.
I don't want anything special - I just want to contribute more using the same license for which I already have contributions already within their company's products.
Post a Comment