From: firstname.lastname@example.org To: Git Mailing List <email@example.com> Cc: "Sebastian Schuberth" <firstname.lastname@example.org>, "Ævar Arnfjörð Bjarmason" <email@example.com>, firstname.lastname@example.org Subject: Re: Pain points in Git's patch flow Date: Fri, 7 May 2021 19:08:55 -0700 [thread overview] Message-ID: <20210508020855.GF3986@localhost> (raw) In-Reply-To: <email@example.com> On 19.04.2021 17:49, Konstantin Ryabitsev wrote: >On Mon, Apr 19, 2021 at 07:54:37AM +0200, Sebastian Schuberth wrote: >> > of these proposed alternatives involve moving away from something that's >> > a distributed system today (E-Mail infrastructure, local clients), to >> > what's essentially some website run by a centralized entity, in some >> > cases proprietary. >> >> That's a good point, I admit I haven't thought of that. Probably >> because I also don't care much. So *does* it really matter? What >> exactly concerns you about a "centralized entity"? Is it the technical >> aspect of a single point of failure, or the political / social aspect >> of being dependent on someone you do not want to get influenced by? I >> guess it's a bit of both. > >Patches sent via email remain immune to this. Even if vger falls over, it's >merely a list service -- there are alternative ways of transmitting RFC2822 >messages that don't involve a central host (such as via a NNTP gateway, >publishing a public-inbox "feed", etc). Email remains one of the few protocols >that are designed ground-up to be decentralized and I'm afraid that we are >again finding ourselves in a world where this is increasingly relevant. I agree with Konstantin on this one. To this day, email is still the most decentralized and "user sovereign" system on the internet. The standardization of protocols and file formats is not perfect but it is "complete" in the sense that it meets all of the requirements for decentralized software development. Think about it like this. Right now, I could use an IMAP client to download all of my emails from GMail, store them in mbox files, then use the IMAP client to upload the email to Fastmail or SDF.org or some other email provider. Or better yet, I can install local tools for working with my email. The fact that email providers/tools are largely interchangeable and replacable--despite Google/Yahoo/Microsoft's best efforts--gives maximum power to users. Like I said, I totally agree with Konstantin and I think the vision he described in his post on developer sigchains is what I've always wanted as an open source developer. It is common to hear the argument that centralized systems are more convient and easier to use and the more decentralized a sysetem, the harder it gets to use. I suspect that is only a half-truth because I don't think we've achieved full decentralization which is what Konstantin touches on in his post too. Full decentralization will bring automatic maintainence of p2p connections and synchronization. Things will "just work". I know I'm veering off topic a bit here but decentralization has been the focus of all of my learning, research and work for more than a decade now. Email is critical for maintaining decentralized development capabilities. Cheers! Dave
next prev parent reply other threads:[~2021-05-08 2:09 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-14 6:13 Jonathan Nieder 2021-04-14 7:22 ` Bagas Sanjaya 2021-04-14 8:02 ` Junio C Hamano 2021-04-14 21:42 ` Junio C Hamano 2021-04-15 8:49 ` Denton Liu 2021-04-15 6:06 ` Junio C Hamano 2021-04-15 15:45 ` Son Luong Ngoc 2021-04-19 2:57 ` Eric Wong 2021-04-19 13:35 ` Theodore Ts'o 2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:21 ` Eric Wong 2021-04-28 7:05 ` Eric Wong 2021-04-15 18:25 ` Atharva Raykar 2021-04-16 19:50 ` Junio C Hamano 2021-04-16 20:25 ` Junio C Hamano 2021-05-02 5:35 ` ZheNing Hu 2021-04-18 8:29 ` Sebastian Schuberth 2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason 2021-04-19 2:58 ` Eric Wong 2021-04-19 5:54 ` Sebastian Schuberth 2021-04-19 6:04 ` Sebastian Schuberth 2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:23 ` Sebastian Schuberth 2021-04-19 22:34 ` Theodore Ts'o 2021-04-20 6:30 ` Sebastian Schuberth 2021-04-20 16:37 ` Theodore Ts'o 2021-04-30 20:45 ` Felipe Contreras 2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:36 ` Eric Wong 2021-04-19 19:49 ` Sebastian Schuberth 2021-04-19 22:00 ` Konstantin Ryabitsev 2021-05-08 2:10 ` dwh 2021-04-19 21:49 ` Konstantin Ryabitsev 2021-04-19 23:03 ` Stephen Smith 2021-05-08 2:08 ` dwh [this message] 2021-05-08 4:41 ` Bagas Sanjaya 2021-04-30 20:58 ` Felipe Contreras 2021-04-21 4:46 ` Daniel Axtens 2021-04-26 2:04 ` brian m. carlson 2021-04-26 14:24 ` Theodore Ts'o 2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:59 ` Eric Wong 2021-04-28 22:44 ` brian m. carlson 2021-04-30 20:16 ` Felipe Contreras 2021-04-30 20:35 ` Felipe Contreras 2021-04-30 21:09 ` Felipe Contreras
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210508020855.GF3986@localhost \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Pain points in Git'\''s patch flow' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).