From: Dmitry Vyukov <email@example.com> To: Konstantin Ryabitsev <firstname.lastname@example.org> Cc: Dmitry Vyukov <email@example.com>, "Theodore Ts'o" <firstname.lastname@example.org>, Rob Herring <email@example.com>, "Rafael J. Wysocki" <firstname.lastname@example.org>, email@example.com, Shuah Khan <firstname.lastname@example.org>, Greg Kroah-Hartman <email@example.com>, Bjorn Helgaas <firstname.lastname@example.org>, Jiri Kosina <email@example.com>, Jani Nikula <firstname.lastname@example.org>, Geert Uytterhoeven <email@example.com>, firstname.lastname@example.org, Sasha Levin <email@example.com>, Christoph Hellwig <firstname.lastname@example.org>, David Miller <email@example.com> Subject: Re: [MAINTAINERS SUMMIT] Reflections on kernel development processes Date: Fri, 11 Oct 2019 12:46:20 +0200 [thread overview] Message-ID: <CACT4Y+ZcPf4HiXhBknBY=aE0hJM33e1FG8pVepb2hYXMvbiMVw@mail.gmail.com> (raw) In-Reply-To: <CAMwyc-TzGj4BE0E2tRn8Esj43SnpcWXpS-ureG1YWbmtzmfqbA@mail.gmail.com> On Fri, Oct 11, 2019 at 4:16 AM Konstantin Ryabitsev <firstname.lastname@example.org> wrote: > > On Tue, 8 Oct 2019 at 12:51, Konstantin Ryabitsev > <email@example.com> wrote: > > >Hi Konstantin, > > > > > >Are you going to attend OSS Summit EU? If yes, I think we should sync > > >up there. I know Dave and Greg are there too. Perhaps we could > > >schedule some kind of semi-formal meeting? > > > > Unfortunately, no -- we have limited budget for traveling and I burned > > through mine by going to Lisbon. I'd be happy to work on a draft > > document that expands on my tooling vision (I'm doing so anyway), and I > > can time it to be ready before the summit so you can review and improve > > it. My hope is to submit it formally to the LF by the end of the month. > > Oh, hey, change of plans -- looks like I *will* be going to Lyon after > all. I think sitting down together for a semi-formal meeting sounds > like a good idea, considering all the active discussions happening > lately. Should we hash out a tentative agenda about topics that we > should and shouldn't cover? Who should be in attendance? Re agenda. For me the main bullet on the agenda would be figuring out high-level final destination for the effort. I think we need to take a step back, forget about implementation costs for a moment and try to imagine how we want kernel development process to look like in 5-10 years. Once we do that, most likely we will decide to cut some corners and compromise on practical grounds, and definitely have some incremental process of getting there. But still making small steps with a clear vision of the final destination is very different from making conflicting small steps in random directions. It should help us to avoid conflicting, duplicate and throwaway efforts. Personally I would be much more willing to contribute to such unified effort with clear destination rather than random projects used by a fraction of the community. It seems that lots of current efforts suffer from an inability to get enough resources behind because of an unofficial status. If we discard something based on the implementation costs, it would be useful to make that an explicit informed decision. Implementing something solid from scratch may actually be less effort than trying to connect together two pieces that were never meant to work together, it's important to consider short term vs long term costs here. But for this final destination we also need to figure out concrete technical foundations: email vs git vs ssb vs forge vs something else; identity/user account story, etc. But it's not just picking one name, because e.g. for ssb it's currently unclear to me how to deal with its inability to provide global data consistency. But git-based solution has comparable fundamental problems too. Without these decisions we won't be able to make any actual forward progress.
next prev parent reply other threads:[~2019-10-11 10:46 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20190912120602.GC29277@pure.paranoia.local> 2019-09-22 12:02 ` [Ksummit-discuss] " Dmitry Vyukov 2019-09-23 12:52 ` Daniel Borkmann 2019-09-23 14:08 ` Dmitry Vyukov 2019-09-23 14:57 ` Daniel Borkmann 2019-09-30 21:24 ` Konstantin Ryabitsev 2019-10-01 21:33 ` Daniel Borkmann 2019-10-02 15:04 ` Konstantin Ryabitsev 2019-09-30 20:24 ` Konstantin Ryabitsev 2019-10-08 6:46 ` Dmitry Vyukov 2019-10-08 16:51 ` Konstantin Ryabitsev 2019-10-11 2:16 ` Konstantin Ryabitsev 2019-10-11 2:30 ` Steven Rostedt 2019-10-11 8:30 ` Greg Kroah-Hartman 2019-10-11 8:59 ` Dmitry Vyukov 2019-10-11 9:33 ` Dmitry Vyukov 2019-10-11 9:40 ` Christian Brauner 2019-10-11 13:18 ` Steven Rostedt 2019-10-11 13:19 ` Christian Brauner 2019-10-11 13:30 ` Dmitry Vyukov 2019-10-11 13:40 ` Laurent Pinchart 2019-10-11 15:28 ` Jonathan Corbet 2019-10-14 7:42 ` Nicolas Belouin 2019-10-14 7:52 ` Daniel Vetter 2019-10-15 7:31 ` Dmitry Vyukov 2019-10-15 16:17 ` Konstantin Ryabitsev 2019-10-11 10:46 ` Dmitry Vyukov [this message] 2019-10-11 13:29 ` Laurent Pinchart 2019-10-11 13:51 ` Theodore Y. Ts'o
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACT4Y+ZcPf4HiXhBknBY=aE0hJM33e1FG8pVepb2hYXMvbiMVw@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [MAINTAINERS SUMMIT] Reflections on kernel development processes' \ /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
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 NNTP newsgroup(s).