| [wtp-pmc] FW: Board Approval of Non-EPL Code |
|
Executive summary: reuse of Apache code *already approved* elsewhere in Eclipse is
now fast tracked. Nothing about the process changes save the expected time lag (Janet’s
ok still required, IP log entry still required, etc.) This only applies to ASF
licensed material. From: Janet Campbell
[mailto:janet.campbell@xxxxxxxxxxx] I received a favorable response. We
are implementing this approach. Janet Campbell Manager, Intellectual Property Eclipse Foundation Inc. Phone: (613) 224-9461, x.229 (GMT
-5) Fax: (613) 224-5172 email: janet.campbell@xxxxxxxxxxx www.eclipse.org From: Tim Wagner
[mailto:twagner@xxxxxxx] Was there a decision from the Board on
this issue? From: Janet Campbell
[mailto:janet.campbell@xxxxxxxxxxx] Currently, there is a requirement that the Board approve
each proposed use non-EPL code in Eclipse, irrespective of whether the code has
already been approved for use in Eclipse. This currently means that if
Apache Ant 1.2 is already used in Eclipse in one project, it must be approved
by the Board to be used in another project. I wanted to let you know that
I currently have a proposal out to the IP Advisory Committee to the Board to
see if we can create an exception to this rule for Apache code. If
I’m successful, this would mean that if Apache Ant 1.2 is already used in
Eclipse in one project, Board approval would not be required and I would be
able to approve the contribution right away. The initial feedback from
the Committee has been favorable. I’ll let you know how the
discussion proceeds. Regards, Janet Campbell Manager, Intellectual Property Eclipse Foundation Inc. Phone: (613) 224-9461, x.229 (GMT -5) Fax: (613) 224-5172 email: janet.campbell@xxxxxxxxxxx www.eclipse.org _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. |