{"type":"rich","version":"1.0","author_name":"npub1xv3g4rkhj7eyape0cqjhc9g4ljdu5axqkgcdewma854a8r7e0mtsl5j2ga","author_url":"https://nostr.ae/npub1xv3g4rkhj7eyape0cqjhc9g4ljdu5axqkgcdewma854a8r7e0mtsl5j2ga","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-18\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nRecently I saw the following video:\n\nhttps://www.youtube.com/watch?v=8JmvkyQyD8w\u0026t=47m58s\n\nHadn't seen it until just today, although it was done on June 8, 2015.\nSo this is a bit dated, but to me it was a bit of a stunner to see the\nextreme nature of (some) of the views presented in this video.\n\nLet me be blunt, I have serious concerns regarding threats issued by a\ndeveloper in this video, and I think that it is entirely possible that\nthose of you who are core developers have already seen this and have\nbeen discussing it.  But I am interested in seeing this resolved here\non this list openly and having it resolved.  It's sad and unfortunate\nto me, but I feel that it's necessary to do this.  Identify what's\nhappening, address it squarely, have the person who is threatening\nothers explain his/her behavior, deal with the problem and move on.\nThis seems to be very important.  Please tell me if I am wrong about\nthis or totally flawed in my perspective here.  Go right ahead.\n\nIn this video, a particular developer makes the following statement,\nstating in part:\n\n\"My preferred solution is that Gavin revokes commit access from\neveryone else in the project, and then... makes the change himself\"\n\nRegardless of how you look at this, and even if we believe that Gavin\nwill not respond to that developer's request for a so-called\n\"solution,\" such a statement (by any developer) is indeed both a\nthreat and an act of sabotage against the larger bitcoin community.\nWe should certainly be thankful therefore, for the recent policy\nchange at bitcoin.org which can be seen here:\nhttps://cloud.githubusercontent.com/assets/61096/8173297/578483f8-1399-1\n1e5-8f48-96f33d12b996.png\n\nI firmly believe that any developer who made a statement suggesting\nthat commit access of others in the project be revoked so that they\ncan proceed with their personal plan, needs to answer for having made\nsuch a suggestion with a formal apology to this list, followed by an\nexplanation for why they themselves should not have their commit\naccess removed.\n\nOverall, however, this sort of bombastic, nuclear suggestion makes me\nseriously concerned for the future of bitcoin (as well as any\ncryptocurrency which has repositories on Github).\n\nSo, you know who you are:  Apologize for your statement (\"preferred\nsolution\") and explain to the community why you should still have\ncommit access in light of the threat you have made to all the other\ndevelopers (and indeed to all participants of the bitcoin community).\n These \"nuclear options\" are unacceptable to us all.\n\nRespectfully,\n\n- -O\n\n\n- -- \nhttp://abis.io ~\n\"a protocol concept to enable decentralization\nand expansion of a giving economy, and a new social good\"\nhttps://keybase.io/odinn\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQEcBAEBAgAGBQJVgoc3AAoJEGxwq/inSG8C6QYH/1Ag+4ESTSUPkP8PCTj1AJds\nJ4MmBz4cX7IYsSttTAjyiwd6oTHCU+wAcXtgZYpzr8rWF62bG5/+kAFUfjKwNsGM\nWqcdNOR6h8fQulx8niuro8kZF/xOsG5eHtRK2FMCorxj0t6qn4pH5WAQL73J3hXQ\nxI831Nt/L7VTa0jlKbr2/VGlqh6CtGrZ9mXp6aV1MBNwHbFryNBJW9ubvUv/IRxZ\nGyJ+c3+Br2KKAQTMsyNn3VXMlXJL6kt0pwwk2od3j/+dKE4pAetHvZ5OgIO+qUWd\n6R0/AaoW5jk343TaQ5BHaSpNW+OM9Yc1ycZyqE/YV8JwWeA6G/QdmRVYeoLMCZQ=\n=zJeO\n-----END PGP SIGNATURE-----"}