No, my suggestion is that license file is updated with the names of contributors, including Intel copyright line.
On Tue, Jul 29, 2014 at 10:07 PM, Kenny, Jason L <jason.l.ke...@intel.com> wrote: > So your suggestion is that I update the license file with Scons Foundation? > > Jason > > -----Original Message----- > From: Scons-dev [mailto:scons-dev-boun...@scons.org] On Behalf Of anatoly > techtonik > Sent: Tuesday, July 29, 2014 12:21 PM > To: SCons developer list > Subject: Re: [Scons-dev] New symlink copy support > > On Tue, Jul 29, 2014 at 4:02 AM, Kenny, Jason L <jason.l.ke...@intel.com> > wrote: >> Ideally that is the hope I have.. CCopy should be used as the backbone >> of all copied in Parts and I hope in SCons. Everything in Parts is >> done so it could be added to SCons. The license is MIT under Intel, >> but it is assumed that SCons will own all this code as it moves stuff >> over. Intel has no interest in controlling a build system. > > As long as license is MIT, there is no need to transfer copyright. Just add > the appropriate line to LICENSE file. In fact, I prefer this way of doing > things, like in Twisted. > > https://twistedmatrix.com/trac/browser/trunk/LICENSE > > Then at the top of each file we just reference the LICENSE. > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > http://two.pairlist.net/mailman/listinfo/scons-dev > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > http://two.pairlist.net/mailman/listinfo/scons-dev -- anatoly t. _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev