<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/22/2015 02:04 AM, Mitar wrote:<br>
</div>
<blockquote cite="mid:555E7286.9050301@tnode.com" type="cite">
<pre wrap="">I agree. With nodewatcher v3 we are making all functionalities a Python
modules. It should be relatively easy then to extract them into a
stand-alone package which can be used by itself, or as a nodewatcher
module. Once a function is encapsulated with a clean API, then it is
much easier to make it stand-alone as well.</pre>
</blockquote>
<br>
That's great, because when a package is general is enough, it can
receive contributions from a broad range of people.<br>
<br>
<font face="Helvetica, Arial, sans-serif">Is there any particular
feature you have been able to <font face="Helvetica, Arial,
sans-serif">extract into a separate python package<font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"> that we can start contr<font
face="Helvetica, Arial, sans-serif">ib<font
face="Helvetica, Arial, sans-serif">uting to?<br>
<br>
<font face="Helvetica, Arial, sans-serif">In nodeshot,
we extracted a few that are qu<font face="Helvetica,
Arial, sans-serif">ite used in the django community<font
face="Helvetica, Arial, sans-serif"> and re<font
face="Helvetica, Arial, sans-serif">ceive quite
many interesting <font face="Helvetica, Arial,
sans-serif">patches</font></font>:<br>
</font></font></font></font></font></font></font></font></font>
<ul>
<li><a class="moz-txt-link-freetext" href="https://github.com/djangonauts/django-rest-framework-gis">https://github.com/djangonauts/django-rest-framework-gis</a>
(geojson api)<br>
</li>
<li><a class="moz-txt-link-freetext" href="https://github.com/djangonauts/django-hstore">https://github.com/djangonauts/django-hstore</a> (key value store
in postgres)<br>
</li>
<li><a class="moz-txt-link-freetext" href="https://github.com/djangonauts/django-rest-framework-hstore">https://github.com/djangonauts/django-rest-framework-hstore</a>
(add support for hstore in django-rest-framework)<br>
</li>
</ul>
<p>Networking side, there are these two, which are quite new:<br>
</p>
<ul>
<li><a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/netdiff">https://github.com/ninuxorg/netdiff</a> (detect changes in network
topology)</li>
<li><a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/netengine">https://github.com/ninuxorg/netengine</a> (intended for automatic
data entry in the node-db for nodes that are not self generated,
eg: importing an existing network - not quite ready for
production use yet though)</li>
</ul>
<p>And then there are a few other features that I plan to extract
later:<br>
</p>
<ul>
<li>an elevation API proxy that returns GeoJSON, needed for the
elevation profile tool into our frontend, now is a view residing
here:
<a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/nodeshot/blob/master/nodeshot/core/nodes/views.py#L269">https://github.com/ninuxorg/nodeshot/blob/master/nodeshot/core/nodes/views.py#L269</a><br>
but can easily extracted in a separate package<br>
<br>
</li>
<li>a proof of concept of storage for metrics/statistics built
with influxdb 0.9 rc:<br>
<a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/nodeshot/tree/master/nodeshot/core/metrics">https://github.com/ninuxorg/nodeshot/tree/master/nodeshot/core/metrics</a><br>
I read that some Freifunkas are interested in influxdb, I tried
to reach them here:<br>
<a class="moz-txt-link-freetext" href="https://github.com/tcatm/meshviewer/pull/8#issuecomment-103854925">https://github.com/tcatm/meshviewer/pull/8#issuecomment-103854925</a><br>
But got no response, and on that repo I cannot find information
on how to get in touch. Peraphs someone reading here could tell
them that we are also working on it and I've been following
actively the development of influxdb 0.9, contributing to the
python-client in order to fix an issue I was expriencing.</li>
</ul>
<p>The approach to extract packages has proven to be very effective.
It takes a bit more time initially to do the work, but afterwards
each package can thrive indipendently and find new contributors.<br>
</p>
<p>Federico<br>
</p>
</body>
</html>