Re: [Audacity-devel] License declaration in header of files?

[Vaughan J. <va...@au...>]

Sorry, I've got very spotty email this weekend through tomorrow night.

Gale, Dominic, and I had been discussing this more broadly off-list. We
should have had a copyright notice in all the file headers all along,
but as a stopgap, I recently put it in the READE and the notice in the
AboutDialog, and made the README refer to all the files in the archive
(i.e., we should have a notice in all files, not just C++ source code).
But it would have more weight to have the notice in every file, than
the attempt at blanket coverage in README.

I think it's better to have them consistent, i.e., "Audacity(R) is
copyright (c) 1999-2008 Audacity Team", rather than have every person
who edits a file add their name to the list. People have rarely added
their names to files so that most say just Dominic even if the majority
of the code in the file was written by somebody else. Also, this way we
can just do a global change and a periodic global check. I also think
the copyright notice has more weight if it's all contiguous on one
line, not spread out over multiple lines.

Thanks, James.

- Vaughan


--- James Crook <cr...@in...> wrote:

> Vaughan Johnson wrote:
> >> However, I'm happy to go 
> >> with files-in-same-directory-with-different-licenses for now if it
> eases 
> >>     
> > other issues. Thanks, I hadn't noticed the notice in the header. It
> refers to 
> > Licensing.txt, but I don't see that, even in the wxWidgets
> hierarchy.
> >   
> 
> I've added a proposal for a 'standard' header for our .cpp files to
> the 
> wiki:
> 
> http://www.audacityteam.org/wiki/index.php?title=CodingStandards
> 
> 
> We're not actually using the (C) symbol in our code and I think we 
> should?  And we should say what license each code file is under?  [I 
> don't like headers which have the whole license in them.  It's
> horrible 
> to work with especially when the files are small.]
> 
> This is just for discussion.
> 
> I don't think we should do anything 'radical' here, like actually
> make a 
> change throughout the project right now, but we do need some
> discussion 
> especially as some GSoC students will be adding new files and we want
> to 
> be able to tell them what to use for a header.
> 
> --James.
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>