From: Priya <vppriya9@gmail.com>
To: lars.kurth@xenproject.org
Cc: xen-devel@lists.xenproject.org
Subject: Regarding Outreachy project on Improving CR Dashboard
Date: Sat, 19 Mar 2016 15:24:40 +0530 [thread overview]
Message-ID: <CAGwjOLP9je2g8AY5j7o=x8W0uv5rB-dho1dwT06xzbgLZpX=YA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]
Hello Lars Kurth,
I'm Priya V, a final year Computer Science student from Amrita University,
India. I came across this project on 'Improving Code Review Dashboard' in
Xen project ideas list, and thought about applying for the same in this
round of Outreachy.
>From a quick look, I understand that the CR data from repositories are
obtained using Metrics Grimoire tools and visualized on a Kibana dashboard.
I see the screenshots within the description, and I was wondering if there is
a way to take a look at any of these ( or can I reproduce it in my local ? )
>From the description of the project, I see that we need to produce Perceval
based scripts to analyze code review messages in Xen, instead of
MLStats/CVSAanlY-based scripts which is currently used. I was looking for
the Xen specific CVS scripts in http://xenbits.xen.org/ and couldnt find it
yet. It would be great if you can point me to the original scripts, so that
I can setup Perceval and try figuring out how to bring about the conversion.
I find my skill-sets matching with the project requirements, and
considering that the deadline is drawing near, please guide me with
pointers to start with.
Thanks,
Priya V
Amrita University
LinkedIn
<https://www.linkedin.com/in/priya-v-195560b6?trk=nav_responsive_tab_profile>
| GitHub <https://github.com/priya299> | Bitbucket
<https://bitbucket.org/priya299/>
[-- Attachment #1.2: Type: text/html, Size: 3154 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-19 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 9:54 Priya [this message]
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 ` Code-Review-Dashboard: Regarding Outreachy project on Improving CR Dashboard Lars Kurth
2016-04-05 16:35 Priya
2016-04-05 23:23 ` Jesus M. Gonzalez-Barahona
2016-04-06 12:00 ` Priya
2016-04-06 21:59 ` Jesus M. Gonzalez-Barahona
2016-04-07 12:27 ` Priya
2016-04-07 17:57 ` Jesus M. Gonzalez-Barahona
2016-04-08 14:03 ` Priya
2016-04-11 7:53 ` Jesus M. Gonzalez-Barahona
2016-04-13 16:33 ` Priya
2016-04-14 17:11 ` Priya
2016-04-14 22:41 ` Jesus M. Gonzalez-Barahona
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='CAGwjOLP9je2g8AY5j7o=x8W0uv5rB-dho1dwT06xzbgLZpX=YA@mail.gmail.com' \
--to=vppriya9@gmail.com \
--cc=lars.kurth@xenproject.org \
--cc=xen-devel@lists.xenproject.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 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).