All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jesus M. Gonzalez-Barahona" <jgb@bitergia.com>
To: Heather Booker <heather.j.booker@gmail.com>,
	xen-devel@lists.xen.org, lars.kurth@xenproject.org
Subject: Re: Outreachy project - Xen Code Review Dashboard
Date: Thu, 06 Apr 2017 16:05:13 +0200	[thread overview]
Message-ID: <1491487513.12313.303.camel@bitergia.com> (raw)
In-Reply-To: <CAGeXjYS4pjKxGuO=_07H8zaFaKBhe6hQp2Y3qgST8vpP+HD9vw@mail.gmail.com>

On Wed, 2017-04-05 at 16:43 -0700, Heather Booker wrote:
> Hi!
> 
> I'd love to work on the Code Review Dashboard project for this round
> of Outreachy.

Great!!

> Are the steps outlined
> here http://markmail.org/message/7adkmords3imkswd still the first
> contribution you'd like to see?

Yes.

> So is this a project that has been worked on in previous rounds of
> GSOC/Outreachy also?
> If so is there a place to find links to the previous participants
> blogs? :)

No. We had one participation at some point, but couldn't even start for
personal reasons. There are some people considering working on this for
this next round of Outreachy, however. You'll see their messages in
this mailing list.

> Should questions about how the specifications/completion of the
> microtask be addressed to
> IRC or this list? If IRC, which channel - #xen-opw or #metrics-
> grimoire? On that note, I'm 
> curious why #metrics-grimoire is the listed channel on the project
> page - are main contributors
> involved in both projects? Or is it just because the Xen dashboard
> doesn't have a channel?

The code review is for the Xen project, but it is done with (I mean,
the ssoftware used for it is) GrimoireLab, which for historical reasons
uses the #metrics-grimoire channel. That's why it is likely that you
find somebody from the project there.

If you have questions, and find me around in IRC, please ping me. If
I'm not available, please send an email message.

Saludos,

	Jesus.

> Thanks!
> 
> Heather
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
-- 
Bitergia: http://bitergia.com
/me at Twitter: https://twitter.com/jgbarah


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-04-06 14:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 23:43 Outreachy project - Xen Code Review Dashboard Heather Booker
2017-04-06 14:05 ` Jesus M. Gonzalez-Barahona [this message]
2017-04-07 22:49   ` Heather Booker
2017-04-08 17:02     ` Jesus M. Gonzalez-Barahona
2017-04-10  4:50       ` Heather Booker
2017-04-13  7:47         ` Heather Booker
2017-04-16 23:23           ` Jesus M. Gonzalez-Barahona
2017-04-17  4:26             ` Heather Booker
2017-04-17  9:04               ` Jesus M. Gonzalez-Barahona
2017-04-19 23:22                 ` Heather Booker
2017-04-13 12:21         ` Jesus M. Gonzalez-Barahona
  -- strict thread matches above, loose matches on Subject: below --
2017-03-31  1:48 Vaishnavi Ramesh Jayaraman
2017-03-31 11:01 ` Lars Kurth
2017-04-02 18:20 ` Jesus M. Gonzalez-Barahona
2017-04-02 20:09   ` vaishnavi.ur777
2017-04-02 21:14     ` 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=1491487513.12313.303.camel@bitergia.com \
    --to=jgb@bitergia.com \
    --cc=heather.j.booker@gmail.com \
    --cc=lars.kurth@xenproject.org \
    --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.