Desired new features to patchworks...

[Deen Sethanandha]

Hello,

   I did develop PatchMetrix during the summer 2010 to collect metrics from
Patchwork.  Please check it out if you can find it useful.
http://deen.sethanandha.com/patchmetrix/.  I put the code here
https://github.com/deenseth/patchwork/tree/patch-stats.  If this is
something that is useful to the community I can continue working on it and
provide patch to the mainline.

  I haven't update the code since August 2010.  I will likely to get back to
it soon.  My plan is to collect data from Patchwork and feed into a process
mining tool (http://processmining.org) to get more stats.

  @Jeff, I particularly interested in the Feature 2.  I would love to know
more about techniques that can be used to detect bottlenecks in the process.

-- Deen

On Mon, Feb 7, 2011 at 9:29 PM, Jeff Kirsher <jeffrey.t.kirsher at intel.com>wrote:

> On Mon, 2011-02-07 at 21:12 -0800, Kumar Gala wrote:
> > On Feb 7, 2011, at 6:11 PM, Jeff Kirsher wrote:
> >
> > > On Mon, Nov 22, 2010 at 01:34, Jeff Kirsher <
> jeffrey.t.kirsher at intel.com> wrote:
> > >> Patchworks has been a great tool when keeping track of patches, but it
> > >> lacks two very useful bits of information.
> > >>
> > >> Feature 1- Metrics: It would be great to have the number of patches in
> a
> > >> particular "state" on any given page.  For instance, if I were to go
> to
> > >> the patches link of a particular project, it would be nice to have in
> > >> the header of the page the number of "new", "Under Review", etc.
> > >> patches.  Also if I were to do a search of all patches submitted by an
> > >> individual, the number of patches in there various states is displayed
> > >> in the header (as well as the results of the search).
> > >>
> > >> Feature 2- Duration: Another feature that would be nice to see is the
> > >> amount of time a patch stays in a particular state and/or the average
> > >> duration that patches stay in a particular state.  This feature would
> > >> help diagnosing bottlenecks in the patch review/test/commit process.
> > >>
> > >> Cheers,
> > >> Jeff
> > >>
> > >
> > > I apologize for sending this out again, the reason being was that I
> > > got a response from an individual off-list that gave me a URL
> > > regarding a tool they had designed and built to generate metrics from
> > > patchwork.  I have misplaced the email the individual sent me and I am
> > > hoping to get that information again.
> > >
> >
> > Would be nice to generally know about this tool.  I think others would be
> interested.
> >
> > - k
> >
>
> I will share it, if I ever get a response...
>
> _______________________________________________
> Patchwork mailing list
> Patchwork at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20110817/075d1fef/attachment.html>