Posts
2041
Following
230
Followers
2519
Director of Linux Foundation IT. Currently in charge of kernel.org infra.

This account is for Linux/Kernel/FOSS topics in general: #linux, #kernel, #foss, #git, #sysadmin, #infrastructure.

For my personal account, please follow @monsieuricon@castoranxieux.ca.

Montréal, Québec, Canada 🇨🇦🇺🇦
monsieuricon

K. Ryabitsev 🍁

Reply to
@raggi @Conan_Kudo @jacksonchen666 @marcan I will agree with you regarding SMTP, but RFC2822 (the "email message" standard) is only a mess because it's old and full of questionable legacy workarounds that were necessary to deal with the early internet (7-bit SMTP protocols, mainly).

If we no longer need to worry about that legacy and can stick to the latest 8-bit-clean standard, the format is quite robust and solid.
1
0
0
monsieuricon

K. Ryabitsev 🍁

Reply to
@raggi @Conan_Kudo @jacksonchen666 @marcan ActivityPub doesn't really bring us anything we don't already have with RFC2822 and SMTP, though. It's just another way of doing the exact same thing, with the exact same inherent problems.

ActivityPub is pretty new and niche, so it hasn't yet been fully abused by spammers and other bad actors, but as time goes on it *will* get all the same kinds of horrible spam-avoidance workarounds that make email seem lossy and unreliable. :(
0
0
0
monsieuricon

K. Ryabitsev 🍁

Reply to
@raggi @Conan_Kudo @jacksonchen666 @marcan Yeah, but people problem is the hardest problem! Believe me, for every person who is raving about how much they hate the process, there's another person who raves how much they love the process for its decentralized, no-single-point-of-failure, everything-is-in-my-inbox kinds of features.
0
0
1
monsieuricon

K. Ryabitsev 🍁

Reply to
@marcan @Conan_Kudo @jacksonchen666

Everyone recognizes that the status quo is inefficient -- everyone just disagrees about how to fix it, and if "don't care if it's down for a month" is acceptable to you, it's not acceptable to many others.

I do have a foot in this dance -- I have been working on a workflow tool that makes it easy to submit patch series and participate in code review. My hope is that we can use evolutionary approach to improve the status quo.

https://b4.docs.kernel.org/en/latest/contributor/overview.html

I have a feeling that it may improve your life as a person who is trying to submit something to upstream.

(I do have a request -- please don't use obscenities in this conversation, because it just raises the emotional degree without actually bringing anything constructive to the table. I'm not really here to yell at anyone, so please don't yell at me.)
0
0
6
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @jacksonchen666 @vincent @marcan I'm not convinced this is accurate. It's easy to blame tooling, which is the most visible part of the process. However, I'm pretty sure if we replace this with the most amazing workflow of submitting and reviewing the code, we'll still be 90% in the same situation, because:

1. Writing kernel code is hard
2. Reviewing kernel code is even harder
3. Upstreaming to rapidly-moving mainline is the hardest

We need maintainers, preferably well-paid teams of maintainers, much more than we need a shiny code review toolset.
2
6
13
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @jacksonchen666 @vincent @marcan if the solution is to fall back to what we're doing now, then we've not really solved anything, just complicated the process and made it more fragile.
1
0
1
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @jacksonchen666 @vincent @marcan kernel.org was offline for months in 2011 and Linux releases kept going out.
1
0
1
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @jacksonchen666 @vincent @marcan no it isn't. If you knock out kernel.org, developers can still collaborate using the same process (email review) and put out a release that can be verified for authenticity by its digital signature.
0
0
0
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @vincent @marcan @jacksonchen666 SMTP is not the only channel for passing around RFC2822 messages, though. However, it remains the only widely used distributed protocol for doing so.
0
0
0
monsieuricon

K. Ryabitsev 🍁

Reply to
@Conan_Kudo @vincent @marcan @jacksonchen666 a single point of failure platform is also not really acceptable. Imagine that you're sitting on a zero-day exploit of the Linux kernel and you want to prevent a fix from going out. Knocking out the central code management system is the logical move.
1
0
1
monsieuricon

K. Ryabitsev 🍁

Reply to
@marcan @Conan_Kudo @jacksonchen666 how do we manage to both provide a better workflow *and* avoid lock-in into an open-core tool like gitlab?

(I'm not trying to be contrary, this is literally my worry.)
4
0
3
monsieuricon

K. Ryabitsev 🍁

Reply to
@sjvn @jamesbelchamber @mattdm @jbowen Thankfully, I’m not a maintainer. :) The best way to describe what I do is “keeper of keys and grounds,” like Hagrid.
0
0
3
monsieuricon
repeated
LinuxSecSummit

Linux Security Summit 🐧

📣 The CfP for the 2023 Linux Security Summit North America is now open! 📣

See: https://events.linuxfoundation.org/linux-security-summit-north-america/program/cfp/

LSS-NA 2023 will be held in Vancouver, BC, Canada from May 10-12.

CfP submissions are open until March 1st!

#linux #linuxsecuritysummit #linuxfoundation #security #infosec
1
6
5
monsieuricon

K. Ryabitsev 🍁

Neat discovery of the day -- tut version 2.0.x will now properly auto-refresh content from social.kernel.org.

Try it out if you haven't for a while.
https://github.com/RasmusLindroth/tut
0
0
2
monsieuricon

K. Ryabitsev 🍁

Reply to
@jamesbelchamber @mattdm @jbowen @sjvn I guess you could say that when it comes to the Linux kernel development world, I *am* kind of its secretary. :)
1
0
7
monsieuricon

K. Ryabitsev 🍁

Reply to
@sjvn @mattdm @jbowen This is the great lie of the GTD method. "If it takes less than 5 minutes to do it, do it right away" means all emails that take more than 5 minutes to handle just pile up throughout the day to the point where I have no mental coherence left to deal with them.

So, you either get stuff from me within minutes, or you may not hear from me ever again until you re-prod me.

:)

or :(

or :'/
2
1
2
monsieuricon

K. Ryabitsev 🍁

Reply to
@jbowen @mattdm I mean, some of these are so old, replying to them would be just embarrassing, so I do think that some of these 192 will get the "delete of shame" treatment.
1
0
2
monsieuricon

K. Ryabitsev 🍁

Reply to
@mattdm People tend to get grumpy when I do that. Don't know why.
1
0
2
monsieuricon

K. Ryabitsev 🍁

Inbox = 192 and falling
1
0
3
monsieuricon

K. Ryabitsev 🍁

Reply to
@mikeymikey Fossil fuel is just well-aged solar.
0
0
1
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: