Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

[Michael Ellerman <mpe@ellerman.id.au>]

On Mon, 2015-07-13 at 12:05 +0100, Damien Lespiau wrote:
> On Thu, Jul 09, 2015 at 01:56:53PM +1000, Michael Ellerman wrote:
> > On Wed, 2015-07-08 at 21:19 +0200, Daniel Vetter wrote:
> > > On Wed, Jul 8, 2015 at 4:20 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> > > > I wish I knew how to use patchwork better, or had a smarter workflow
> > > > that could comprehend a series as a single entity.  Patchwork is a lot
> > > > of clicking, but I don't know anything better.
> > > 
> > > We're working on improving patchwork here to understand series and
> > > help out with auto-deprecating patches when new versions show up.
> > > Currently being tested internally and we plan to push to upstream ofc
> > > and deploy on freedesktop.org (since that's where all the drm/gfx
> > > folks hang out), but because of all the things going on it's really
> > > slow. Damien knows more, maybe we could push the current state to some
> > > git branch somewhere.
> > 
> > I'd be interested in that if you can publish it somewhere.
> > 
> > At the moment I have a very hacky script that tries to recognise a series on
> > the client, which usually works, but not always.
> 
> I have quite a few patches on top of upstream now. It's really a back
> burner distraction, so well, I have no ETA to give for when I'd be happy
> with the state of this work.

Yeah fair enough, I'm in the same boat, it's a tool I use for my job but it's
not my job to work on the tool :)

> I have a work-in-progress branch here:
> 
>   https://github.com/dlespiau/patchwork
> 
> What's on there is roughly a re-design of the interface, a new REST API
> and parsing/presenting series to the user, not just patches.
> 
> I have some more work (unpublished because not quite ready) on top of
> this to parse and present new versions/revisions of series when:
>   - people post a v2/3/4/... of a patch as a reply to one of the series
>   - people post a full new series as a v2/3/4/..
> 
> The goal being one series object (with a unique ID for that patchwork
> instance) represents the whole life cycle of that work, including
> multiple versions.

Sounds great.

Maybe we can slowly get some of it merged, I'll try and have a look at it in my
copious spare time.

cheers