Licensing Policy: Accepting Apache 2 for oss-fuzz related files
Azhar Momin
azhar-momin at outlook.com
Wed Aug 6 10:14:03 BST 2025
On 8/5/25 4:15 AM, Albert Astals Cid wrote:
> El divendres, 30 de maig del 2025, a les 11:53:45 (Hora d’estiu d’Europa
> central), Albert Astals Cid va escriure:
>> We are trying to move most of the oss-fuzz related files to our reops
>> instead of being in https://github.com/google/oss-fuzz/
>>
>> This will allow us to not have to depend on other people to merge changes in
>> them which sometimes creates a bit of friction.
>>
>> The problem is that those files are licenses under Apache 2 which is not
>> mentioned in https://community.kde.org/Policies/Licensing_Policy
>>
>> I would like to propose that we add a point 18 to the policy that says
>>
>> 18. Files involved in the oss-fuzz tooling can be licensed under the Apache
>> License 2.0
>>
>> Comments?
>>
>> Please see
>> https://invent.kde.org/frameworks/karchive/-/merge_requests/125/diffs
>> for one of the various places we would use it.
> Neal did my arguments convince you?
>
> At some point in the thread you stopped answering and I would really really
> like to proceed with merging
> https://invent.kde.org/frameworks/karchive/-/merge_requests/125/
>
> Is there anything that would make the addition of point 18 easier for you to
> accept? Maybe
>
> 18. Build scripts involved in the oss-fuzz tooling can be licensed under the
> Apache License 2.0
One minor correction, this would be "Build scripts and fuzz targets".
Best Regards,
Azhar
> instead of "files" in general?
>
> Best Regards,
> Albert
>
>
>> Best Regards,
>> Albert
>
>
>
More information about the kde-devel
mailing list