Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: local policy)
In-Reply-To: <2d12b2f00703131945h6c72308fq464b12dd1eb178b9@mail.gmail.com>
References: <ecd0e3310702070847i7f1bf7e7re434c6c5271b8b11@mail.gmail.com>
 <16d6c6200702070916m33d495d4se5ac0e214d0d4db5@mail.gmail.com>
 <2d12b2f00702071055q323c02b3yb13dcf503138f572@mail.gmail.com>
 <ecd0e3310702081123te438871m7f075c1294595a62@mail.gmail.com>
 <77B5894F-6E89-4AA1-AFBC-F86325306E4B@wsanchez.net>
 <15DA30B0-0F1D-4EE5-A06F-9DF32C9D1EA5@gbiv.com>
 <ecd0e3310702201229j144811f0k865207067a7dd240@mail.gmail.com>
 <68E3A47F-1B78-4B59-B035-271B1A941295@gbiv.com>
 <2d12b2f00703131945h6c72308fq464b12dd1eb178b9@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <AD21F86E-2BDF-4459-A950-4ACD3DB2E656@gbiv.com>
Cc: "Howard Lewis Ship" <hlship@gmail.com>,
 legal-discuss@apache.org
Content-Transfer-Encoding: 7bit
From: "Roy T. Fielding" <fielding@gbiv.com>
Subject: Re: About bundling JavaScript with frameworks
Date: Wed, 14 Mar 2007 12:31:46 -0700
To: Henri Yandell <bayard@apache.org>

On Mar 13, 2007, at 7:45 PM, Henri Yandell wrote:
> I don't think we can draw this line here - if the distribution will
> contain the 3rd party library then keeping it in SVN seems prudent.
> Otherwise you're at the whim and mercy of a 3rd party URL.

So?  That URL will change.  If it disappears entirely, you had better
have the source code on hand anyway.

> In many cases I suspect we don't keep it in SVN simply because it's
> available from the Maven repository - so be it, but I don't think we
> can take those cases to be the rule.

No, we don't keep it in SVN because it is a big honking file that
isn't subject to version control and isn't in open source code form.
Our foundation creates open source and ONLY open source -- binaries
are only redistributed as a convenience to end-users with releases.
If we have third-party code in subversion, then it is in source code
form and it is there because we have made local changes.  Otherwise,
the module should not be in subversion -- it should be downloaded by
whatever build script is used by the developers to construct a
testable package.

The only exceptions are for subversion modules that are not products,
like the site modules that usually contain whatever jars are necessary
to build the site.

....Roy

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org