public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: s7r <s7r@sky-ip.org>
Cc: Andy Schroder <info@AndySchroder.com>,
	bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Thu, 11 Jun 2015 11:27:46 +0200	[thread overview]
Message-ID: <20150611092744.GA2167@amethyst.visucore.com> (raw)
In-Reply-To: <557883A7.7030906@sky-ip.org>

On Wed, Jun 10, 2015 at 09:36:23PM +0300, 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.

I completely agree here. I'm not against migration if a much better option comes along, but e.g. paying for another provider sounds like nonsense when sourceforge does this for free (with some minor annoyances - other providers will have their own).

Paying per message is far-fetched, something that could work in economic theory with perfectly spherical people in their perfectly efficient market. In practice the likely result would be a mailing list only used for advertisement and promotion, and technical discussion and release announcements would disappear.

BTW for people that *don't* like sourceforge's web archive UI there are some other options via gmane:

http://dir.gmane.org/gmane.comp.bitcoin.devel

Wladimir



      parent reply	other threads:[~2015-06-11  9:27 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
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 [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=20150611092744.GA2167@amethyst.visucore.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=info@AndySchroder.com \
    --cc=s7r@sky-ip.org \
    /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