From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: LICENSE in cygport (was Re: [ANNOUNCEMENT] cygport 0.35.2-1)
Date: Sun, 17 Jul 2022 12:19:07 +0100 [thread overview]
Message-ID: <6dedeae9-4f9d-bc3e-e329-a96749cd6d9a@dronecode.org.uk> (raw)
In-Reply-To: <8c74dba3-bfaa-e011-e40f-d9bb66363ce8@SystematicSw.ab.ca>
On 04/07/2022 20:41, Brian Inglis wrote:
> On 2022-07-04 10:30, Andrey Repin wrote:
>>> Jon Turney wrote:
>>>> The following packages have been uploaded to the Cygwin distribution:
>>>> * cygport-0.35.2-1
>>>> cygport is the standard method for building and maintaining
>>>> packages for the Cygwin distribution.
>>>> Jon Turney (7):
>>>> Add LICENSE variable
>
>>> I would suggest to print a note or warning if LICENSE is missing.
>>> This may encourage maintainers to add it.
>
>> I second that emotion.
>> For those unconvinced, here's a friendly detailed explanation:
>> https://blog.codinghorror.com/pick-a-license-any-license/
> Good article! Great quote from comments:
> "Most developers will spend more time deciding on which license to use
> and figuring out the difference between all of the licenses than they
> will developing the app they want to license."
That is an orthogonal discussion: We already require that packages have
a definite license, and that it's an OSI approved one, so we know that
we can distribute it.
We just don't record that information in the package currently.
> I would suggest not yet, as there is no other documentation that it
> exists, what it should contain, or suggestions for use, and it would be
> annoying to maintainers if it appeared every time the .cygport is parsed
> during a build! It needs to be discussed some more on cygwin-apps.
>
> Perhaps a reminder at scallywag build or cygport upload, once the
> requirements have been documented?
Yes, the first step would be to warn at upload if license: is missing,
but we're not there yet.
I am proposing that the value of LICENSE should be a SPDX license
expression, and the documentation should now reflect that.
prev parent reply other threads:[~2022-07-17 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.118112b9-787c-9e8e-9ac8-650b17c8b49b@dronecode.org.uk>
[not found] ` <fd28d2c3-79c2-a278-6009-43c8de5c085b@t-online.de>
[not found] ` <1732944933.20220704193058@yandex.ru>
2022-07-04 19:41 ` [ANNOUNCEMENT] cygport 0.35.2-1 Brian Inglis
2022-07-17 11:19 ` Jon Turney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6dedeae9-4f9d-bc3e-e329-a96749cd6d9a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).