From: "David A. Harding" <dave@dtrt•org>
To: Jonas Schnelli <dev@jonasschnelli•ch>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ads on bitcoin.org website
Date: Fri, 13 Nov 2015 10:59:16 -0500 [thread overview]
Message-ID: <20151113155915.GA3822@localhost.localdomain> (raw)
In-Reply-To: <564590F4.8040605@jonasschnelli.ch>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
On Fri, Nov 13, 2015 at 08:27:48AM +0100, Jonas Schnelli via bitcoin-dev wrote:
> I'm a little bit concerned about the future of bitcoin.org.
Bitcoin.org hosts the Bitcoin Core binaries refered to in release
announcements, so this subject is conceivably on-topic for bitcoin-dev.
However, I think questions about how Bitcoin.org operates are best asked
on bitcoin-discuss[1] (or somewhere else) and issues about the
advertising are best addressed in the PRs you referenced.
So, as one of the Bitcoin.org maintainers, here are my suggestions:
1. I'm on bitcoin-discuss. Please feel free to ask any questions there.
2. I just opened a GitHub issue for discussing advertising on Bitcoin.org[2]
- I will reply to your specific questions there after I've sent this
mail.
3. If advertisements are added to Bitcoin.org and there is general
dissatisfaction about that, maybe then we can come back to
bitcoin-dev to discuss moving the Bitcoin Core binaries
somewhere else.
Thanks,
-Dave
[1] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-discuss
[2] https://github.com/bitcoin-dot-org/bitcoin.org/issues/1139
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-11-13 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 7:27 Jonas Schnelli
2015-11-13 15:59 ` David A. Harding [this message]
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=20151113155915.GA3822@localhost.localdomain \
--to=dave@dtrt$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dev@jonasschnelli$(echo .)ch \
/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