[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    [syslog-ng] Syslog-ng: GSoC2015: Project: Riak Destination
From:       Parth Oberoi <htrapdev () gmail ! com>
Date:       2015-03-12 15:57:00
Message-ID: CAL_C7Ezbfxccrj9BWeqRaq_q8fR_LpmygC7xoVgJicZqBefYsg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hello everyone,

I am a prospective gsoc 2015 applicant and wishes to apply to it under the
New Destination Project -Riak Destination .
@algernon-the mentor for this project gave me a few pointers to get started
get started, so i have gone through the following things

1- compiled syslog-ng from source
2- went through the configuration docs(chapter 5), found it pretty
interesting
3- Read up on the Google protocol Buffers and reading through the examples
of its c library protobuf-c
4- did set up a single riak node()(will experiment with it after i set up
the riak-c-client which i am currently installing)

The things i am planning to do in the coming couple of days is to figure
out the features of riak 2.0 that riak-c-client does not support and really
would have to decide whether to use this library and implement the missing
features or develop the new one . Only after this step can i lay down a
project plan for the GSoC time period.

Also i have working knowledge of C, lex and yacc (brushing them up these
days). Any suggestions or tips or ideas would be welcome. I usually learn
as i go and have a keen interest in new technologies,so any other
prerequisite that i should have or that can help me in the project should
be told.
I am usually always online so i can be reached at htrapdev@gmail.com , irc
nick: @htrap.

Github: github.com/htrap

Please let me know if any other details are required. looking forward to
suggestions.

Regards,
Parth Oberoi

[Attachment #5 (text/html)]

<div dir="ltr">Hello everyone,<div><br></div><div>I am a prospective gsoc 2015 \
applicant and wishes to apply to it under the New Destination Project -Riak \
Destination .</div><div>@algernon-the mentor for this project gave me a few pointers \
to get started get started, so i have gone through the following \
things</div><div><br></div><div>1- compiled syslog-ng from source</div><div>2- went \
through the configuration docs(chapter 5), found it pretty interesting</div><div>3- \
Read up on the Google protocol Buffers and reading through the examples of its c \
library protobuf-c</div><div>4- did set up a single riak node()(will experiment with \
it after i set up the riak-c-client which i am currently \
installing)</div><div><br></div><div>The things i am planning to do in the coming \
couple of days is to figure out the features of riak 2.0 that riak-c-client does not \
support and really would have to decide whether to use this library and implement the \
missing features or develop the new one . Only after this step can i lay down a \
project plan for the GSoC time period.</div><div><br></div><div>Also i have working \
knowledge of C, lex and yacc (brushing them up these days). Any suggestions or tips \
or ideas would be welcome. I usually learn as i go and have a keen interest in new \
technologies,so any other prerequisite that i should have or that can help me in the \
project should be told.</div><div>I am usually always online so i can be reached at \
<a href="mailto:htrapdev@gmail.com">htrapdev@gmail.com</a> , irc nick: \
@htrap.</div><div><br></div><div>Github: <a \
href="http://github.com/htrap">github.com/htrap</a></div><div><br></div><div>Please \
let me know if any other details are required. looking forward to \
suggestions.</div><div><br></div><div>Regards,</div><div>Parth \
Oberoi</div><div><br></div><div><br></div></div>



______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq



[prev in list] [next in list] [prev in thread] [next in thread]