An FYI on one person's feelings about putting jars into svn, and
consequences if those jars contain 5D002 software.
Also, if we are now supporting encryption functionality in the
modeler, we need to get listed on
http://www.apache.org/licenses/exports/ by following the processes
outlined at http://www.apache.org/dev/crypto.html
There's a lot more detailed info on this topic in the "podling BIS
notifications" thread running on genera..ncubator.apache.org if you
want to read it.
On 2/21/07, Roy T. Fielding <fieldin..biv.com> wrote:
> Note, however, that if anyone commits something like the OpenSSL
> or Bouncy Castle source code and/or binaries, which are products
> in and of themselves, to the subversion instance, then the PMC
> must file an export notice for the subversion area even if no ASF
> product has been released yet. That is because distributing
> third-party products from a public web server is the same as
> exporting them. Personally, I think it is wrong for projects to
> commit code to subversion unless it is intended to be maintained
> as source, but I know that some "real" projects at the ASF are too
> lazy to write build scripts and instead use our subversion instance
> as a binary distribution medium.
This archive was generated by hypermail 2.0.0 : Wed Feb 21 2007 - 12:47:40 EST