From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: workflows@vger.kernel.org
Subject: Tooling and workflows meeting at OSS EU Lyon
Date: Thu, 24 Oct 2019 16:58:03 -0400 [thread overview]
Message-ID: <20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local> (raw)
Hi, everyone:
So, if I read everything correctly, the meeting shall take place at OSS EU
Lyon, on Tuesday, from 14:00 to 15:00. The following people have
expressed interest in attending:
- Steven Rostedt
- Greg Kroah-Hartman
- Dmitry Vyukov
- Konstantin Ryabitsev
- Christian Brauner
- Laurent Pinchart
- Jon Corbet
- Daniel Vetter
- Nicolas Belouin
- Shuah Khan
(If your name is not on this list but you're planning to attend, please
follow up.)
I have confirmed that we can use the Developer Lounge, which will
contain either a whiteboard or a flip chart. Alternatively, if you think
we should get a dedicated meeting room, we can book one on-site. It's on
a first-come, first-served basis and it doesn't look like I can book it
before actually getting there. I will send exact details of the location
on Monday.
Since we only have an hour, I propose that we focus on a couple of
topics and perhaps keep them anchored to the immediate future,
discussing evolutionary changes as opposed to grand schemes that will
require changing half the known world.
I can discuss any of the following topics at length:
1. Current tools and automation offered at kernel.org, plus new features
they are likely to see in the future that are interesting to both
developers and maintainers:
- public-inbox
- patchwork
- bugzilla
- pr-tracker-bot and git-patchwork-bot
2. Proposed enhancements to the email-based workflow
- cryptographic attestation of patches
- adding (and requiring) base tree information in submitted patches/series
- git-to-ML bridges ("turn this pull request into a well-formatted
patch series and send it to the right places")
3. CI and bot integration
- identifying the data that maintainers/developers want to see
- communicating structured data over email
- providing consumable feeds of CI/bot jobs (as public-inbox
repositories?)
- avoiding bug duplication
- recognizing when a bug is fixed and following up on issues that
nobody has taken on
4. Maintainer tooling
- adaptability of existing tools for kernel development, such as:
- GitHub/GitLab
- SourceHut
- Gerrit
- building on top of public-inbox feeds to create a tool that can:
- track patches obtained from multiple sources (multiple mailing
lists, individual developer feeds, bot activity feeds, etc)
- collect the usual trailers (Reviewed-By's, etc)
- show interdiffs
- send automated templated replies
- apply series to a local git repository (streamlining "save these
patches as an mbox, make a new branch, run git-am")
Unfortunately, that's enough topics to fill a 3-day mini-summit. :)
Which ones are folks most interested in discussing during the meet-up,
and which ones should be targeted for hallway discussions?
Regards,
--
Konstantin Ryabitsev
Director, IT Core Projects
The Linux Foundation
Montréal, Québec
next reply other threads:[~2019-10-24 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:58 Konstantin Ryabitsev [this message]
[not found] ` <<20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local>
2019-10-25 6:58 ` Tooling and workflows meeting at OSS EU Lyon Nicolas Belouin
2019-10-25 11:16 ` Laurent Pinchart
2019-10-25 11:20 ` Dmitry Vyukov
2019-10-25 12:24 ` Veronika Kabatova
2019-10-25 13:36 ` Konstantin Ryabitsev
2019-10-25 14:15 ` Veronika Kabatova
2019-10-26 12:00 ` Kevin Hilman
2019-10-28 9:25 ` Konstantin Ryabitsev
2019-10-28 10:03 ` Konstantin Ryabitsev
2019-10-28 11:42 ` Frank Rowand
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=20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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).