On Tue, 24 Jul 2018 10:36:04 +0200 catalin.dominte@nocsult.net wrote:
Hi everyone,
My name is Catalin, and I own a small MSP company in the UK.
Hi Catalin,
as it happens, I'm at EuroPython in Edinburgh this week :)
recently talked to a developer to work on these two features and I will be paying him to do these two to begin with so they are done faster.
I assume you're speaking of at least some of the issues discussed in this GitHub issue: https://github.com/Uninett/nav/issues/1630
However, once he has done this, I would like to make it available into the core code so the entire user community can benefit from it. I will ask my dev to join this list, and if he needs help finding his way around the code is this the best way to ask for help?
Yes, this mailing list is the best entry point for this type of discussion.
Another alternative might be the #nav IRC channel on freenode, but I'm having a hard time getting the other devs to hang around on IRC any more ;-)
Is there a dev based documentation that you can share so the dev can start looking at the way everything is built?
He can start by reading the hacker's guide to NAV (which is constantly in danger of becoming outdated, it seems):
https://nav.uninett.no/doc/dev/hacking/index.html
I have a lot more features planned for the dev once these two are completed, so I hope this will be a long and fruitful journey for all of us and for the Open Source Community!
Many thanks for this really good and easy to use piece of monitoring. It is exactly what I needed!
Thanks for your kind words and your interest in NAV. Please do share your ideas here, so it would be possible to have a discussion about whether they fit with the project, or can be made to fit with the project.
I'll be off on three weeks of vacation starting this weekend, but the other main dev is returning to work on Monday, so hopefully he will be able to give some guidance.