Embrace, extend, and finally extinguish - Microsoft plays their hand
@sir found a typo, thought I'd report back
@awalvie thanks, pushing a fix
@sir well written. In Addition I think is is really maddening how many developers and their managers think that git and github are identical... or that Micro$oft acquiered git..
> “Relying on plain-text email is a ‘barrier to entry’ for kernel development, says Linux Foundation board member”, a title which conveniently chooses to refer to Sarah Novotny by her role as a Linux Foundation board member, rather than by her full title, “Sarah Novotny, Microsoft employee, transitive owner of GitHub, and patroness saint of conflicts of interests.”
I’ll look into what you are doing with sourcehut and if that makes it any better, but I’m not 100% ready to chalk this up as one of Microsoft’s crimes just yet.
Question. Is sourcehut just a website, or can we download and install it in our own servers for public or private use?
Looks a bit complicated for the layperson but I'm glad there are already Debian packages for it.
Let's hope it gets widespread adoption.
BTW, the page says it's distributed. Does that mean I can fork a repo from another sourcehut server into my own? Or what do you mean exactly when you say "distributed"?
@sir I really liked the bluntly phrased "open source is a means to an end for us" part in the article. The end being to sabotage all competition.
To me it's pretty obious MS still treats FOSS like the cancer they believe it is.
@sir This is well-written. I'm always impressed by your blog posts.
You seem to have strong opinions about stuff like this, but you put in the work and put your money where your mouth is. More power to you
@sir One would assume that a person competent enough to patch the kernel, will be able to configure their client for plain-text email, right?
@sirjofri @x @sir my stance on this is similar to Taleb's (below): forcing cultural and procedural shifts in the name of abstract accessibility makes that way of living the only way of living, and wow, it plays into corporate playbooks too?
sometimes you have to learn the way it works to be a member, and everyone is better for it.
@am thanks for sharing, I'm not done reading but so far it's excellent, I was hoping it would talk about linguistics and it does!
rather than saying, "use one of 50 possibly maintained email clients that somebody has used successfully. plus also probably some other fun stuff that you may not have experience with, but you can figure that out." and feeling smug about having jumped through those (technically unnecessary) hoops yourself, you *could* say, "download this program that speaks both git and email and you're good to go."
somehow nobody thought of that since the 90s
I think it's fine to say that there should be arbitrary and artificial barriers to entry for things like contributing code to the Linux kernel, or whatever rules you have for your own project. It's yours, after all.
I don't think it's fine to tell people that setting up and using 'plain-text email' (as needed to participate in this particular thing) is actually easy or straightforward or a good use of every person's time if they weren't already required to be using it.
For me in particular, it wouldn't be a good use of my time. I don't have any use for that particular style of plain-text email patching workflow anymore, since I'm not involved with any projects that use it.
If I wanted to make a one-off patch to fix some small thing, but I was mandated to jump through the hoops to set up all of that stuff to submit it, I probably wouldn't. (1/2)
It's fine for other people's projects to use or mandate it, though. It's their projects! They can do whatever they want. But it is a barrier to entry. That may be a good or bad thing.
I've done this at least twice over the years. Setting up maildir or mbsync and mutt or alpine or the emacs thing and notmuch... the thing I end up with in the end is only good for that particular style of email, not support emails with customers or w/e
are you sure you want them to do that? it's not like they do this by accident.
@sir Ha! It was only a matter of time, like the scorpion riding the frog across the river, it’s their nature.
Npm is next.
@hxii "There is a reason(few reasons, actually :) ) why GitHub has more than 50 million active developers using it, and why it became the de facto home of Open Source."
Yeah, marketing and money.
Note that they didn't bother explaining any of those reasons
I can't trust it. The "de facto home of Open Source" which is closed source itself.
Developers also choose GitHub for the visibility it gives to their projects, for the "everybody is there", "it's easier to get people involved", etc.
It's the path of least resistance.
People just don't give a f*ck.
I hate it.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!