<div dir="ltr"><div><br></div><div>Hello,</div><div><br></div><div><br></div><div>I am Oluwatobi, I love to contribute to kea, I have built and install kea and have been going through the documentation/familiarise my self</div><div>to the project, I have found tickets that I can start working and solve. But I have not been able to register on-site, I keep getting Trac Error that</div><div>my submission is a potential spam and that my Ip address is blacklisted. I have had this problem with my first attempt. I connect to the internet</div><div>using a mobile internet provided by my ISP( orange Cameroon ). Just maybe am not following the correct process, I will love to get help on how to complete this process</div><div><br></div><div>thank's</div><div><br></div><div>Oluwatobi.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 13, 2018 at 7:33 PM, Tomek Mrugalski <span dir="ltr"><<a href="mailto:tomasz@isc.org" target="_blank">tomasz@isc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jerin,<br>
Thanks for your interest in Kea project. See my responses below.<br>
<br>
On 10/03/2018 08:50, Jerin John wrote:<br>
> I was intrigued by ISC's Kea, and going through the features and<br>
> scope of your DHCP software has inspired me to send an application<br>
> via GSoC, to contribute as a part of your dev team. I was hoping to<br>
> send a proposal in reference to your idea for the *'Kea monitoring<br>
> dashboard*', to implement a standalone web application that<br>
> integrates with your REST APIs, using *Angular *framework and basing<br>
> the GUI on material design.<br>
><br>
> I have a fair background in web development, being a part of an<br>
> internship and training program that provided exposure to<br>
> technologies like JSPs, Servlets, PHP and most recently JavaScript<br>
> frameworks like Angular and React; would be glad to provide a<br>
> detailed account of my previous work experience, if you see me as a<br>
> potential candidate for the role.<br>
I'll send you some off the list questions.<br>
<br>
> I would really appreciate it if you could provide me insights into<br>
> the requirements for this dashboard,<br>
Vicky will come up with more detailed requirements, but the general core<br>
requirement is to have a visualization of the state of the server. Think<br>
how people are using their DHCP servers. On a very basic level, there is<br>
a sysadmin that monitors often very complicated network. So the<br>
dashboard has to display the list of subnets and shared networks, and<br>
display a state for them. Over time, the dashboard should allow some<br>
configurability.<br>
<br>
There are many use cases to cover here. I'm sure the community will be<br>
more than happy to come up with scenarios that would be good to cover.<br>
<br>
Please read the User's Guide and find out how the server configuration<br>
is structured, what types of configuration elements are used and how<br>
would you like to display them.<br>
<br>
> methods to start contributing and all your suggestions to get myself<br>
> accustomed to your code base and dev practices.<br>
The usual way is via github. We have Kea Contributor's guide<br>
<a href="https://jenkins.isc.org/job/Kea_doc/doxygen/" rel="noreferrer" target="_blank">https://jenkins.isc.org/job/<wbr>Kea_doc/doxygen/</a>, click on Contributor's<br>
guide. For GSoC we'd like to more or less follow it.<br>
<br>
> specifics of the Kea API,<br>
I'm sure you found out the kea website already. There's a User's guide<br>
there. We have two versions of it: stable (that documents the latest<br>
release 1.3.0) and development (which documents our latest version from<br>
git, being regenerated daily). You may want to look at that. Section<br>
8.9, 9.13 and 16 describe the API. Section 19 describes kea-shell, which<br>
is a simple tool to use that API.<br>
<br>
> I believe Kea would provide me the perfect platform to gain vast<br>
> amounts of knowledge, exposure to the open source community and<br>
> ultimately mold myself into a better software developer.<br>
><br>
> Looking forward to hearing from you. Thanking you in anticipation.<br>
Thanks for looking at Kea. You're a bit late to the crowd (first<br>
students contacted us 3 weeks ago), but as I understand the process,<br>
there's still plenty of time for you to write your proposal.<br>
<br>
Good luck,<br>
Tomek<br>
______________________________<wbr>_________________<br>
kea-dev mailing list<br>
<a href="mailto:kea-dev@lists.isc.org">kea-dev@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-dev" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-dev</a><br>
</blockquote></div><br></div>