Snort mailing list archives
Copyright assignment on new source files in a patch?
From: Joshua Kinard <kumba () gentoo org>
Date: Sun, 09 Mar 2014 17:24:58 -0400
So if I wanted to send in a patch that creates a new source file in Snort, what's the proper copyright assignment? Dual-copyright to 2014 Cisco/SourceFire/affiliates and myself (w/ year), or assign full copyright to Cisco/SourceFire/affiliates, insert an "Author" line or other such acknowledgement for myself, or just go full anonymity and an entry in the Changelog? Can't find a good reference for this, neither in the Snort manual nor via Google, save a very similar question asked back in 2003 on this topic. -- Joshua Kinard Gentoo/MIPS kumba () gentoo org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Snort-devel mailing list Snort-devel () lists sourceforge net https://lists.sourceforge.net/lists/listinfo/snort-devel Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=snort-devel Please visit http://blog.snort.org for the latest news about Snort!
Current thread:
- Copyright assignment on new source files in a patch? Joshua Kinard (Mar 09)
- Re: Copyright assignment on new source files in a patch? Joel Esler (jesler) (Mar 09)