From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
Date: Thu, 11 Jun 2020 22:47:28 +0000
Message-ID: <bug-374-13-RtFAx4rr8i@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=374
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
the idea came up in the virtual coffee call today: it is for searchability,
to indicate the existence of the project. a single file with a README
explaining that libre-soc is a Libre Project (not an "Open Source" one)
with a single link to the website would achieve this.
if the project's source code is actually mirrored *on* github, it indicates
an implicit endorsement by the project that proprietary services are
acceptable.
this GNU page explains the criteria:
https://www.gnu.org/software/repo-criteria.en.html
and this page evaluates commonly available and commonly used services:
https://www.gnu.org/software/repo-criteria-evaluation.html
of course we cannot prevent or prohibit *individuals* from utilising github:
that would be completely inappropriate, and the GNU project goes to some
lengths to explain how best to communicate that effectively and respectfully.
if however we wish to properly demonstrate a committment to ethical principles,
i.e. actually *be* a Libre Project, then respecting the GNU guidelines is
a good example to follow.
grey area: i am... "okay with" the idea of putting a single page README - not
in
any way under an "officially sanctioned" github username (registration of
github.com/libre-soc would be completely inappropriate) - under *personal*
github accounts, just to get at least something into github search criteria,
as long as it is just a single page, with a single link, and a short sentence
explaining that we are a Libre Project, following and respecting the GNU
Ethical Hosting guidelines.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 22:17 [libre-riscv-dev] [Bug 374] New: " bugzilla-daemon
2020-06-11 22:19 ` [libre-riscv-dev] [Bug 374] " bugzilla-daemon
2020-06-11 22:19 ` bugzilla-daemon
2020-06-11 22:47 ` bugzilla-daemon [this message]
2020-06-11 22:48 ` bugzilla-daemon
2020-06-11 22:50 ` bugzilla-daemon
2020-06-11 22:55 ` bugzilla-daemon
2020-06-11 23:00 ` bugzilla-daemon
2020-06-11 23:01 ` bugzilla-daemon
2020-06-11 23:03 ` bugzilla-daemon
2020-06-12 11:55 ` bugzilla-daemon
2020-06-12 11:55 ` bugzilla-daemon
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=bug-374-13-RtFAx4rr8i@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git