Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cft-dev] Help clarifying if CFT needs license files at "root" level

Hi,

I haven't found an answer to this yet. Elson, is this something WTP
also needs to do, to have license files at root level?

Thanks.

-Nieraj

On Mon, May 23, 2016 at 3:14 AM, Martin Lippert <mlippert@xxxxxxxxx> wrote:
> Hey Nieraj,
>
> back from vacation now, sorry for not replying to this earlier.
> Did you sort this out in the meantime?
>
> Cheers,
> -Martin
>
>
>
>> Am 13.05.2016 um 03:18 schrieb Nieraj Singh <nsingh@xxxxxxxxxx>:
>>
>> I wanted to ask in cft-dev first before asking in the cross-mailing
>> list or emailing license@xxxxxxxxxxx, but does anyone know if the
>> checklist for SUA at the end of section 4.1 here:
>>
>> https://eclipse.org/legal/guidetolegaldoc.php#LegalDoc
>>
>> applies to CFT?
>>
>> These are the two checklists:
>>
>> - Every build distribution has the standard SUA in the root as "notice.html"
>> - Every build distribution has a copy of the primary license(s) in the
>> root, e.g., "epl-v10.html"
>>
>> We do provide update sites as zips for offline installation, does this
>> mean that at root level in these zips we need to have notice.html and
>> the epl html license file?
>> _______________________________________________
>> cft-dev mailing list
>> cft-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cft-dev
>
> _______________________________________________
> cft-dev mailing list
> cft-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cft-dev


Back to the top