[Interop-dev] GSoC 2017 student application

[Nemesis]

Yes you should. According to the GSoC rules, you can start sending your
proposal from 20th of March onwards, consult the official GSoC timeline
for more precise information:
https://developers.google.com/open-source/gsoc/timeline

At this stage, I highly suggest you to try the library, play with it,
consult the issue list:
https://github.com/netjson/netjsongraph.js/issues - is there any issue
easy enough that you would be able to solve right now?

We want to be sure the students we accept in our organizations are
autonomous, you work on a problem, if you get stuck you ask a few
questions, but you go ahead on your own and come up with a good enough
solution. If you can show to be able to propose good solutions for the
problems we are working on you have a higher chance of being accepted.

Federico


On 03/02/2017 05:33 PM, Xiang Gao wrote:
> Great thanks. I have experience for network visualization and ready to
> get started. Should I write a proposal to Freifunk?
> 
> 
>> On Mar 1, 2017, at 16:49, Nemesis <(spam-protected)
>> <mailto:(spam-protected)>> wrote:
>>
>> I'm contributor OpenWISP, NetJSON and Ninux and I have been mentor and
>> organization admin for Freifunk a few times in the previous years
>> (almost every year since 2011), I know personally many people in
>> Freifunk and we are good friends.
>>
>> All these projects have a slightly different scope but have one common
>> denominator: they want to make it easier to build bottom-up computer
>> networks (wireless, mesh, wired, radio, fiber, whatever technology).
>>
>> The NetJSON implementation ideas present in
>> http://openwisp.org/gsoc/ideas-2017.html are focused on the
>> configuration part (NetJSON DeviceConfiguration), which is the current
>> focus of OpenWISP 2.
>>
>> NetJSON is an open format and can be implemented by any software.
>> My aim in trying to get NetJSON accepted as a mentoring organization was
>> to help it gain popularity, but I knew the chances were not very high so
>> I made sure to write the same project ideas in multiple places, because
>> I think those project ideas are valid and useful indipendently on which
>> umbrella organization works on them, be it Freifunk, Ninux or NetJSON.
>> Since in the ninux.org <http://ninux.org> community network we are
>> using the NetJSON
>> NetworkGraph objects to collect and visualize topology information, it
>> makes sense to keep working on this front with Freifunk, which is an
>> Umbrella organization for community networks.
>>
>> But this are just my ideas and do not represent the view of Freifunk as
>> I haven't had the time to discuss thoroughly with them. The number of
>> available projects will depend on the number of applications Freifunk
>> gets.
>>
>> Therefore, if you like the project you were interested in, get involved
>> as soon as you can, show that you care, that you are able to improve it
>> so it can be useful to all the communities collaborating with Freifunk.
>> We are actively looking for new, valid and passionate contributors, if
>> you think you are one, show us!
>>
>> Federico
>>
>>
>> On 02/28/2017 07:28 PM, Xiang Gao wrote:
>>> Hi,
>>>
>>> Excuse my-ties, I wonder what relationship between OpenWisp and
>>> Freifunk? I saw the NetJSON project in
>>> http://openwisp.org/gsoc/ideas-2017.html, too.
>>>
>>> Best regards
>>> Xiang
>>>
>>>
>>>> On Feb 28, 2017, at 20:37, Nemesis <(spam-protected)
>>>> <mailto:(spam-protected)>
>>>> <mailto:(spam-protected)>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> NetJSON has not been accepted for the GSOC 2017, but you can still apply
>>>> with Freifunk for the same ideas, see
>>>>
>>>> https://wiki.freifunk.net/Ideas#Netjsongraph.js:_canvas_and_geographic_data
>>>>
>>>> Best regards
>>>> Federico
>>>>
>>>>
>>>> On 02/22/2017 07:16 PM, Nemesis wrote:
>>>>> On 02/22/2017 03:34 PM, GeekPlux wrote:
>>>>>> Great thanks for all.
>>>>>>
>>>>>> Sounds very cool and useful. I don't know about wireless dev, but
>>>>>> know a
>>>>>> generic data format is important. Do I need to understand OpenWISP2?
>>>>>
>>>>> You don't need to understand OpenWISP2 in order to work on
>>>>> netjsongraph.js.
>>>>>
>>>>> You need to know NetJSON, be sure to read the information provided on
>>>>> the website and the RFC.
>>>>>
>>>>> Federico
>>>>
>>>
>>
>