RFE: use patchwork to submit a patch
laurent.pinchart at ideasonboard.com
Wed Oct 16 03:32:41 AEDT 2019
On Tue, Oct 15, 2019 at 11:40:10AM -0400, Konstantin Ryabitsev wrote:
> On Mon, Oct 14, 2019 at 06:33:33PM +0300, Laurent Pinchart wrote:
> > If the goal is to work around SMTP-related technical issues, is a web UI
> > really the best way to go ? Wouldn't it be better to do the same through
> > a git push ? We could setup a git server that requires authentication,
> > and implement a push-to-email bridge. The information that would need to
> > be entered in a web UI could be put in a tag message, and we could have
> > a CLI to create the tag from a list of questions.
> Well, this is largely what GitGitGadget does
> (https://gitgitgadget.github.io), and we could go that route, sure. I'm
> reluctant only because, quoth:
> GitGitGadget itself is a GitHub App that is backed by an Azure
> Pipeline written in Typescript (which is really easy to understand and
> maintained at https://github.com/gitgitgadget/gitgitgadget.
> I have zero familiarity with any of the above. That said, we do have a
> bunch of CI engineers working at the LF, and I can probably avail myself
> of their expertise if we decide to set this up.
I certainly wouldn't recommend a solution based on a proprietary
closed-source stack :-) But as we're talking about performing new
development for patchwork, I wanted to point out that we could also
consider a different technical approach that would involve new
development for a different open-source project. For instance, is the
above idea something that could be developed on top of gitolite ? Or
possibly even as a tiny standalone git server ?
More information about the Patchwork