xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth.xen@gmail.com>
To: "Jesus M. Gonzalez-Barahona" <jgb@bitergia.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: Priya <vppriya9@gmail.com>,
	Daniel Izquierdo <dizquierdo@bitergia.com>,
	Lars Kurth <lars.kurth@xenproject.org>
Subject: Re: Code-Review-Dashboard: Regarding Outreachy project on Improving CR Dashboard
Date: Thu, 24 Mar 2016 17:33:55 +0000	[thread overview]
Message-ID: <809652C8-7400-4A89-A5FB-26F2AEB13DA9@gmail.com> (raw)
In-Reply-To: <1458647225.4380.391.camel@bitergia.com>

Removed urgent, added xen-devel back in

> On 22 Mar 2016, at 11:47, Jesus M. Gonzalez-Barahona <jgb@bitergia.com> wrote:
> On Tue, 2016-03-22 at 15:13 +0530, Priya wrote:
>> Hello all, 
>> Thank you for the introduction Lars. 
>> On Mon, Mar 21, 2016 at 3:13 PM, Lars Kurth <lars.kurth.xen@gmail.com
>>> wrote:
>>> There are no Perceval based scripts at this stage yet. But maybe we
>>> can find some improvements. 
>>> @Priya: What is your IRC handle. I think we ought to set up a quick
>>> chat, if possible. I am usually lars_kurth on #xendevel on
>>> freenode 
>> I went through some of the existing scripts used, and in my
>> understanding - the project is to shift completely from existing
>> MLStats like scripts to Perceval. I have started working on my
>> proposal focusing around this idea, and I will be sharing it with you
>> shortly. 
> Indeed, the idea is to switch from MetricsGrimoire (MLStats and
> CVSAnalY in this case) to Perceval backends. That means moving from SQL
> databases to ElasticSearch too.
>> btw, I am priya_ on freenode. 
> I guess we were talking some days ago on IRC, right? (I'm jgbarah
> there).
>>> @Dani, @Jesus: could you find a suitable task. We can also consider
>>> extending the deadline by a couple of days.
>> This would be really great, as we are approaching the deadline soon. 
> I guess a task to evaluate your proposal could be writting an script to
> use the Perceval email backend to feed data from the xen-devel mailing
> list to an ElasticSearch database, and annotating in it messages in the
> same thread.
> For identifying threads, you can use the Zawinski algorithm, https://ww
> w.jwz.org/doc/threading.html
> The result of the script would be an ElasticSearch search index, with
> one JSON document per message (it could be the same document produced
> by Perceval), with one extra field (property), with the same value for
> messages in in the same thread. The value could be the message-id of
> the first message in the thread.
> Priya, if you need, I could refine the definition of the problem.
> Lars, I removed xen-devel from the CC, just to avoid making noise. We
> can summarize later (but if you prefer all of this copied to xen-devel, 
> just let me know).

As part of the objective of Outreachy is for participants to work in 
the open and conduct open code reviews and discussions, please ensure 
that xen-devel is added in future. I think we should mark emails related 
to this project with "Code-Review-Dashboard:" in the subject line, which 
means people who don't care can ignore the mails.

Also, reviewers, maintainers and committers expect to be CC'ed and will 
either ignore or just scan mails that only go to xen-devel@


Xen-devel mailing list

      parent reply	other threads:[~2016-03-24 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-19  9:54 Regarding Outreachy project on Improving CR Dashboard Priya
2016-03-21  9:43 ` Regarding Outreachy project on Improving CR Dashboard (Urgent) Lars Kurth
2016-03-22  9:43   ` Priya
2016-03-22 12:05     ` Lars Kurth
     [not found]     ` <1458647225.4380.391.camel@bitergia.com>
2016-03-24 17:33       ` Lars Kurth [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=809652C8-7400-4A89-A5FB-26F2AEB13DA9@gmail.com \
    --to=lars.kurth.xen@gmail.com \
    --cc=dizquierdo@bitergia.com \
    --cc=jgb@bitergia.com \
    --cc=lars.kurth@xenproject.org \
    --cc=vppriya9@gmail.com \
    --cc=xen-devel@lists.xen.org \


* 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).