From: Leo Famulari <leo@famulari.name>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: Giving up on RubyGems
Date: Tue, 20 Oct 2015 15:19:10 -0400 [thread overview]
Message-ID: <20151020191910.GA19646@jasmine> (raw)
In-Reply-To: <87eggpya7p.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me>
On Tue, Oct 20, 2015 at 08:51:22AM -0400, David Thompson wrote:
> I've grown very tired of trying to convince people that independent user
> verification of binary releases is an important thing to prioritize, but
> they think that users do not want the source code. I've tried to make
> my arguments as clear as I could, yet they've been misunderstood by some
> and rejected entirely by others, and now it is time to give up.
As someone with zero Ruby experience, I find this very confusing. Are
you saying that they don't think it's necessary to be able to build the
Gem "binaries" independently? If that were true, how can RubyGems be a
trusted intermediary between software authors and users? How can users
verify that the RubyGems people are not distributing malicious
"binaries". Am I totally misunderstanding the role of RubyGems in the
Ruby world?
> This effort has drained too much of my enthusiasm, and now I need a
> break.
:( We all have experiences like this once in a while. Everyone
appreciates the work you do on Guix. Hopefully you can come back with
some fresh energy when you are ready!
next prev parent reply other threads:[~2015-10-20 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 12:51 Giving up on RubyGems David Thompson
2015-10-20 13:14 ` Taylan Ulrich Bayırlı/Kammer
2015-10-20 13:32 ` Ludovic Courtès
2015-10-20 14:18 ` John Darrington
2015-10-20 19:19 ` Leo Famulari [this message]
2015-10-21 9:46 ` Pjotr Prins
2015-10-21 12:43 ` Thompson, David
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151020191910.GA19646@jasmine \
--to=leo@famulari.name \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).