also sprach namnd <[EMAIL PROTECTED]> [2008.02.17.1720 +0100]: > My team have been developing a software for my company since 2004, > now I have plan to release it to the public, hopefully in an open > source license if the management board doesn't object. So I need > the peer reviews from the community of the quality of the > software […]
Hello Nam, I am the author of netconf (http://netconf.alioth.debian.org), which Brian has already introduced in another post to this thread. I am very interested in your work because all the issues you highlight in your mail are core to my motivations for writing netconf. You are asking us to evaluate the quality of a software based only on the descriptions you provide. This is really difficult. While others have picked up on shortcomings, such as the use of XML, I wonder about certain other things: - what language are you using? - is this a daemon-based design? - how much internal state do you keep? - how extensible is the software? - how large is the code base? - how do you interface with e.g. openvpn? Do you wrap it (and thus limit the possible configuration), or do you feedthrough to it (and thus provide the full configuration abilities)? - does your software handle wireless networks, including those configured by wpa_supplicant? I think it's always a good idea to release software to the public. As such, I encourage you to convince your management to slap a good licence onto your work. On the other hand, you and your team may also be interested in netconf. You surely have a lot of experience in the domain, and netconf could greatly benefit from your input. While netupdown seems designed to override shortcomings in ifupdown, netconf aims to fix those at the root. netconf is currently implemented in Python, but that only really makes it easier for others to read the code and contribute to it. Unfortunately, netconf is not yet ready for use, but it's not very far either. Please release your software to the public and then consider joining the netconf team and getting your colleagues interested too. We can then reuse your work on netupdown and integrate it into netconf to add advanced network configuration abilities to Debian by default! -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems there is no place like ~
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
