From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Kernel development collaboration platform wish list
Date: Fri, 13 Sep 2019 14:37:53 +0300 [thread overview]
Message-ID: <20190913113753.GG29992@pendragon.ideasonboard.com> (raw)
In-Reply-To: <1811089.yxvLMk49Ug@kreacher>
Hi Rafael,
On Fri, Sep 13, 2019 at 10:22:20AM +0200, Rafael J. Wysocki wrote:
> Hi All,
>
> During the Maintainers Summit session yesterday I started to create a wish list
> for the new kernel development collaboration platform to be created (and to
> replace the multiple pieces of tooling in use today). I also asked Bjorn,
> Jiri, Greg and Shuah for input and here's the reslut:
>
> 1. Compatible with e-mail
>
> (a) E-mail send to it stored and included automatically; appears as part of
> the normal flow.
>
> (b) Automatic e-mail responses
> If e-mail is sent to it, the sender will get all responses to it in the
> given thread by e-mail.
>
> 2. History tracking
>
> (a) Should be able to track revisions of a given patch series (or patch) down
> to the initial submission.
>
> 3. Integration with git
>
> (a) Should be able to create git commits from patches (or patch series)
> tracked by it if pointed to a git branch (either locally or remotely).
>
> (b) Link tags pointing back to it should be added automatically to git
> commits created from patches tracked by it.
In addition to a link, should the tag message contain a copy of the
cover letter for the patch series ?
> 4. Distributed
>
> (a) Support for running offline.
>
> (b) Support for batch updates.
>
> (c) CL-frendly.
>
> 5. Patchwork-like features
>
> (a) Delegation support.
>
> (b) Support for bundles and patch series manipulation.
>
> (c) Smart mbox (download all selected patches).
>
> 6. Easy to set up (especially for local installations)
>
> 7. Bug tracking support
>
> I guess there are more items to be added to this list, so please extend it if
> you have any ideas and we'll see where this goes. :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-09-13 11:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 8:22 Kernel development collaboration platform wish list Rafael J. Wysocki
2019-09-13 11:13 ` Jani Nikula
2019-09-17 21:58 ` Rafael J. Wysocki
2019-09-18 8:05 ` Jani Nikula
2019-09-18 13:43 ` Steven Rostedt
2019-09-13 11:37 ` Laurent Pinchart [this message]
2019-09-13 12:02 ` Geert Uytterhoeven
2019-09-13 12:15 ` Laurent Pinchart
2019-09-13 12:23 ` Geert Uytterhoeven
2019-09-17 22:00 ` Rafael J. Wysocki
2019-10-02 9:30 ` Rafael J. Wysocki
2019-09-17 18:40 ` Stefan Schmidt
2019-09-24 9:43 ` Paolo Bonzini
2019-09-24 12:20 ` Stefan Schmidt
2019-09-17 22:12 ` Rafael J. Wysocki
2019-10-01 3:52 ` Daniel Axtens
2019-10-01 4:50 ` Andrew Donnellan
2019-10-01 5:04 ` Daniel Axtens
2019-09-23 16:20 ` Theodore Y. Ts'o
2019-09-24 1:39 ` Eric Wong
2019-09-24 5:06 ` Greg Kroah-Hartman
2019-10-01 3:58 ` Daniel Axtens
2019-09-26 10:18 ` Geert Uytterhoeven
2019-09-26 11:40 ` Steven Rostedt
2019-09-26 13:39 ` Geert Uytterhoeven
2019-09-28 22:16 ` Steven Rostedt
2019-09-29 16:03 ` Dmitry Vyukov
2019-09-26 13:10 ` Jani Nikula
2019-09-26 13:41 ` Geert Uytterhoeven
2019-09-26 14:40 ` Jani Nikula
2019-10-02 9:55 ` Rafael J. Wysocki
2019-10-02 14:22 ` Daniel Axtens
2019-10-03 9:23 ` Rafael J. Wysocki
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=20190913113753.GG29992@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=rjw@rjwysocki.net \
--cc=skhan@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 NNTP newsgroup(s).