From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: Adam Hassick <ahassick@iol.unh.edu>,
David Marchand <david.marchand@redhat.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: Adding Series Dependency to Patchwork
Date: Thu, 4 Apr 2024 09:50:01 -0400 [thread overview]
Message-ID: <CAJvnSUAi0SbZ_LRyX3R+i=RL4QBK0jQYJtrW2yHEQ+pLJ0ggxQ@mail.gmail.com> (raw)
In-Reply-To: <CAC-YWqhFpn5zrZsJ_R6sUehH1FzSWpuRFpgQ-CRaG5p8NrHAbQ@mail.gmail.com>
Hi Thomas,
Adam explains more completely in the preceding email, but he has
talked with the patchwork project maintainer, and determined the
needed next steps to do work adding depends-on support to patchwork
server. And he provides an estimate (35-50 hours of his time) for
adding this feature to pw.
What we want is a community opinion on using Community Lab resources
(our developer time) towards this effort on patchwork project. I'm
going to you, because you were the person who originally raised the
depends on issue and adding this support to pw server.
Given his time estimate, do you endorse this work, or do you prefer we
focus on our SOW items and other community requests which are in queue
right now? Thanks.
On Thu, Feb 22, 2024 at 2:51 PM Adam Hassick <ahassick@iol.unh.edu> wrote:
>
> Hi All,
>
> There has been a discussion on GitHub between myself and others about
> adding support for series dependency to Patchwork. This would involve
> adding the feature to the Patchwork dashboard and git-pw. However, it
> seems like the maintainer would like us to do much of the required
> implementation work. I estimate, with a low level of certainty, that
> it would consume 35 to 50 hours of developer time.
>
> The active issue relating to this feature can be found here, as well
> as the archived one:
> https://github.com/getpatchwork/patchwork/issues/583
>
> Would it be worth it for us here at the Community Lab to contribute
> upstream to Patchwork? Implementing the feature in the Patchwork
> project will make our method for defining series dependencies the
> standard, and it may lift some of the burden of maintaining this
> feature off of us.
>
> Regards,
> Adam Hassick
next prev parent reply other threads:[~2024-04-04 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 19:51 Adam Hassick
2024-04-04 13:50 ` Patrick Robb [this message]
2024-04-05 6:41 ` Thomas Monjalon
2024-04-11 14:18 ` Aaron Conole
2024-04-11 14:33 ` Patrick Robb
2024-07-12 20:15 ` Adam Hassick
2024-07-19 15:32 ` Patrick Robb
2024-07-19 17:43 ` Ferruh Yigit
2024-07-19 17:40 ` Ferruh Yigit
2024-07-22 16:16 ` Adam Hassick
2024-07-22 16:28 ` Patrick Robb
2024-07-23 12:41 ` Aaron Conole
[not found] ` <6b425d90-78b2-497b-958c-9d36e2ba6e3b@amd.com>
2024-07-23 15:36 ` Patrick Robb
2024-07-23 16:08 ` Ferruh Yigit
2024-07-24 15:07 ` Adam Hassick
2024-07-25 9:47 ` Ferruh Yigit
2024-07-25 17:52 ` Patrick Robb
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='CAJvnSUAi0SbZ_LRyX3R+i=RL4QBK0jQYJtrW2yHEQ+pLJ0ggxQ@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=thomas@monjalon.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.
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).