Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of nslater@tumbolia.org designates
 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKprHVZXyqe2OaqUA6X46mzkzKVhFsPW=DUPOg=pmZ1no9k47A@mail.gmail.com>
References: 
 <CA+96GG5B9USXfHMLEhV_1X5r9uJaaZdRajYX48Oa3TziRrPoaw@mail.gmail.com>
	<CA+Y+447zNKkccPXGT9HWiYYnKyWjJjj9EANvTis=OGSSt1VYFQ@mail.gmail.com>
	<CAKprHVaC9ZPYuxSZ5DCUWgaxxtxzb_7XpwfONSZqr77-EKv7rw@mail.gmail.com>
	<CA+Y+444aY_LjSQ5YkCXbnQeRDd8gVTo1cu6UvZoqbFenOu4h2g@mail.gmail.com>
	<CAKprHVZXyqe2OaqUA6X46mzkzKVhFsPW=DUPOg=pmZ1no9k47A@mail.gmail.com>
Date: Thu, 13 Sep 2012 19:43:08 +0100
Message-ID: 
 <CA+Y+445=WS2ckcfyu+h-NdH1Y=yZ5OMOm4UZ_-kiHrRw63E5nQ@mail.gmail.com>
Subject: Re: [ASFCS40][DISCUSS] How should we move forward to resolution on
 the config files in "patches"? Was: "Re: [ASFCS40] Configuration file
 licensing followup"
From: Noah Slater <nslater@tumbolia.org>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b41c3eabe31f304c999ada1

--047d7b41c3eabe31f304c999ada1
Content-Type: text/plain; charset=ISO-8859-1

Thanks!

On Thu, Sep 13, 2012 at 7:41 PM, David Nalley <david@gnsa.us> wrote:

> On Thu, Sep 13, 2012 at 2:36 PM, Noah Slater <nslater@tumbolia.org> wrote:
> > Saying that configuration files, in all cases, are not copywritable
> because
> > that are, on the whole, not as complex as code is like saying that blog
> > posts, in all cases, are not copywritable because they are, on the whole,
> > not as complex as books.
> >
> > The law is much more nuanced than that. There is no way we can say, up
> > front, whether a configuration file is protected by copywrite or not. The
> > unwillingness to commit to anything on legal-discuss is an indication of
> > this. (It was made explicit that with a vague question, there will only
> be
> > vague answers.)
> >
> > It might be better to actually document what we have, and then present
> that
> > to legal discuss and take it from there.
> >
> > Let's get concrete.
> >
> > We should put together a list of each config file path, along with
> > information such as:
> >
> > * Size of file
> > * Complexity (key/value, code snippets, what?)
> > * Copyright notice or license header?
> > * License of project it (may) have been taken from
> > * Origin (Citrix, upstream project, unknown?)
> >
> > Once we have a complete picture, I think we can talk about how to
> proceed.
> >
> > (And hopefully propose a guideline for future config files.)
> >
> > I certainly do not think we are in a position to write of an entire
> > category of data as being uncopywritable.
> >
> > I am happy to run this to pursue this with legal too, but I think we
> need a
> > better view of what we're dealing with.
> >
> > Thoughts?
> >
>
>
> Alright, I'll start working on compiling this.
>
> --David
>


-- 
NS

--047d7b41c3eabe31f304c999ada1--