Thanks for the pointer. To summarize: if an author modifies a work covered by GPL , and that author chooses not to distribute the modification, there is no obligation for the change to "come back". If the author does choose to distribute the mod, then the source is "requestable" by those that wish to see the mod source.
Re the issue of config files in LCNC - It seems to me that an explicit declaration of the lisc status of those files is helpful and that a permissive lisc makes sense for how they are intended to be used. I do wish that the project would/could decide to simply state something like "Config files are licensed under X terms" or "all *.Y config files are licensed under X terms...", or "all files in these directories are licensed under X terms". I just get tired of paging past lisc text whenever I open a config file (particularly when the lisc text is a significant portion of the file content in many cases). Alternatively, I'd think that this should be possible by saying something short in the file like: (c) year ABC, licensed under XYZ terms (which it the approach that much of the LCNC source uses re GPL statements). The snag seems to be that there are multiple names for each of the versions of the (for example) BSD license variants. Perhaps the project can pick and define the Lisc name tokens used by LCNC files for the permissive license variants, then state that these names in file (c) references mean this specific text. (Like the copying file does for projects that are 100% GPL). Dave On 9/11/2013 5:24 PM, Chris Radek wrote: > On Wed, Sep 11, 2013 at 03:53:42PM -0700, David Bagby wrote: >> It seems to me that if everyone that made a change to those *had* to >> contribute it back (due to GPL), we'd just get a bunch of patches >> [...] > This is a misunderstanding of the GPL, so beware any conclusions > drawn from it. See here and nearby: > > https://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. Consolidate legacy IT systems to a single system of record for IT > 2. Standardize and globalize service processes across IT > 3. Implement zero-touch automation to replace manual, redundant tasks > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
