Mike Kienenberger schrieb:
Looking at someone else's code and then writing your own version is a no-no.
However, there's a legal way to deal with it. Clean-room reverse engineering.
Here's an example of how it was done with wireless driver support for
linux -- good overview of the proper
Ok guys to get back to the topic, I now have committed the clean parts
of the renderer and the behavior so someone else can take over from now.
All which is missing is the full tag integration, I have not yet checked
the already existing tag code so I am not sure what is missing there.
Btw.
On Wed, Sep 2, 2009 at 5:36 PM, Matthias Wessendorfmat...@apache.org wrote:
On Wed, Sep 2, 2009 at 5:29 PM, Bruno Arandabrunoara...@gmail.com 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
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
On Thu, Sep 3, 2009 at 12:29 PM, Curtiss Howardcurtiss.how...@gmail.com wrote:
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
+1. Better to be safe than sorry here in my opinion.
Matthias Wessendorf wrote:
On Thu, Sep 3, 2009 at 12:29 PM, Curtiss Howardcurtiss.how...@gmail.com wrote:
an interesting note from the Apache Harmony project, we got on legal@:
snip
Harmony, OTOH, says that they have been extremely
+1. Same opinion as Michael.
2009/9/3 Michael Concini mconc...@gmail.com:
+1. Better to be safe than sorry here in my opinion.
Matthias Wessendorf wrote:
On Thu, Sep 3, 2009 at 12:29 PM, Curtiss Howardcurtiss.how...@gmail.com
wrote:
an interesting note from the Apache Harmony project,
Looking at someone else's code and then writing your own version is a no-no.
However, there's a legal way to deal with it. Clean-room reverse engineering.
Here's an example of how it was done with wireless driver support for
linux -- good overview of the proper process.
I don't think you should worry too much about it. We could re-write it later
if it is perceived as some kind of copyright violation, but I doubt that
could ever be the case. Like you said, every single line was written by you.
You can't help what your influences were.
I say proceed :)
On Wed,
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
Yeah, you are not going to prison just for committing the code. And
the discussion can continue in legal while things work...
Cheers,
Bruno
2009/9/2 Werner Punz werner.p...@gmail.com:
That is one of the reasons why I am discussing this here from an Apache
codebase and license point of view I
Yeah, you are not going to prison just for committing the code. And
the discussion can continue in legal while things work...
Cheers,
Bruno
That's true, but some of us who work at certain paranoid companies may
become contaminated by association by virtue of the fact that we
have access to
Matthias Wessendorf schrieb:
On Wed, Sep 2, 2009 at 5:29 PM, Bruno Arandabrunoara...@gmail.com 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
On Wed, Sep 2, 2009 at 5:38 PM, Werner Punzwerner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
On Wed, Sep 2, 2009 at 5:29 PM, Bruno Arandabrunoara...@gmail.com wrote:
Yeah, you are not going to prison just for committing the code. And
the discussion can continue in legal while things
Actually if anyone not contaminated is willing to program the tag
handler for f:ajax I would be happy to donate the code not touched
by my mojarra knowledge so that anyone else can take over ;-)
What you could get what is clean is the ajax behavior itself and the
renderer as well as the
Matthias Wessendorf schrieb:
Already done, lets see what they have to say.
cool. thanks!
Ok so far no decisive no or yes, but the main issue here I think
is less the ASL license I personally think we are clear here,
but the way some of the attached companies handle the legal issues
16 matches
Mail list logo
