From: Lars-Dominik Braun <lars@6xq.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Project direction with testing changes (branches and patches)
Date: Thu, 12 Aug 2021 10:04:02 +0200 [thread overview]
Message-ID: <YRTV8pVLmkBg3ai/@noor.fritz.box> (raw)
In-Reply-To: <87bl6hbd05.fsf@cbaines.net>
Hi Chris,
> So, I think I've recently switched to thinking about the problem as one
> of testing changes, rather than just testing patches. Since both patch
> series, and branches are used to propose changes, I think this makes
> sense.
I agree with this analysis and this was always something that bugged me
about Patchwork: That it knew about patch series (most of the time), but
seemed to operate on individual patches only.
> - Then there's the general UI component, ideally a first time
> contributor would be able to take advantage of automatic feedback
> about a patch they submit. There's multiple other groups of users
> though, like patch reviewers, and committers for example.
> […]
> The UI part is much less certain, I've done some work with Patchwork,
> and I do have some ideas in mind, but there's still more thinking and
> work to do in this area.
This is the main problem right now: UI. As a reviewer I need the
following information about a changeset:
1 Is anyone else reviewing it already and what were the comments? (Do I
need to take a look at it?)
2 Which packages/components are affected? (Do I have the knowledge to
review this changeset?)
3 Are there any obvious issues with it? (Does it pass linting? Does it
build? Can it be rebased onto master without conflicts?)
4 Where can I pull the changeset from to do further tests?
(Patch-over-email is super-fragile, from encoding/newline issues to
merging problems)
5 Who is the contributor? (Does he/she have commit access or do I have
to commit on his behalf?)
I also want to subscribe to certain changesets (new comments, new
versions, …) and filter them to find those, where I can actually help.
And debbugs certainly can’t provide any of this. I believe it would be
wise not to spend too much time to recreate what GitLab/gitea/GitHub/…
do already and just use them to our advantage, filling the holes with
bridges/bots to some CI infrastructure (it does not matter whether this
is Cuirass, Chris’ build coordinator, the Data Service, … – we just have
to be able to get the data in and out somehow).
Cheers,
Lars
prev parent reply other threads:[~2021-08-12 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 11:50 Project direction with testing changes (branches and patches) Christopher Baines
2021-08-04 21:15 ` Ludovic Courtès
2021-08-09 22:09 ` Christopher Baines
2021-08-10 6:04 ` Mathieu Othacehe
2021-08-10 19:26 ` Christopher Baines
2021-08-11 10:37 ` Ludovic Courtès
2021-08-11 22:27 ` Christopher Baines
2021-08-10 7:05 ` Ricardo Wurmus
2021-08-12 8:04 ` Lars-Dominik Braun [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRTV8pVLmkBg3ai/@noor.fritz.box \
--to=lars@6xq.net \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).