Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
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 23:00:39 +0000
Message-ID: <bug-374-13-0Y95jpDkw4@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 #7 from Yehowshua <yimmanuel3@gatech.edu> ---
> sadly whilst very "convenient", this indicates that our project endorses
> github's
> unethical practices.  this includes censorship and government sanctioning.

I disagree. Mirroring indicates that we do not endorse their practices.

But COLLABORATING on Github would be a different story.

And for that matter, I generally feel that Github has done a much better job at
handling open source than SourceForge did.
I generally try to maintain personal projects in such a way that migration away
from Github is possible and am careful with personal information.

-- 
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

  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
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 [this message]
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-0Y95jpDkw4@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