On 9/19/2013 9:48 PM, Jon Elson wrote: > Jeff Epler wrote: >> Depending what files you're referring to, there are two reasons that >> they might not have shown up in my list (besides errors on my part): >> * hal and ini files (among other file types) are not listed >> * files that already exist in v2.5_branch are not listed >> > Yes, those are exactly the files I was thinking of. So, are we going to > try to get these > to have a particular license declaration?
NOTE: I am waiting to see what the consensus is before adding license declarations to my config files. I would be happy with any license or even no license at all (public domain), but I don't want to make multiple updates just to change the licensing. So...are config files to be public domain, GPL-V2+, or something else? Also, I do agree with having at least a one or two line copyright and license statement in each file, although the full GPL header seems a bit too much to add to every config file. -- Charles Steinkuehler [email protected]
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
