I would like to add to the site some text around applying the copyright statement per the license text as per http://www.ovirt.org/about/licensing/ In the piece at the top of the license, there is a section "Copyright [yyyy] [name of copyright owner]"

Based on some discussion reading the source to be opened for the workshop, I believe we should use the following general rule for the projects. The author of the file applies his organization or themselves as the copyright owner, and then any additions / modifications can be determined from the GIT history. Maybe better I just create a guide for any incubating project, I'll post it for comment. Carl. _______________________________________________ Board mailing list Board(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/board

On Tue, Oct 18, 2011 at 01:41:04PM -0500, Anthony Liguori wrote: > > On 10/18/2011 12:35 PM, Carl Trieloff wrote: >> > > >> > >I would like to add to the site some text around applying the copyright >> > >statement per the license text as per http://www.ovirt.org/about/licensing/ >> > > >> > >In the piece at the top of the license, there is a section >> > > >> > >"Copyright [yyyy] [name of copyright owner]" > > > > This will remain a recommendation, right? It would be difficult for > > us to get approval to use something other than the IBM corporate > > standard copyright notice (which does change every couple years). > > It seems (C) comes in and out of style over time :-) That line is actually from the appendix of the Apache License 2.0, which gives a recommended copyright notice. I'm sympathetic to the view that precise formal details of copyright notices should not be mandated. At Red Hat, I think the "(C)" may have been historically recommended, but I have non-actively promoted non-use of it on principles of minimalism :-). I think, however, that Carl was suggesting a rule that *some* suitable form of copyright notice be placed by the author of an original file, not mandating what the form would be.

I personally rather dropping the [name of copyright owner] I believe that's why we have history in the source control.

On 10/23/2011 08:37 AM, Carl Trieloff wrote: > On 10/22/2011 01:18 PM, Livnat Peer wrote: >> I personally rather dropping the [name of copyright owner] I believe >> that's why we have history in the source control. > > That is also fine. > > Note that if a file is brought to the project it is considered bad form > to strip the copyright notice, so over time we will get a collection of > files with notices and without over time if code is re-used from other > OSS projects. Are we talking about dropping the copyright line or an authors line? For instance: * Copyright International Business Machines, 2011 * Authors: * Anthony Liguori <aliguori(a)us.ibm.com&gt; Having a person's name in the file is useful in terms of asking questions. Yes, git exists but not everything deals with git trees. If we're talking about stripping the Copyright line, that's not going to be allowed some corporate legal departments. People copy files between projects so preserving the copyright notice is pretty important. Regards, Anthony Liguori

> > Carl. > _______________________________________________ > Board mailing list > Board(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/board >

On Sunday 23 October 2011 20:01:33 Livnat Peer wrote: > On 10/23/2011 07:31 PM, Anthony Liguori wrote: >> On 10/23/2011 08:37 AM, Carl Trieloff wrote: >>> On 10/22/2011 01:18 PM, Livnat Peer wrote: >>>> I personally rather dropping the [name of copyright owner] I believe >>>> that's why we have history in the source control. >>> >>> That is also fine. >>> >>> Note that if a file is brought to the project it is considered bad form >>> to strip the copyright notice, so over time we will get a collection of >>> files with notices and without over time if code is re-used from other >>> OSS projects. >> >> Are we talking about dropping the copyright line or an authors line? >> For instance: >> >> * Copyright International Business Machines, 2011 >> * Authors: >> * Anthony Liguori&lt;aliguori(a)us.ibm.com&gt; >> >> Having a person's name in the file is useful in terms of asking >> questions. Yes, git exists but not everything deals with git trees. >> >> If we're talking about stripping the Copyright line, that's not going to >> be allowed some corporate legal departments. People copy files between >> projects so preserving the copyright notice is pretty important. >> >> Regards, >> >> Anthony Liguori >> > > I was referring to the author. > One person is adding the file and many others are changing it. Many > times (after a while) the file has little to do with the original file > that was added. > > So for questions about the file you usually need to deal with the info > from the source control. > > Livnat > WRT to omitting the person name (from past experience...), After a year or so people change positions / work places, and this becomes simply an old memory, with the relevant person not longer available to answer questions, so this is missing the point.

> WRT to omitting the person name (from past experience...), After a year or so people change positions / work places, and this becomes simply an old memory, with the relevant person not longer available to answer questions, so this is missing the point.