From: Mike Hearn <mike@plan99•net>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Something people are forgetting about the Gentoo / Luke-jr censorship issue
Date: Fri, 10 Oct 2014 19:26:49 +0200 [thread overview]
Message-ID: <CANEZrP3NDFq8RJMH_OwH=9r3nOvLt4vhToy8qDnLzHb7EsP9iw@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0OcTFKdg8+ZLjaTqSQkGeqBARfKSb81fWMRM2RRBV=Jig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
I'm sure this suggestion will go down like a lead balloon, but Bitcoin Core
is not the first project that's had issues with Linux distros silently
modifying their software as they package it. In this case Luke has changed
things to be closer to what users expect, which is good to see, but I
expect to see the same issue crop up with other Linux distributions in
future. The temptation to "improve" things when you're a middleman is just
too great.
The usual approach to fixing it is trademark the project name and use that
to enforce "clean" packaging. Firefox and Chrome both take this approach.
I'll probably do the same with Lighthouse (need to figure out the
trademarking process first).
The goal here is not to remove choice, rather to ensure people know what
they're getting. It's reasonable to assume if you do "emerge bitcoin" then
you're getting Bitcoin Core as distributed by bitcoin.org, not a highly
opinionated fork of it. Renaming a project and creating a package under the
new name is not only better for end users, but lets the fork grow into
something else and be more usable to people on other distros too.
In this case "Bitcoin" is already a trademark, though I lost track of who
owns it at the moment (the foundation?) but I guess Bitcoin Core is not.
[-- Attachment #2: Type: text/html, Size: 1624 bytes --]
next prev parent reply other threads:[~2014-10-10 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:22 xor
2014-10-10 16:42 ` Jeff Garzik
2014-10-10 17:26 ` Mike Hearn [this message]
2014-10-10 18:41 ` Justus Ranvier
2014-10-10 19:02 ` Thomas Zander
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='CANEZrP3NDFq8RJMH_OwH=9r3nOvLt4vhToy8qDnLzHb7EsP9iw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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