microsoft
Ability to use SPDX identifiers to quickly add licenses to FOSS software
Description of the new feature/enhancement
Ability to add SPDX identifiers (https://spdx.org/licenses/) similar to how scoop handles licenses, to add info on the licenses a package uses. See https://github.com/lukesampson/scoop-extras/blob/master/bucket/geany.json#L5 for one example.
Proposed technical implementation details (optional)
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.
@denelon Is it intended that this bot closes inactive issues at such a fast rate? I'm used to projects having a much longer time before being marked as stale (to respect progress on releases) and am concerned that major issues could be closed due to this.
I need to update the comment placed by the bot. It will not close the issue if it doesn't have the label "Needs-author-feedback".
Personally, I think it would suffice to document (after establishing consensus) that it's best-practice to use an SPDX identifier in the License field of manifests, if the license is in the SPDX License List. There is currently very little guidance regarding values of those fields.
