This request is superseded by
request 895352
(Show diff)
Overview
Request 895185 superseded
Initial packaging of appx-util to replace fb-util-for-appx
- Created by Pharaoh_Atem
- In state superseded
- Package maintainer: Pharaoh_Atem
- Supersedes 895184
- Superseded by 895352
Loading...
Request History
Pharaoh_Atem created request
Initial packaging of appx-util to replace fb-util-for-appx
Pharaoh_Atem superseded request
Initial packaging of appx-util to replace fb-util-for-appx
Thanks for bringing this fork to our attention. Planning to accept, but let me check on timing with one other person first. The obsoleting of fb-util-appx for replacement by this package could require some OBS prjconf changes just as the 15.3 releases are being prepared.
We should also have a reviewer for the post-fork license change from BSD-3 to MPL-2.0.
Yeah, I don't think this is legally correct.
The original license states
but that was removed completely.
Would putting a copy of the original license file somewhere satisfy this? I thought I had this resolved with preserving the copyright statement in the source files...
IANAL: I assume so, but all of the affected files must also still contain the old reference to the license.
I don't think that's quite right. I think the last clause can be satisfied with a documentation file that says "portions of this code was previously available under the terms of the BSD license, as this project was forked from facebookarchive/fb-util-for-appx".
This project is MPL-2.0 licensed, not BSD-3-Clause licensed. It has code that was BSD licensed, but permissive to copyleft relicensing is definitely okay. Otherwise all the proprietary software in the world would be screwed.
You can redistribute code under license A under another license B if that license B fulfills all of the requirements imposed by license A. In this case this is only achievable by effectively distributing it as BSD+MPL FWICT.
https://blog.gerv.net/2013/02/relicensing-when-do-you-have-to-ask/#comment-23967
Already tracked internally as OPENSUSE-28/SLE-18068
What's wrong with just keeping the original BSD license?
I don't like developing/maintaining permissively licensed projects.
quite rude
Eh? I could have left it dead instead. And I think the MPL is a decent compromise of a license.