On Sat, Jan 19, 2013 at 10:35 PM, Pedro Giffuni <p...@apache.org> wrote:
> > I would label it DISCLAIMER to make it pristine clear. > Something in the lines of: > ________ > Development branches represent Work in Progress for internal use only. > This code may be present in a future release but no claim is made concerning > their content including licensing status or code quality. > Use at your own risk. > ________ I put a more detailed version of this into a DISCLAIMER file. This statement isn't really a "legal" statement in any sense, since even our official releases come with no guarantees. So it is not like the stuff in SVN comes with fewer rights. But it does come without review and approval by the project, and that is worth noting. There was a recent discussion on legal-discuss related to this, where Roy said: "The dev subversion repo is not a means of distributing to the "general public". It distributes to our self-selected development teams that are expected to be aware of the state of the code being distributed. When we distribute to the "general public", it is called a release." http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201301.mbox/browser So, IMHO, it is worth explaining this important distinction. We shouldn't take active steps to prevent someone from using code from Subversion. But neither are we obligated to encourage the use of pre-release cide outside of the project. This is similar to how we treat dev snapshot builds. We no longer advertise them to the general user public on the website. We only make them known to the smaller group following our mailing lists. -Rob > You may want to check with legal if we should include something else. > > Pedro. > > ________________________________ > From: Rob Weir <robw...@apache.org>; > To: <dev@openoffice.apache.org>; Pedro Giffuni <p...@apache.org>; > Subject: Re: Root README file in SVN > Sent: Sun, Jan 20, 2013 3:19:19 AM > > On Sat, Jan 19, 2013 at 10:10 PM, Pedro Giffuni <p...@apache.org> wrote: > > Hi Rob; > > > > Perhaps we should add a legal DISCLAIMER to the branches directory? > > > > Funny you said that. I was in the process of adding some additional > language to the end of the README. I'd be interested in your feedback > on that. I think a disclaimer is appropriate for all of the > directories that can contain unreleased code, including branches. but > also /trunk. > > > I am aware of other projects taking code from there that we may not > > be releasing after all (oops). > > > > It is helpful, I think, to make sure the distinction between an Apache > release and unvetted code in SVN is clear. > > -Rob > > > Pedro. > > > > > > ----- Messaggio originale ----- > >> Da: Rob Weir > >> > >> I've checked in a README file to the root of our SVN tree: > >> > >> https://svn.apache.org/repos/asf/openoffice/README > >> > >> This should be useful to help orient someone who is browsing our tree. > >> > >> I could use your help identifying the purpose of the branches. I > >> described the ones I know about, but there are several there that I am > >> not familiar with. > >> > >> Thanks! > >> > >> -Rob > >>
