I''m happy to announce that we now have contributor agreements available for folks who would like to contribute code to IronRuby. The process is pretty straightforward - send an email to ssiadmin at microsoft.com<mailto:ssiadmin at microsoft.com> and request to be added as a contributor to the IronRuby project. The actual signature process is handled through an online electronic signature tool. No trees will be harmed. Once you''ve signed the agreement we''ll be able to review your code for inclusion in IronRuby. Thanks for your help! -John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ironruby-core/attachments/20070917/9ac7afb9/attachment.html
Great! I can attest that it''s pretty painless too. Except that newborn clause... ;) Anyways, once that we''ve signed the agreement, how do we approach external but related code? IronRuby is surrounded by directly & indirectly related open source projects (Matz''s Ruby, jRuby, numerous libraries, etc). Do we need to avoid all of that code entirely for risk of patent & copyright contamination? Is it OK to peek at how they solved the same problems? Can we use the same algorithms? Obviously lifting code is inappropriate on many levels, but pretending we''re solving problems for the first time seems a little backwards too. -Eric On 9/17/07, John Lam (DLR) <jflam at microsoft.com> wrote:> > I''m happy to announce that we now have contributor agreements available > for folks who would like to contribute code to IronRuby. The process is > pretty straightforward ? send an email to ssiadmin at microsoft.com and > request to be added as a contributor to the IronRuby project. > > > > The actual signature process is handled through an online electronic > signature tool. No trees will be harmed. Once you''ve signed the agreement > we''ll be able to review your code for inclusion in IronRuby. > > > > Thanks for your help! > > -John > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ironruby-core/attachments/20070917/a9d6b2b4/attachment.html
> From: Eric Nicholson > Sent: Monday, September 17, 2007 2:17 PM > To: ironruby-core at rubyforge.org > Subject: Re: [Ironruby-core] Contributor agreements are ready > > Great! I can attest that it''s pretty painless too. Except that > newborn clause... ;)Wasn''t that newborn clause printed with a white font??? :)> Anyways, once that we''ve signed the agreement, how do we > approach external but related code? IronRuby is surrounded > by directly & indirectly related open source projects > (Matz''s Ruby, jRuby, numerous libraries, etc). Do we need > to avoid all of that code entirely for risk of patent & copyright > contamination? Is it OK to peek at how they solved the same > problems? Can we use the same algorithms?I think you should be fine looking at whatever code that you feel like looking at, since you aren''t a Microsoft employee :) But just make sure that you have the rights to do copyright assignment on your contributions. Thanks, -John