📅 Original date posted:2015-06-14
📝 Original message:Hi,
I just wanted to let everyone know that every email is also archived at bitcoin-development.narkive.com <http://bitcoin-development.narkive.com/>;, where you can find everything since the beginning of the list (June 2011). That should answer to Andy’s concern about the older messages not being archived anywhere but on sourceforge.
Davide
> On 14 Jun 2015, at 23:59, Adam Back <adam at cypherspace.org> wrote:
>
> It might be as well to keep the archive but disable new posts as
> otherwise we create bit-rot for people who linked to posts on
> sourceforge.
>
> The list is also archived on mail-archive though.
> https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/
>
> Adam
>
> On 14 June 2015 at 22:55, Andy Schroder <info at andyschroder.com> wrote:
>> Hello,
>>
>> I'd support moving to a Linux Foundation e-mail list. I am also against
>> google groups. I agree that the gesture of moving indicates that SourceForge
>> is not playing nice on other issues and that moving this list shows their
>> behavior is being acknowledged.
>>
>> I understand your reason for wanting to delete the Source Forge account
>> (after reading the links). However, the only problem with that is that the
>> SourceForge archive is the oldest one I've found with some early messages
>> from Satoshi. Myself finding Bitcoin after its inception, as well as this
>> mailing list even later on, it's nice to be able to review the archives.
>> SourceForge's interface to those archives is pretty bad though. I'm not sure
>> if there is any way to get older messages archived on sites like gmane or
>> mail-archive? Does anyone know? You mentioned importing the list archive as
>> part of the migration plan, but I guess is this easy to do from SourceForge?
>>
>>
>> Andy Schroder
>>
>> On 06/14/2015 06:12 AM, Warren Togami Jr. wrote:
>>
>> Discomfort with Sourceforge
>>
>> For a while now people have been expressing concern about Sourceforge's
>> continued hosting of the bitcoin-dev mailing list. Downloads were moved
>> completely to bitcoin.org after the Sept 2014 hacking incident of the SF
>> project account. The company's behavior and perceived stability have been
>> growing to be increasingly questionable.
>>
>>
>> http://www.theregister.co.uk/2013/11/08/gimp_dumps_sourceforge_over_dodgy_ads_and_installer
>>
>> November 2013: GIMP flees SourceForge over dodgy ads and installer
>>
>> https://lwn.net/Articles/646118/
>>
>> May 28th, 2015: SourceForge replacing GIMP Windows downloads
>>
>> http://seclists.org/nmap-dev/2015/q2/194
>>
>> June 3rd, 2015: Sourceforge hijacked nmap's old site and downloads.
>>
>>
>> When this topic came up over the past two years, it seemed that most people
>> agreed it would be a good idea to move. Someone always suggests Google
>> Groups as the replacement host. Google is quickly shot down as too
>> controversial in this community, and it becomes an even more difficult
>> question as to who else should host it. Realizing this is not so simple,
>> discussion then dies off until the next time somebody brings it up.
>>
>>
>> http://sourceforge.net/p/bitcoin/mailman/bitcoin-development/thread/1943127.DBnVxmfOIh%401337h4x0r/#msg34192607
>>
>> Somebody brought it up again this past week.
>>
>>
>> It seems logical that an open discussion list is not a big deal to continue
>> to be hosted on Sourceforge, as there isn’t much they could do to screw it
>> up. I personally think moving it away now would be seen as a gesture that
>> we do not consider their behavior to be acceptable. There are also some
>> benefits in being hosted elsewhere, at an entity able to professionally
>> maintain their infrastructure while also being neutral to the content.
>>
>>
>> Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
>>
>>
>> Bitcoin is a global infrastructure development project where it would be
>> politically awkward for any of the existing Bitcoin companies or orgs to
>> host due to questions it would raise about perceived political control.Â
>> For example, consider a bizarro parallel universe where MtGox was the
>> inventor of Bitcoin, where they hosted its development infrastructure and
>> dev list under their own name. Even if what they published was 100%
>> technically and ideologically equivalent to the Bitcoin we know in our
>> dimension, most people wouldn't have trusted it merely due to appearances
>> and it would have easily gone nowhere.
>>
>>
>> I had a similar thought process last week when sidechains code was
>> approaching release. Sidechains, like Bitcoin itself, are intended to be a
>> generic piece of infrastructure (like ethernet?) that anyone can build upon
>> and use. We thought about Google Groups or existing orgs that already host
>> various open source infrastructure discussion lists like the IETF or the
>> Linux Foundation. Google is too controversial in this community, and the
>> IETF is seen as possibly too politically fractured. The Linux Foundation
>> hosts a bunch of infrastructure lists and it seems that nobody in the Open
>> Source industry considers them to be particularly objectionable. I talked
>> with LF about the idea of hosting generic Bitcoin-related infrastructure
>> development lists. They agreed as OSS infrastructure dev is already within
>> their charter, so early this week sidechains-dev list began hosting there.
>>
>>
>> From the perspective of our community, for bitcoin-dev it seems like a great
>> fit. Why? While they are interested in supporting general open source
>> development, the LF has literally zero stake in this. In addition to
>> neutrality, they seem to be suitable as a competent host. They have
>> full-time sysadmins maintaining their infrastructure including the Mailman
>> server. They are soon upgrading to Mailman 3, which means mailing lists
>> would benefit from the improved archive browser. I am not personally
>> familiar with HyperKitty, but the point here is they are a stable non-profit
>> entity who will competently maintain and improve things like their Mailman
>> deployment (a huge improvement over the stagnant Sourceforge). It seems
>> that LF would be competent, neutral place to host dev lists for the
>> long-term.
>>
>>
>> To be clear, this proposal is only about hosting the discussion list. The
>> LF would have no control over the Bitcoin Project, as no single entity
>> should.
>>
>>
>> Proposed Action Plan
>>
>>
>> Discuss this openly within this community. Above is one example of a great
>> neutral and competent host. If the technical leaders here can agree to
>> move to a particular neutral host then we do it.
>>
>> Migration: The current list admins become the new list admins. We import
>> the entire list archive into the new host's archives for user convenience.
>>
>> http://sourceforge.net/p/bitcoin/mailman/ Â Kill bitcoin-list and
>> bitcoin-test. Very few people actually use it. Actually, let's delete
>> the entire Bitcoin Sourceforge project as its continued existence serves no
>> purpose and it only confuses people who find it. By deletion, nobody has
>> to monitor it for a repeat of the Sept 2014 hacking incident or GIMP-type
>> hijacking?
>>
>> The toughest question would be the appropriateness of auto-importing the
>> subscriber list to another list server, as mass imports have a tendency to
>> upset people.
>>
>>
>> Thoughts?
>>
>>
>> Warren Togami
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150615/7a01af58/attachment.html>;
Davide Cavion [ARCHIVE] /
npub1u8…hhwve
2023-06-07 15:37:53
in reply to nevent1q…fww4
Author Public Key
npub1u8lcqavvfp7rqjwxdc8s0hjpjsrcqg9teactyelpfg52ph9gx68s9hhwveSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:37:53Event JSON
{
"id": "c83e7bb319207cac6b21e7c047b2cd1bf25cd760593e5b975c0848a7764a6f75",
"pubkey": "e1ff80758c487c3049c66e0f07de4194078020abcf70b267e14a28a0dca8368f",
"created_at": 1686152273,
"kind": 1,
"tags": [
[
"e",
"810d20bcf991f0775ab3cca311351e013d4d782191b318764a6f2045d4a0f082",
"",
"root"
],
[
"e",
"85f7cbf0b3979a1ef57d9be078e0daa755a4491ea25f64efa6cb84c1a61e0d7e",
"",
"reply"
],
[
"p",
"ee0fa66772f633411e4432e251cfb15b1c0fe8cd8befd8b0d86eb302402a8b4a"
]
],
"content": "📅 Original date posted:2015-06-14\n📝 Original message:Hi,\n\nI just wanted to let everyone know that every email is also archived at bitcoin-development.narkive.com \u003chttp://bitcoin-development.narkive.com/\u003e, where you can find everything since the beginning of the list (June 2011). That should answer to Andy’s concern about the older messages not being archived anywhere but on sourceforge.\n\nDavide\n\n\n\u003e On 14 Jun 2015, at 23:59, Adam Back \u003cadam at cypherspace.org\u003e wrote:\n\u003e \n\u003e It might be as well to keep the archive but disable new posts as\n\u003e otherwise we create bit-rot for people who linked to posts on\n\u003e sourceforge.\n\u003e \n\u003e The list is also archived on mail-archive though.\n\u003e https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/\n\u003e \n\u003e Adam\n\u003e \n\u003e On 14 June 2015 at 22:55, Andy Schroder \u003cinfo at andyschroder.com\u003e wrote:\n\u003e\u003e Hello,\n\u003e\u003e \n\u003e\u003e I'd support moving to a Linux Foundation e-mail list. I am also against\n\u003e\u003e google groups. I agree that the gesture of moving indicates that SourceForge\n\u003e\u003e is not playing nice on other issues and that moving this list shows their\n\u003e\u003e behavior is being acknowledged.\n\u003e\u003e \n\u003e\u003e I understand your reason for wanting to delete the Source Forge account\n\u003e\u003e (after reading the links). However, the only problem with that is that the\n\u003e\u003e SourceForge archive is the oldest one I've found with some early messages\n\u003e\u003e from Satoshi. Myself finding Bitcoin after its inception, as well as this\n\u003e\u003e mailing list even later on, it's nice to be able to review the archives.\n\u003e\u003e SourceForge's interface to those archives is pretty bad though. I'm not sure\n\u003e\u003e if there is any way to get older messages archived on sites like gmane or\n\u003e\u003e mail-archive? Does anyone know? You mentioned importing the list archive as\n\u003e\u003e part of the migration plan, but I guess is this easy to do from SourceForge?\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Andy Schroder\n\u003e\u003e \n\u003e\u003e On 06/14/2015 06:12 AM, Warren Togami Jr. wrote:\n\u003e\u003e \n\u003e\u003e Discomfort with Sourceforge\n\u003e\u003e \n\u003e\u003e For a while now people have been expressing concern about Sourceforge's\n\u003e\u003e continued hosting of the bitcoin-dev mailing list. Downloads were moved\n\u003e\u003e completely to bitcoin.org after the Sept 2014 hacking incident of the SF\n\u003e\u003e project account. The company's behavior and perceived stability have been\n\u003e\u003e growing to be increasingly questionable.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e http://www.theregister.co.uk/2013/11/08/gimp_dumps_sourceforge_over_dodgy_ads_and_installer\n\u003e\u003e \n\u003e\u003e November 2013: GIMP flees SourceForge over dodgy ads and installer\n\u003e\u003e \n\u003e\u003e https://lwn.net/Articles/646118/\n\u003e\u003e \n\u003e\u003e May 28th, 2015: SourceForge replacing GIMP Windows downloads\n\u003e\u003e \n\u003e\u003e http://seclists.org/nmap-dev/2015/q2/194\n\u003e\u003e \n\u003e\u003e June 3rd, 2015: Sourceforge hijacked nmap's old site and downloads.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e When this topic came up over the past two years, it seemed that most people\n\u003e\u003e agreed it would be a good idea to move. Someone always suggests Google\n\u003e\u003e Groups as the replacement host. Google is quickly shot down as too\n\u003e\u003e controversial in this community, and it becomes an even more difficult\n\u003e\u003e question as to who else should host it. Realizing this is not so simple,\n\u003e\u003e discussion then dies off until the next time somebody brings it up.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e http://sourceforge.net/p/bitcoin/mailman/bitcoin-development/thread/1943127.DBnVxmfOIh%401337h4x0r/#msg34192607\n\u003e\u003e \n\u003e\u003e Somebody brought it up again this past week.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e It seems logical that an open discussion list is not a big deal to continue\n\u003e\u003e to be hosted on Sourceforge, as there isn’t much they could do to screw it\n\u003e\u003e up. I personally think moving it away now would be seen as a gesture that\n\u003e\u003e we do not consider their behavior to be acceptable. There are also some\n\u003e\u003e benefits in being hosted elsewhere, at an entity able to professionally\n\u003e\u003e maintain their infrastructure while also being neutral to the content.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Proposal: Move Bitcoin Dev List to a Neutral Competent Entity\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Bitcoin is a global infrastructure development project where it would be\n\u003e\u003e politically awkward for any of the existing Bitcoin companies or orgs to\n\u003e\u003e host due to questions it would raise about perceived political control.Â\n\u003e\u003e For example, consider a bizarro parallel universe where MtGox was the\n\u003e\u003e inventor of Bitcoin, where they hosted its development infrastructure and\n\u003e\u003e dev list under their own name. Even if what they published was 100%\n\u003e\u003e technically and ideologically equivalent to the Bitcoin we know in our\n\u003e\u003e dimension, most people wouldn't have trusted it merely due to appearances\n\u003e\u003e and it would have easily gone nowhere.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e I had a similar thought process last week when sidechains code was\n\u003e\u003e approaching release. Sidechains, like Bitcoin itself, are intended to be a\n\u003e\u003e generic piece of infrastructure (like ethernet?) that anyone can build upon\n\u003e\u003e and use. We thought about Google Groups or existing orgs that already host\n\u003e\u003e various open source infrastructure discussion lists like the IETF or the\n\u003e\u003e Linux Foundation. Google is too controversial in this community, and the\n\u003e\u003e IETF is seen as possibly too politically fractured. The Linux Foundation\n\u003e\u003e hosts a bunch of infrastructure lists and it seems that nobody in the Open\n\u003e\u003e Source industry considers them to be particularly objectionable. I talked\n\u003e\u003e with LF about the idea of hosting generic Bitcoin-related infrastructure\n\u003e\u003e development lists. They agreed as OSS infrastructure dev is already within\n\u003e\u003e their charter, so early this week sidechains-dev list began hosting there.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e From the perspective of our community, for bitcoin-dev it seems like a great\n\u003e\u003e fit. Why? While they are interested in supporting general open source\n\u003e\u003e development, the LF has literally zero stake in this. In addition to\n\u003e\u003e neutrality, they seem to be suitable as a competent host. They have\n\u003e\u003e full-time sysadmins maintaining their infrastructure including the Mailman\n\u003e\u003e server. They are soon upgrading to Mailman 3, which means mailing lists\n\u003e\u003e would benefit from the improved archive browser. I am not personally\n\u003e\u003e familiar with HyperKitty, but the point here is they are a stable non-profit\n\u003e\u003e entity who will competently maintain and improve things like their Mailman\n\u003e\u003e deployment (a huge improvement over the stagnant Sourceforge). It seems\n\u003e\u003e that LF would be competent, neutral place to host dev lists for the\n\u003e\u003e long-term.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e To be clear, this proposal is only about hosting the discussion list. The\n\u003e\u003e LF would have no control over the Bitcoin Project, as no single entity\n\u003e\u003e should.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Proposed Action Plan\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Discuss this openly within this community. Above is one example of a great\n\u003e\u003e neutral and competent host. If the technical leaders here can agree to\n\u003e\u003e move to a particular neutral host then we do it.\n\u003e\u003e \n\u003e\u003e Migration: The current list admins become the new list admins. We import\n\u003e\u003e the entire list archive into the new host's archives for user convenience.\n\u003e\u003e \n\u003e\u003e http://sourceforge.net/p/bitcoin/mailman/  Kill bitcoin-list and\n\u003e\u003e bitcoin-test. Very few people actually use it. Actually, let's delete\n\u003e\u003e the entire Bitcoin Sourceforge project as its continued existence serves no\n\u003e\u003e purpose and it only confuses people who find it. By deletion, nobody has\n\u003e\u003e to monitor it for a repeat of the Sept 2014 hacking incident or GIMP-type\n\u003e\u003e hijacking?\n\u003e\u003e \n\u003e\u003e The toughest question would be the appropriateness of auto-importing the\n\u003e\u003e subscriber list to another list server, as mass imports have a tendency to\n\u003e\u003e upset people.\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Thoughts?\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e Warren Togami\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e \n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e \n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e \n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150615/7a01af58/attachment.html\u003e",
"sig": "499feb2b297e7a4ee2a20951bfafc239b93ba08cb03cc34b4e35655dca5c58d43bdad76ca7ff0695e7fde8532bee2150e9e16731ce4b6651f2f731091bc76884"
}