Licensing for the ArchLinux repositories
Task Info (Flyspray) | |
---|---|
Opened By | Alexandru Stan (amstan) |
Task ID | 44893 |
Type | Bug Report |
Project | Arch Linux |
Category | Arch Projects |
Version | None |
OS | All |
Opened | 2015-05-07 21:36:31 UTC |
Status | Assigned |
Assignee | Levente Polyak (anthraxx) |
Details
A few days ago I wished to contribute to the Arch Linux ARM project, which is a downstream project, but all of this is applicable to Arch proper first (and it probably needs to be solved before Arch Linux ARM can take steps to fix this).
This contribution was sparked because I am a ChromeOS developer for Google. I made that patch(adding a new PKGBUILD) as a Google employee with Google hardware (it wouldn't make sense for me to do it on my personal time). As a result my employer has to approve any open source releases/patches that I write.
I had a new PKGBUILD ready for Arch Linux ARM, but my employer refused to approve it. As far as they are concerned the PKGBUILDs are not licensed under an open source license.
The situation is that even though the patches in every folder and the packages themselves are licensed under the respective licenses (the license=('') line in the pkgbuilds), the PKGBUILD themselves and the install scripts have no license.
I know some of you consider this to not be a big deal (why would anyone get upset over copying a thing that a project's documentation says you should do), but this essentially prevents me from contributing things related to my job to Arch Linux or Arch Linux ARM.
Is there some way we could attach a license to all these files?