From: Iresha Perera <ireshaharshani.13@cse.mrt.ac.lk>
To: "Jesus M. Gonzalez-Barahona" <jgb@bitergia.com>
Cc: lars.kurth@xenproject.org, xen-devel@lists.xen.org
Subject: Re: [Outreachy] - Xen Code Review Dashboard
Date: Mon, 3 Apr 2017 09:30:03 +0530 [thread overview]
Message-ID: <CAGEwzfrQiitywZ8joOWeBGgM-3W7wjADBWP3SVrerwknAoyC6Q@mail.gmail.com> (raw)
In-Reply-To: <1491157061.12313.144.camel@bitergia.com>
[-- Attachment #1.1: Type: text/plain, Size: 2457 bytes --]
Hi Jesus,
I have a good knowledge on Python and a basic knowledge on noSQL concepts
and ElasticSearch. I started following a tutorial to improve my knowledge
on ElasticSearch. Because I'm a quick learner and I'm really interested on
doing this project, I'm sure I will be able to improve my knowledge on
ElasticSearch quickly.
Could you please let me know a possible time for you to have an IRC chat?
Thank you very much.
Sincerely,
On 2 April 2017 at 23:47, Jesus M. Gonzalez-Barahona <jgb@bitergia.com>
wrote:
> On Sun, 2017-04-02 at 15:43 +0530, Iresha Perera wrote:
> > Hi all,
> >
> > I'm a 4th year undergraduate at University of Moratuwa, following a
> > Computer Science and Engineering degree. I'm interested in Xen Code
> > Review Dashboard project and I would love to participate in this
> > project for Outreachy program, 2017. I have a good knowledge on SQL,
> > Java, Javascript, HTML5 and XML and I have done several projects with
> > these technologies.
> >
> > To start with Outreachy program, I need to make a contribution to the
> > Xen Code Review Dashboard project.I read about the Contribution
> > Guidelines. It would be very grateful if you could provide me with
> > the details on how I can make an initial contribution to this
> > project, in order to participate for the Outreahcy program.
>
> Hi, Iresha,
>
> First of all, thanks for your interest.
>
> And now, a warning notice: this project will require mainly Python and
> noSQL (ElasticSearch, in particular) knowledge. If you're not familiar
> with them, that could be a big problem.
>
> [Lars, I now notice this is wrong in the project description at
> https://wiki.xenproject.org/wiki/Outreach_Program_Projects
> sorry about that. Could we change it?]
>
> If you're still interested, I guess it would be good to have a quick
> IRC chat, and discuss about the initial contribution.
>
> Saludos,
>
> Jesus.
>
> > Thank you very much.
> >
> > Sincerely,
> > --
> > Anne Iresha Perera
> > Department of Computer Science Engineering
> > University of Moratuwa
> > Sri Lanka
> >
> > _______________________________________________
> > 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
>
>
--
*Anne Iresha Perera*
Department of Computer Science Engineering
University of Moratuwa
Sri Lanka
<https://lk.linkedin.com/in/ireshaharshani>
[-- Attachment #1.2: Type: text/html, Size: 5765 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-03 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 10:13 [Outreachy] - Xen Code Review Dashboard Iresha Perera
2017-04-02 18:17 ` Jesus M. Gonzalez-Barahona
2017-04-03 4:00 ` Iresha Perera [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:
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=CAGEwzfrQiitywZ8joOWeBGgM-3W7wjADBWP3SVrerwknAoyC6Q@mail.gmail.com \
--to=ireshaharshani.13@cse.mrt.ac.lk \
--cc=jgb@bitergia.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 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).