public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay•com>
To: Andy Schroder <info@andyschroder•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 12:54:25 -0700	[thread overview]
Message-ID: <CAJHLa0OHN-ouh5zXAHh-hTWd=Uh1TvhhxZQd_h3ChCKvbo7-0A@mail.gmail.com> (raw)
In-Reply-To: <55788924.6090008@AndySchroder.com>

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

On Wed, Jun 10, 2015 at 11:59 AM, Andy Schroder <info@andyschroder•com>
wrote:

>  Hello,
>
> A couple of motivations for a mailing list switch:
>
>    1. Sometimes the mailing list delays delivery for 10 minutes to
>    several days.
>    2. There are usually lots of ads at the footer of the messages. Really
>    confuses new readers (for me at least), and seems like it really pollutes
>    such a historical dialog that may be referenced long into the future. How
>    would it be if the 10 Commandments, Magna Carta, Bill of Rights, The Sermon
>    on the Mount, or The Gettysburg Address had ads intertwined within them?
>     3. Don't think HTML messages are allowed.
>    4. Seems like digital signatures are always broken on messages because
>    the list server slightly modifies them (?), so my e-mail client doesn't
>    verify them all.
>
> Not only -- mail header rewrites cause all my emails to go into people's
spam folders, if they were not directly listed in the To/CC headers...




>
>    1.
>
>
>
> Andy Schroder
>
> On 06/10/2015 02:36 PM, s7r wrote:
>
> The mail list is public, so it's not like the data on it is somehow
> sensitive. Sourcefoge is fine, it has a nice web UI where you can browse
> the message and sort/order them as you want, etc.
>
> Why would you want to move to a paid solution? And why would you want
> users to have to pay per message? This is the worst idea ever from my
> point of view. We want to encourage people to join the community, run
> full nodes, ask questions, come with solutions, ideas for improvements
> and so on. Everyone should read and write and contribute as much as
> possible with ideas in debates. You never know who can have bright ideas
> in some contexts.
>
> Bottom line is so far sourceforge handles the mail lists just fine. I
> don't see a single advantage another mail list provider / system could
> offer, except some headache and extra work for migration. The software
> distribution via sourcefoge was cancelled for obvious reasons which I
> fully understand and agree to, but it has nothing to do with the mail
> lists. We have way more important things to brainstorm about.
>
> On 6/10/2015 7:46 PM, Andy Schroder wrote:
>
>  Regarding changing the e-mail list provider. Is anyone interested in
> sponsoring it? There are non-free options, but it may be difficult to
> always ensure the fee is being paid to the provider. I think finding an
> agreeable free solution may have been the issue before? I've also
> thought of trying to make a pay per message or byte solution (and this
> cost could be dynamic based upon the number of current mailing list
> subscribers). This could solve the who pays problem (the sender pays),
> as well as motivate people to be more concise and clear with their
> messages, and at the same time limit spam.
>
>
>
> Any thoughts?
>
> Andy Schroder
>
> On 06/10/2015 05:35 AM, Wladimir J. van der Laan wrote:
>
>  On Wed, Jun 10, 2015 at 10:25:12AM +0200, xor wrote:
>
>  http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/
>
>  All our downloads (even old ones) have recently been deleted from sourceforge, for this reason. They haven't been mentioned in Bitcon Core release announcements for a long time.
>
> No opinion on the mailing list. Though I think it's less urgent. The issue of moving the mailinglist has come up before a few times and people can't agree where to move to.
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
>
>  ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing listBitcoin-development@lists•sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>


-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

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

  parent reply	other threads:[~2015-06-10 19:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  8:25 xor
2015-06-10  9:35 ` Wladimir J. van der Laan
2015-06-10 16:46   ` Andy Schroder
2015-06-10 18:02     ` Troy Benjegerdes
2015-06-10 18:41       ` Andy Schroder
     [not found]       ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
     [not found]         ` <20150610185810.GQ27932@nl.grid.coop>
     [not found]           ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11  1:46             ` Troy Benjegerdes
2015-06-10 18:28     ` Ivan Brightly
2015-06-10 18:47       ` Troy Benjegerdes
2015-06-10 19:13         ` Ivan Brightly
2015-06-10 18:36     ` s7r
2015-06-10 18:59       ` Andy Schroder
2015-06-10 19:03         ` Peter Todd
2015-06-10 19:12           ` Andy Schroder
2015-06-10 19:20             ` Peter Todd
2015-06-10 19:36               ` Andy Schroder
2015-06-10 19:43                 ` Peter Todd
2015-06-10 20:03                   ` Andy Schroder
2015-06-10 19:54         ` Jeff Garzik [this message]
2015-06-11  9:27       ` Wladimir J. van der Laan

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='CAJHLa0OHN-ouh5zXAHh-hTWd=Uh1TvhhxZQd_h3ChCKvbo7-0A@mail.gmail.com' \
    --to=jgarzik@bitpay$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=info@andyschroder$(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