On Wed, Sep 2, 2009 at 5:36 PM, Matthias Wessendorf<[email protected]> wrote: > On Wed, Sep 2, 2009 at 5:29 PM, Bruno Aranda<[email protected]> wrote: >> Yeah, you are not going to prison just for committing the code. And >> the discussion can continue in legal while things work... > > no, but isn't the general problem that some folks are looking at the RI code > ?! > IMO that's not correct at all. I agree with Curtiss' concerns, as I share > them. > > Maybe we should ping legal _before_ committing problematic stuff ?
an interesting note from the Apache Harmony project, we got on legal@: <snip> Harmony, OTOH, says that they have been extremely cautious and have not allowed any developer to work on any part which they have previously been exposed to. This is largely precautionary beyond necessity. </snip> perhaps we should also ensure a policy like that ?! > > -Matthias > >> >> Cheers, >> >> Bruno >> >> 2009/9/2 Werner Punz <[email protected]>: >>> That is one of the reasons why I am discussing this here from an Apache >>> codebase and license point of view I am pretty sure I am clear here (I also >>> will bring this to legal tomorrow), but I am still not sure if I can commit >>> the code due >>> to the stance some of the contributing companies have regarding code. >>> >>> My personal point of view for now is this: >>> >>> a) bring this discussion to legal >>> >>> b) commit the code - if legal gives its ok, if someone thinks it is >>> infringing (which i doubt) we still can rip it out >>> >>> >>> >>> Werner >>> >>> >>> Curtiss Howard schrieb: >>>> >>>> The only concern I have is that my company considers a person >>>> "contaminated" if they've been exposed to some other code base and >>>> therefore any code written by that person carries the risk of >>>> infrigement (i.e., if you saw a company's code for class X and write >>>> your own implementation of X without looking at their code ever again, >>>> you could remember things you saw and your implementation could >>>> subsequently copy parts of their code with literally being a copy). I >>>> would be careful. >>>> >>>> Thanks, >>>> >>>> >>>> Curtiss Howard >>>> >>> >>> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
