Device config import

Outback Dingo

unread,

May 18, 2021, 8:10:29 PM5/18/21

to OpenWISP Google Summer of Code

Id be happy to mentor someone, especially if we can nail down and complete device config import.

the.one.above.all.titan

unread,

May 19, 2021, 7:29:26 AM5/19/21

to OpenWISP Google Summer of Code

Hi there!

Thank you for volunteering for mentorship. We started with seven project ideas for GSoC this year and five of them got accepted in GSoC. Hence, we can only work on the accepted project ideas under GSoC.

This certainly does not mean that we won't work on anything else during summers. But this is not the correct mailing list to have that discussion. I suggest you to check whether there's an existing thread on OpenWISP's Support mailing list or an issue on GitHub and continue the conversation there. If there is not, feel free to open a new one.

Please keep in mind that I can't assure you when we will add such a feature in OpenWISP. It will be great to have requirements ready when it's time to implement it.

Best,

Gagan Deep

Federico Capoano

unread,

May 19, 2021, 2:29:07 PM5/19/21

to OpenWISP Google Summer of Code

Hi man,

great to know that.
The application period in which we could propose ideas is closed, now the program is starting.

I believe that in order to implement storing the full configuration of devices we need to take care of the UI side properly, I've been collecting requirements here: https://github.com/openwisp/netjsonconfig-editor.js/issues/23

On the backend side, some work has been done, some other work is pending.

However, I believe this will be an important change which could have destructive consequences on the system, so I don't feel comfortable in delegating it to a GSoC student which is by definition an inexperienced developer and doesn't know openwisp well enough.
I think we have to find organizations which are interested in this feature and willing to fund it so at least 2 experienced developers can work on it full time for a couple of months. GSoC is useful but it's only one side of the equation, most of the code of OpenWISP has been funded with commercial projects.

GSoC projects this year are also shorter (they changed the rules), If you look at the project ideas, you'll se they're not huge projects. The purpose is to allow inexperienced developers to gain experience while doing something useful and challenging, with the aim of turning these students into active contributors that can then progress their skills up to the point in which they can do more challenging work later.