From: Leon Romanovsky <leon@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: James.Bottomley@hansenpartnership.com,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance
Date: Tue, 11 Sep 2018 13:06:39 +0300 [thread overview]
Message-ID: <20180911100639.GA3142@mtr-leonro.mtl.com> (raw)
In-Reply-To: <3446025.tlHTe8tT15@avalon>
[-- Attachment #1: Type: text/plain, Size: 4826 bytes --]
On Tue, Sep 11, 2018 at 12:38:13AM +0300, Laurent Pinchart wrote:
> Hi Sean,
>
> On Tuesday, 11 September 2018 00:09:02 EEST Sean Paul wrote:
> > On Mon, Sep 10, 2018 at 4:15 PM Laurent Pinchart wrote:
> > > On Monday, 10 September 2018 18:13:05 EEST Jiri Kosina wrote:
> > >> On Mon, 10 Sep 2018, James Bottomley wrote:
> > >>> 1. How do reviews happen? Non email projects tend to have only one
> > >>> review mechanism (gerrit, github, gitlab, etc.) and stick to it.
> > >>> Do we want to pick a technology or allow multiple? I don't
> > >>> think this is kernel wide, it could be a sybsystem choice.
> > >>
> > >> Yeah, but OTOH even now I've heard a lot of feedback about the irregular
> > >> contributors / newcomers being confused by different subsystems having
> > >> different processess and requirements; and those are basically just
> > >> rather "minor" things currently (bugzilla usage, patchwork usage,
> > >> subscriber-only mailinglists, etc), but it's still enough to confuse the
> > >> hell out of people.
> > >
> > > That's also one of my concerns. The differences between subsystems that
> > > all use an email-based review process can already be confusing, or just
> > > annoying to handle, especially when specific tools are mandated (the DRM
> > > dim tool or the ARM patch system come to mind). I dread to think about
> > > how painful it would be if one subsystem adopted gitlab, another one
> > > gerrit, ...
> >
> > The other way to look at this is as a feature, not a bug. As mentioned
> > upthread, each subsystem is essentially its own oss project at this
> > point, so why keep pretending they're all the same thing?
>
> Subsystems are given lots of freedom in how they implement their development
> process, and many use that freedom, but in the end they are all integrated in
> the same kernel. This works because we have a common communication tool.
>
> > At least in the gitlab/gerrit/github nightmare, the differing contributing
> > rules would be obvious as opposed to implicit as they are today.
>
> And we would lose the common communication tool.
And not only communication tool, but educational tool. Reviews are
performed by email visible to everyone and are supposed to be
lesson-learned for other contributors. In opposite, gerrit-like tools
favor one-to-one discussions.
>
> (And if we went for gerrit, we'd likely lose the majority of developers, but
> that's a separate topic - after having to use gerrit when working on project
> Ara, I now reject any customer project that would force me to use gerrit
> again)
As the one who suffers from internal gerrit and forced to use it,
I fully agree with you and will add that we will lose most reviewers too,
because it simply too much painful to follow and to do random review there.
>
> > > That would also make changes that cross subsystem boundaries a nightmare
> > > to handle. Let's not forget that many developers are not confined within a
> > > single subsystem.
> >
> > Well, yeah, this kind of blows a hole in what I said above. I'm
> > imagining Kees crying out in pain thinking about tree-wide changes in
> > this new world :-).
>
> I had the exact same image :-)
I already suffer from it while submitting patches both to netdev and
RDMA. The difference in coding style alone makes me nervous every time
I get comment for such cross-subsystem patches. I'm pretty sure that it
will be unbelievable hard to work in "multi-tool world".
>
> > That said, there's probably a pretty good middle ground between what
> > we have now and the gitlab utopia.
>
> I believe we all agree there's lots of room for improvement, that's already
> quite positive.
>
> > > On the other hand, I don't really see how switching the whole kernel to
> > > gitlab (or another system) could happen without frustrating a very large
> > > number of developers. We all know how conservative the community tend to
> > > be.
> > >
> > > One possible course of action would be to make the new tools optional and
> > > keep email as a common denominator. That way the old dinosaurs who won't
> > > adopt any tool introducing even the slightest disturbance in their work
> > > flow (it's not pleasant to realize that I may well be one of them) will
> > > still be able to work undisturbed, and all the other developers would be
> > > able to enjoy the myriad of amazing features offered by their tooling of
> > > choice. This would however put an extra burden on the new tools that
> > > would need to have first-class email compatibility. I don't know whether
> > > that would be feasible.
>
> --
> Regards,
>
> Laurent Pinchart
>
>
>
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-09-11 10:06 UTC|newest]
Thread overview: 162+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 8:59 [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance Daniel Vetter
2018-09-10 14:53 ` Linus Torvalds
2018-09-10 15:08 ` James Bottomley
2018-09-10 15:10 ` Linus Torvalds
2018-09-10 15:38 ` Sasha Levin
2018-09-10 15:47 ` James Bottomley
2018-09-10 15:55 ` Sasha Levin
2018-09-10 16:13 ` James Bottomley
2018-09-10 16:24 ` Sasha Levin
2018-09-10 17:10 ` James Bottomley
2018-09-10 15:47 ` Konstantin Ryabitsev
2018-09-10 15:56 ` Sasha Levin
2018-09-10 16:02 ` Konstantin Ryabitsev
2018-09-10 16:07 ` Daniel Vetter
2018-09-10 16:18 ` Konstantin Ryabitsev
2018-09-10 16:23 ` Daniel Vetter
2018-09-10 16:41 ` Konstantin Ryabitsev
2018-09-10 17:06 ` Daniel Vetter
2018-09-10 19:48 ` Laurent Pinchart
2018-09-10 20:50 ` Daniel Vetter
2018-09-10 15:49 ` Mark Brown
2018-09-10 16:33 ` Olof Johansson
2018-09-10 19:59 ` Laurent Pinchart
2018-09-10 21:30 ` Josh Triplett
2018-09-10 23:00 ` Laurent Pinchart
2018-09-10 23:16 ` Daniel Vetter
2018-09-11 1:14 ` Josh Triplett
2018-09-10 15:13 ` Jiri Kosina
2018-09-10 15:20 ` James Bottomley
2018-09-10 15:31 ` Sasha Levin
2018-09-10 20:15 ` Laurent Pinchart
2018-09-10 21:09 ` Sean Paul
2018-09-10 21:38 ` Laurent Pinchart
2018-09-11 10:06 ` Leon Romanovsky [this message]
2018-09-11 8:44 ` Jani Nikula
2018-09-11 9:08 ` Geert Uytterhoeven
2018-09-11 10:01 ` Daniel Vetter
2018-09-11 10:09 ` Geert Uytterhoeven
2018-09-11 10:17 ` Daniel Vetter
2018-09-11 10:30 ` Geert Uytterhoeven
2018-09-11 8:41 ` Jani Nikula
2018-09-10 15:31 ` Daniel Vetter
2018-09-10 16:39 ` Olof Johansson
2018-09-10 17:10 ` Daniel Vetter
2018-09-12 19:02 ` Darren Hart
2018-09-12 18:59 ` Darren Hart
2018-09-12 20:05 ` Daniel Vetter
2018-09-12 20:58 ` Darren Hart
2018-09-13 11:27 ` Mark Brown
2018-09-13 11:41 ` Daniel Vetter
2018-09-13 17:08 ` Darren Hart
2018-09-13 2:56 ` Theodore Y. Ts'o
2018-09-13 5:17 ` Daniel Vetter
2018-09-10 15:56 ` Daniel Vetter
2018-09-10 20:32 ` Laurent Pinchart
2018-09-10 20:55 ` Daniel Vetter
2018-09-10 21:33 ` Laurent Pinchart
2018-09-10 22:44 ` Daniel Vetter
2018-09-11 12:44 ` Alexandre Belloni
2018-09-11 14:35 ` Mark Brown
2018-09-11 15:17 ` Alexandre Belloni
2018-09-11 15:02 ` Daniel Vetter
2018-09-11 22:00 ` Alexandre Belloni
2018-09-11 22:17 ` Guenter Roeck
2018-09-12 8:42 ` Jani Nikula
2018-09-12 18:45 ` Alexandre Belloni
2018-09-12 19:52 ` Dave Airlie
2018-09-12 22:25 ` Daniel Vetter
2018-09-12 9:14 ` Linus Walleij
2018-09-12 18:23 ` Alexandre Belloni
2018-09-12 18:44 ` Thomas Gleixner
2018-09-13 12:08 ` Maxime Ripard
2018-09-13 12:57 ` Alexandre Belloni
2018-09-13 13:18 ` Maxime Ripard
2018-09-13 14:25 ` Jani Nikula
2018-09-13 20:05 ` Thomas Gleixner
2018-09-13 23:02 ` Rodrigo Vivi
2018-09-14 6:47 ` Rafael J. Wysocki
2018-09-14 6:39 ` Dave Airlie
2018-09-14 14:15 ` Thomas Gleixner
2018-09-17 7:40 ` Daniel Vetter
2018-09-14 7:08 ` Linus Walleij
2018-09-14 7:39 ` Geert Uytterhoeven
2018-09-14 8:08 ` Linus Walleij
2018-09-12 21:21 ` Linus Walleij
2018-09-21 16:05 ` Joe Perches
2018-09-12 22:44 ` Laurent Pinchart
2018-09-10 22:56 ` Laurent Pinchart
2018-09-10 21:11 ` Theodore Y. Ts'o
2018-09-10 23:05 ` Laurent Pinchart
2018-09-17 11:43 ` Mauro Carvalho Chehab
2018-09-17 12:03 ` Geert Uytterhoeven
2018-09-17 13:04 ` Mauro Carvalho Chehab
2018-09-17 13:10 ` Julia Lawall
2018-09-17 13:29 ` Christoph Hellwig
2018-09-17 13:48 ` Laurent Pinchart
2018-09-17 13:58 ` Mauro Carvalho Chehab
2018-09-17 14:18 ` Christoph Hellwig
2018-09-17 14:50 ` Geert Uytterhoeven
2018-09-17 15:21 ` Mauro Carvalho Chehab
2018-09-17 14:18 ` Laurent Pinchart
2018-09-17 16:50 ` Joe Perches
2018-09-17 14:14 ` Laurent Pinchart
2018-09-17 14:59 ` Mauro Carvalho Chehab
2018-09-17 22:39 ` Dave Airlie
2018-09-17 23:04 ` James Bottomley
2018-09-18 8:00 ` Daniel Vetter
2018-09-18 11:16 ` James Bottomley
2018-09-18 15:26 ` Randy Dunlap
2018-09-18 16:47 ` Tim.Bird
2018-09-18 16:59 ` Konstantin Ryabitsev
2018-09-18 17:08 ` Tim.Bird
2018-09-18 17:12 ` Tim.Bird
2018-09-18 17:31 ` Konstantin Ryabitsev
2018-09-18 17:42 ` Tim.Bird
2018-09-18 17:55 ` Konstantin Ryabitsev
2018-09-18 18:58 ` Tim.Bird
2018-09-18 19:24 ` Konstantin Ryabitsev
2018-09-18 17:47 ` Geert Uytterhoeven
2018-09-18 17:49 ` Greg KH
2018-09-18 18:03 ` Konstantin Ryabitsev
2018-09-18 22:46 ` Alexandre Belloni
2018-09-18 18:22 ` Dmitry Torokhov
2018-09-18 19:16 ` Theodore Y. Ts'o
2018-09-18 18:56 ` Sasha Levin
2018-09-18 23:05 ` Laurent Pinchart
2018-09-18 7:37 ` Nicolas Ferre
2018-09-18 7:47 ` Geert Uytterhoeven
2018-09-18 10:38 ` Laurent Pinchart
2018-09-18 16:02 ` Mark Brown
2018-09-18 16:32 ` Luck, Tony
2018-09-18 16:35 ` Dmitry Torokhov
2018-09-18 17:18 ` Linus Torvalds
2018-09-18 17:28 ` Sean Paul
2018-09-18 17:37 ` Tim.Bird
2018-09-21 16:46 ` Olof Johansson
2018-09-21 17:08 ` Mauro Carvalho Chehab
2018-09-21 17:16 ` Olof Johansson
2018-09-18 17:21 ` Mark Brown
2018-09-18 21:01 ` Steven Rostedt
2018-09-18 23:16 ` Laurent Pinchart
2018-09-18 23:54 ` Mark Brown
2018-09-19 5:27 ` Christoph Hellwig
2018-09-19 9:46 ` James Bottomley
2018-09-18 17:10 ` Tim.Bird
2018-09-18 20:48 ` Takashi Iwai
2018-09-18 16:50 ` David Woodhouse
2018-09-18 17:24 ` Mark Brown
2018-09-18 19:22 ` David Woodhouse
2018-09-18 19:30 ` Sasha Levin
2018-09-18 19:38 ` Josh Triplett
2018-09-18 19:48 ` David Woodhouse
2018-09-18 8:24 ` Eric W. Biederman
2018-09-17 13:12 ` Christoph Hellwig
2018-09-17 14:14 ` Mauro Carvalho Chehab
2018-09-17 21:59 ` Rafael J. Wysocki
2018-09-17 22:17 ` Rafael J. Wysocki
2018-09-10 21:19 ` Konstantin Ryabitsev
2018-09-11 8:33 ` Rafael J. Wysocki
2018-09-10 16:29 ` [Ksummit-discuss] Fwd: " Daniel Vetter
2018-09-11 15:35 ` [Ksummit-discuss] " Jiri Kosina
2018-09-17 11:11 ` [Ksummit-discuss] [MAINTAINER SUMMIT] Live without email - possible? - Was: " Mauro Carvalho Chehab
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=20180911100639.GA3142@mtr-leonro.mtl.com \
--to=leon@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).