ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: ketuzsezr@gmail.com
Cc: ksummit@lists.linux.dev, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Tech Topic] Integrating GitLab into the Red Hat kernel workflow
Date: Mon, 12 Jul 2021 09:30:14 -0400	[thread overview]
Message-ID: <20210712133014.cltekdzbd5fqemkw@redhat.com> (raw)
In-Reply-To: <22d1051d4aa1e3db742349ab213485fe3429feec.camel@gmail.com>

On Fri, Jul 09, 2021 at 10:59:55AM -0400, ketuzsezr@gmail.com wrote:
> On Wed, 2021-07-07 at 17:19 -0400, Don Zickus wrote:
> > Submission #89:
> > 
> > The Red Hat kernel team recently converted their RHEL workflow from
> > PatchWork to GitLab. This talk will discuss what the new workflow
> > looks like
> > with integrated CI and reduced emails. New tooling had to be created
> > to
> > assist the developer and reviewer. Webhooks were utilized to autoamte
> > as
> > much of the process as possible making it easy for a maintainer to
> > track
> > progress of each submitted change. Finally using CKI, every submitted
> > change
> > has to pass CI checks before it can be merged.
> > 
> > We faced many challenges especially around reviewing changes.
> > Resolving
> > those led to a reduction of email usage and an increase in cli tools.
> > Demos
> > of those tools will be included.
> > 
> > Attendees will leave with an understanding how to convert or
> > supplement
> > their workflow with GitLab.
> > 
> 
> Hey Don!
> 
> This sounds quite interesting to not just folks who are invited to the
> kernel summit but also those who work on distro kernels day-to-day.
> 
> Would it perhaps be worth doing this on also on a venue that is more
> open to distro kernel engineers (who aren't neccesarily invited to the
> kernel summit)?

Happy to give the talk at other venues.  I already presented at devconf.cz and
CentOS's Dojo as more RH focused events.  Happy to present this at a general
Plumbers talk for my eyes and ears.  Suggestions?

Cheers,
Don


      reply	other threads:[~2021-07-12 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 21:19 [Tech Topic] Integrating GitLab into the Red Hat kernel workflow Don Zickus
2021-07-07 21:42 ` Laurent Pinchart
2021-07-07 22:27   ` Don Zickus
2021-07-07 22:40     ` Laurent Pinchart
2021-07-08 21:04       ` Don Zickus
2021-07-10 22:38         ` Laurent Pinchart
2021-07-12 13:58           ` Don Zickus
2021-07-12 19:07             ` Konstantin Ryabitsev
2021-07-14 16:35               ` Don Zickus
2021-07-14 23:47             ` Laurent Pinchart
2021-07-09 14:59 ` ketuzsezr
2021-07-12 13:30   ` Don Zickus [this message]

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=20210712133014.cltekdzbd5fqemkw@redhat.com \
    --to=dzickus@redhat.com \
    --cc=ketuzsezr@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ksummit@lists.linux.dev \
    /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 NNTP newsgroup(s).