On 20/11/2024 20:04, Brian Inglis via Cygwin-apps wrote:
On 2024-11-20 12:43, Glenn Strauss via Cygwin-apps wrote:
On Wed, Nov 20, 2024 at 12:27:19PM -0700, Brian Inglis via Cygwin-apps
wrote:
Hi folks,
Arch is clarifying packages PKGBUILD sources licences.
https://archlinux.org/news/providing-a-license-for-package-sources/
https://rfc.archlinux.page/0040-license-package-sources/
What are our assumptions and requirements?
As far as I'm aware, we have no policy on this, currently.
This should probably change.
If you want to take the lead on this issue, that would be great!
(I've got a vague plan to send out a reminder email to all package
maintainers early next year, since we have some who have been inactive
for a long time, who's ssh keys I want to deactivate in accordance with
sourceware policies on dormant accounts, so we could also use that as an
opportunity to inform them of any policy change here)
I have provided a BSD-2-clause contributor's licence for patches
wrt. patches, I think the sensible policy is that they should be
provided under the upstream's license(s), so they can be... upstreamed.
