workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
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: Mon, 23 Sep 2019 12:20:01 -0400	[thread overview]
Message-ID: <20190923162001.GD6005@mit.edu> (raw)
In-Reply-To: <1811089.yxvLMk49Ug@kreacher>

One of the things I'd like to add as a strong desire is the ability to
review patches via web if that's what users would like to do.  There
are some real benefits for web-based review.  It means that if you
need to see greater context, it's relatively easy to do this.  It also
is convenient to be able to see the conversation for a particular hunk
of code right alongside the code.

It's clear that whatever we do, it needs to be compatible with e-mail.
That's very clear.  But it would be useful if we can support both the
e-mail and web-based review.  There have some prototypes that have
been floated which shows that it is at least possible; perhaps
imperfectly, but something which provides a bidrectional gateway
between those who perfer to use e-mail and those that prefer to use a
web-based UI would be able to do it.

There will be many potential kernel contributors who will be used to
web-based UI's such as those that are available on github.  So while
remaining e-mail compatible, having some way of allow as many
operations to be done via web interfaces might help us get some newer
developers who are more comfortable to living on the web than some of
us more senior developers who remember when "gopher" was a text-based
search engine, and not a mascot for the Go programming langauge.  :-)

       	       	       	 	- Ted

  parent reply	other threads:[~2019-09-23 16:20 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
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 [this message]
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=20190923162001.GD6005@mit.edu \
    --to=tytso@mit.edu \
    --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).