public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ivan Brightly <ibrightly@gmail.com>
To: Andy Schroder <info@andyschroder.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 14:28:55 -0400	[thread overview]
Message-ID: <CAAre=yQSkFAHLfJ0h2rQY5vOFExSq2GDiRV32qe=EEVYOxCpqg@mail.gmail.com> (raw)
In-Reply-To: <557869F9.8030109@AndySchroder.com>

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

I like elegant solutions and while eventually I can see a "pay to
contribute" service, I don't imagine you'll get consensus in short order.

List provider costs are pretty reasonable, so if that's the hurdle to
overcome I'm happy to offer sponsorship.

Ivan Brightly
SolidX Partners

On Wed, Jun 10, 2015 at 12:46 PM, Andy Schroder <info@andyschroder.com>
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 list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

  parent reply	other threads:[~2015-06-10 18:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  8:25 [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? 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 [this message]
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
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='CAAre=yQSkFAHLfJ0h2rQY5vOFExSq2GDiRV32qe=EEVYOxCpqg@mail.gmail.com' \
    --to=ibrightly@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=info@andyschroder.com \
    /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