public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Zac Greenwood <zachgrw@gmail.com>
To: Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>, jack <jack@squareup.com>
Cc: Prayank <prayank@tutanota.de>, info@bitcoindefensefund.org
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Fri, 21 Jan 2022 15:36:10 +0100	[thread overview]
Message-ID: <CAJ4-pEC5tBpXOe_q+62ehAPNvo3aLNL8LK4TBgPDAH20akOeTg@mail.gmail.com> (raw)
In-Reply-To: <F3DA4333-E4BB-4A3F-B050-AA142465F2C8@squareup.com>

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

The name of the fund should ideally unambiguously clarify its scope, i.e.,
Bitcoin & development. So maybe “Bitcoin Developers Community LDF”. Or
perhaps “Bitcoin Technical Community LDF” which nicely abbreviates to
BTCLDF.

Zac


On Thu, 13 Jan 2022 at 19:49, jack via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi Prayank,
>
> > On 13 Jan 2022, at 10:13, Prayank <prayank@tutanota.de> wrote:
> > I had few suggestions and feel free to ignore them if they do not make
> sense:
> >
> > 1.Name of this fund could be anything and 'The Bitcoin Legal Defense
> Fund' can be confusing or misleading for newbies. There is nothing official
> in Bitcoin however people believe things written in news articles and some
> of them might consider it as an official bitcoin legal fund.
>
> Excellent point. Will come up with a better name.
>
> Open to ideas and suggestions on all.
>
> jack
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1835 bytes --]

  parent reply	other threads:[~2022-01-21 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 10:13 [bitcoin-dev] Bitcoin Legal Defense Fund Prayank
2022-01-13 18:20 ` jack
2022-01-14 13:21   ` Aymeric Vitte
2022-01-14 18:18     ` qmccormick13
2022-01-14 18:34       ` Jeremy
2022-01-21 14:36   ` Zac Greenwood [this message]
2022-01-13 18:28 ` Steve Lee
2022-01-13 18:54   ` Alex Schoof
2022-01-13 19:28     ` Steve Lee
2022-01-13 19:05   ` Jeremy
2022-01-13 20:50     ` Antoine Riard
  -- strict thread matches above, loose matches on Subject: below --
2022-01-12  9:59 SatoshiSingh
2022-01-12  0:13 jack
2022-01-12  0:47 ` René Pickhardt
2022-01-12  1:42   ` Christopher Allen
2022-01-13 19:25   ` Alex Morcos

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=CAJ4-pEC5tBpXOe_q+62ehAPNvo3aLNL8LK4TBgPDAH20akOeTg@mail.gmail.com \
    --to=zachgrw@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=info@bitcoindefensefund.org \
    --cc=jack@squareup.com \
    --cc=prayank@tutanota.de \
    /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