[gnessus-discuss] Contributions (fwd)
lists at securityspace.com
Wed Nov 2 20:03:23 CET 2005
Can this be done without any signficant administrative overhead?
Specifically, if a scenario exists that will see about 10 new plugins
added to the project, on average, every day?
I like the idea of adhering to the KISS principal whenever possible.
Robert Rich wrote:
> This may be out there a bit, but it's something i've been mulling over
> for a while: pluginforge. Why not raise each plugin to the status of a
> mini development project? They all certainly have their own lifecycle,
> reliability, bugs, etc.. Look at the list of 'metadata' tracked by
> source forge on some random project:
> * Development Status: 5 - Production/Stable
> * Intended Audience: End Users/Desktop
> * License: GNU General Public License (GPL)
> * Operating System: All 32-bit MS Windows (95/98/NT/2000/XP)
> * Programming Language: C++
> * Topic: File Sharing
> * Translations: Afrikaans, Brazilian Portuguese, Chinese
> (Simplified), Croatian, Dutch, English, Finnish, French, German,
> Greek, Hebrew, Hungarian, Italian, Lithuanian, Norwegian, Polish,
> Russian, Spanish
> * User Interface: Win32 (MS Windows)
> Two or three may not apply, but most do, and more could be added.
> The nice thing about a pluginforge concept is that it would allow folks
> to publish their own plugins, with their selected license and whatnot,
> without all of the infrastructure overhead that the openvas
> administrators are dealing with now. You could even leverage some of
> the lessons learned through the social networking crowd and let folks
> publish their own 'feeds' that they can then reference from the
> nessus-update-plugins equivalent.
> Just a thought...
> gnessus-discuss mailing list
> gnessus-discuss at gnessus.org
More information about the Openvas-discuss