Re: Copyright assignment on new source files in a patch?

["Joel Esler (jesler)" <jesler () cisco com>]

On Mar 9, 2014, at 5:24 PM, Joshua Kinard <kumba () gentoo org<mailto:kumba () gentoo org>> wrote:


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.

I’ve been having some recent conversations about this with legal now that we are Cisco.  Let’s take it off list and 
work it out between us and legal maybe on a conference call or something, then when we document the procedure, we’ll 
filter that back to the list/website.

It’s slightly different now that we are Cisco than it was at Sourcefire.  About the same amount of work (simple 
actually), but we just need to get the verbiage correct is all.

--
Joel Esler
Open Source Manager
Threat Intelligence Team Lead
Vulnerability Research Team

------------------------------------------------------------------------------
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!