Hi, all:
I would like to propose a new (large) feature to patchwork with the goal
to make the process of submitting a patch easier for newbies and people
generally less familiar with patch-based development. This was discussed
previously on the workflows list:
https://lore.kernel.org/workflows/20190930202451.GA14403@pure.paranoia.local/
How I envision this would work:
- user creates an account (which requires a mail confirmation)
- they choose a "submit patch" option from the menu
- the patch submission screen has a succession of screens:
1. a screen with a single field allowing a user to paste a URL to
their fork of the git repository. Once submitted, patchwork does a
"git ls-remote" to attempt to get a list of refs and to verify that
this is indeed a valid git repository
2. next screen asks the user to select the ref to work from using the
list obtained from the remote. Once submitted, patchwork performs a
`git clone --reference` to clone the repository locally using a
local fork of the same repo to minimize object transfer. This part
requires that:
a. patchwork project is configured with a path to a local fork,
if this feature is enabled for a project
b. that fork is kept current via some mechanism outside of
patchwork (e.g. with grokmirror)
c. there is some sanity-checking during the clone process to
avoid abuse (e.g. a sane timeout, a tmpdir with limited size,
etc -- other suggestions welcome)
3. next screen asks the user to pick a starting commit from the log.
Once submitted, patchwork generates the patch from the commit
provided to the tip of the branch selected by the user earlier,
using git format-patch.
4. next screen asks the user to review the patch to make sure this is
what they want to submit. Once confirmed, patchwork performs two
admin-defined optional hooks:
a. a hook to generate a list of cc's (e.g. get_maintainer.pl)
b. a sanity check hook (e.g. checkpatch.pl)
5. if sanity checking is defined, next screen shows the output of the
sanity check hook, asking confirmation to proceed.
6. next screen shows the user three fields:
a. title of the patch/series
b. cover letter for the patch/series
c. message-id of the previous patch revision (can be picked from
the list of previously submitted series by this user --
patchwork should have them already)
d. number of the revision (can be auto-filled if previous field
is provided) and other tags to include in []
7. next screen shows final review of what would be sent out to the
list (and cc's, if the hook to get cc's is defined and returned any
results). Once submitted, patchwork sends the patch/series using
patchwork's envelope-from and the user's own email in the From:
header.
8. once sent successfully, cleanups are performed (also needs to be
done as part of the regular cron job, for any aborted attempts)
I know this is a pretty big RFE, and I would like to hear your thoughts
about this. If there is general agreement that this is doable/good idea,
I may be able to come up with funding for this development as part of
the overall tooling improvement proposal.
Best regards,
-K
_______________________________________________
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
