From: Ian Campbell <ian.campbell@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Daniel Izquierdo <dizquierdo@bitergia.com>,
"Jesus M. Gonzalez-Barahona" <jgb@bitergia.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC] Results of Phase 1 of the Review Process study
Date: Fri, 16 Oct 2015 10:58:52 +0100 [thread overview]
Message-ID: <1444989532.12442.34.camel@citrix.com> (raw)
In-Reply-To: <E07411F5-26A5-43EC-A09A-AC18225DCC64@gmail.com>
On Fri, 2015-10-16 at 10:29 +0100, Lars Kurth wrote:
> > On 16 Oct 2015, at 10:19, Ian Campbell <ian.campbell@citrix.com> wrote:
> >
> > > * To consider that when there is no activity for a certain period,
> > > the
> > > review is no longer going to progress, and can be considered
> > > abandoned.
> > > The main trouble with this could be that we have seen some patch
> > > series
> > > inactive for very long periods, and still coming back to life after
> > > that. But being a very small fraction of the cases, for statistical
> > > purposes those could be considered as abandoned.
> >
> > Yes, and I suppose based on data mining you can see the longest delay
> > before "coming back to life", which would then feed into the selection
> > of
> > the certain period.
>
> Let's see what we can do. I am wondering whether there is some tool,
> where you put in two lists, you run an algorithm over it and out comes
> the most optimal matching pattern, matching the maximum set of entries.
>
> If I think about the possible users for what phase 2 will deliver, I see
> a number of different stake-holders / use-cases
> a) Community manager : requires some reports that are statistically sound
> b) Developers : something to make your life easier - requires better
> matching
> c) Recognition of reviewers and their effort
> d) There may be some more ...
FWIW as far as b) goes I think I don't expect anything to make things
easier as such more like "facilitates a) while not being an undue burden".
Where "a" may certainly lead to thing which make life easier for "b"
though.
Ian.
next prev parent reply other threads:[~2015-10-16 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 17:32 [RFC] Results of Phase 1 of the Review Process study Lars Kurth
2015-10-15 9:06 ` Ian Campbell
2015-10-15 9:26 ` Ian Campbell
2015-10-15 21:36 ` Lars Kurth
2015-10-15 22:25 ` Jesus M. Gonzalez-Barahona
2015-10-15 22:32 ` Jesus M. Gonzalez-Barahona
2015-10-16 9:19 ` Ian Campbell
2015-10-16 9:29 ` Lars Kurth
2015-10-16 9:58 ` Ian Campbell [this message]
2015-10-15 21:18 ` Lars Kurth
2015-10-16 9:06 ` Ian Campbell
2015-10-16 9:15 ` Ian Campbell
2015-10-15 11:58 ` Wei Liu
2015-10-15 21:20 ` Lars Kurth
2015-10-15 22:38 ` Jesus M. Gonzalez-Barahona
2015-10-16 11:06 ` Stefano Stabellini
2015-10-16 18:18 ` Lars Kurth
2015-10-21 12:49 ` Lars Kurth
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=1444989532.12442.34.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=dizquierdo@bitergia.com \
--cc=jgb@bitergia.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.