From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New Package: ivpn-3.4.5
Date: Sun, 12 Dec 2021 18:53:53 +0100 [thread overview]
Message-ID: <20211212175353.CSosxylySUFTQrt5a_15Yc8ZgwdoHRsorc6c5F3wD4E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34435@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
New review comment by NeelChotai on void-packages repository
https://github.com/void-linux/void-packages/pull/34435#discussion_r767307027
Comment:
This feels a little out of place for me since it's a EULA of the IVPN service rather than the software. As maintainers, we're only providing the software and in my eyes any acceptance of a service agreement is between the service provider and the user.
If you agree, this doesn't need to be in the nonfree repo since the build scripts seem to be pulling in all open source software and the licence should be changed to GPL3-only.
next prev parent reply other threads:[~2021-12-12 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 6:00 [PR PATCH] " b-l-a-i-n-e
2021-12-12 17:53 ` NeelChotai [this message]
2021-12-12 17:58 ` [PR REVIEW] " NeelChotai
2021-12-13 3:44 ` b-l-a-i-n-e
2021-12-13 3:55 ` b-l-a-i-n-e
2021-12-13 4:07 ` [PR PATCH] [Updated] " b-l-a-i-n-e
2021-12-13 4:08 ` b-l-a-i-n-e
2021-12-14 2:50 ` NeelChotai
2021-12-14 2:50 ` NeelChotai
2021-12-14 2:50 ` NeelChotai
2022-02-01 16:58 ` b-l-a-i-n-e
2022-02-01 16:58 ` [PR PATCH] [Closed]: " b-l-a-i-n-e
2023-02-24 14:01 ` niels0n
2023-02-24 16:33 ` b-l-a-i-n-e
2023-02-24 16:48 ` niels0n
2023-02-24 17:10 ` b-l-a-i-n-e
2023-02-24 17:35 ` b-l-a-i-n-e
2023-02-24 18:42 ` niels0n
2023-02-24 18:47 ` niels0n
2023-02-26 8:59 ` niels0n
2023-02-26 8:59 ` niels0n
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=20211212175353.CSosxylySUFTQrt5a_15Yc8ZgwdoHRsorc6c5F3wD4E@z \
--to=neelchotai@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).