Conversation
monsieuricon

K. Ryabitsev

My grand plan is to put together a Free Tooling Workgroup at the Linux Foundation that would:

* secure funding for continued work on public-inbox and lei
* secure funding to pay patchwork maintainers to add better CI integration
* secure funding for continued b4 development (so I'm not doing it in-between sysadmin/IT staff management tasks but can make it my primary effort)
* investigate ways to integrate AI into bug report analysis so we can better categorize reported bugs
* slowly and iteratively replace the SMTP component from patch submission and code review, while keeping everything distributed *and* decentralized

I intend to put forth a formal proposal to the Technical Advisory Board in the next few months.
4
8
28
monsieuricon

K. Ryabitsev

Reply to @monsieuricon
Public-inbox repositories (the data layer behind lore.kernel.org) is not just an archival medium, but also an efficient git-based message distribution platform. You can clone all data behind lore.kernel.org *and* keep it continuously updated.

For example, https://lore.kernel.org/b4-sent/ contains submitted patches there never touched SMTP but were submitted via b4's web submission endpoint. A tool like "lei" is able to retrieve these messages and deliver them to reviewers without any of it touching the much-hated SMTP protocol. Yes, "lei" is a backend tool that is not very end-user-friendly -- the goal is to offer it as a service delivering query-based results into its own public-inbox feed that is available via POP, IMAP, or any other message retrieval protocol, plus fed into patchwork.

Evolutionary change is how we'll improve the situation, not by introducing centralized, single-point-of-failure, outright proprietary or "open-core" tools.
1
2
9
vbabka

Vlastimil Babka

Reply to @monsieuricon
@monsieuricon oh I'd so very much welcome lei as a service.
0
0
0
monsieuricon

K. Ryabitsev

Reply to
@cgwalters if by "resistance to change" you mean "not breaking workflows that are extremely efficient for many people", then all of it.
1
0
1
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: