robert burrell donkin wrote:
On 12/29/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I think that for DK we have to deal with their patent and the license
for Implementing the Specification.
[...]
IANAL...
Nor do I, and if I understand ASF rules we cannot decide ourselves this
issue. There is a list of licenses that we are allowed to include. THis
is not listed, so we have to ask and wait for approval (right?).
Guillermo pointed out the DKIM specification but I don't know how it
relates to Domain Keys. I see that Apache SpamAssassing is listed
between implementations of the DKIM specification.
Maybe DKIM is something different and released under different
licensings (it is being proposed to ietf and probably cannot contain the
reciprocal patent issue) or that SpamAssassin PMC already solved the
legal issues related to including DKIM.
I only found this related message on the SA-dev list:
http://www.nabble.com/DKIM-IPR-details-updated-tf301386.html#a843058
> i think that a CLA or a software grant would be more appropriate in
> this case but JIRA's the usual first port of call.
I agree, but I think it is really fast to at least attach to JIRA, and
this will give us the opportunity to review the code and understand how
much code it is.
I think, for example, we could also consider creating an ad-hoc project
(like jSPF).
> since my reading of the licenses indicates that it's safe to develop,
> one possibility would be to offshore the development whilst the legal
> issues are sorted out.
>
> googlecode's fast and uses subversion. svn:externals could be used to
> easily create a composite source. discussions would be fine on this
> list but the code would be offshore for the time being. i'd be happy
> to help Tom apply appropriate headers and check that the statements
> required by Yahoo! are in the right place.
>
> opinions?
>
> - robert
I don't like too much the use of svn:externals. Either way we'll have to
wait for the legal issues to be resolved in order to try to release.
I thought that legally we could also include it in ASF repository while
we resolve the legal issues and that this is only blocking for releases
(like the svn:external).
Btw if you want to take care of this issue (both technical and legal) we
would really appreciate this.
Maybe writing to the SpamAssassing PMC and to Cliff Schmidt (cliffs at
ASF) is the fastest path: would you mind taking care of this?
Thank you,
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
