| | Here are a few ideas for new features that could be implemented in Maintain. Please read the [Maintain Code Contribution Guide] first. |
| | |
| | | If there is already a task for this in the JIRA bug tracking system, we also link to it from here. |
| | | If there is already a task for this in the [JIRA bug tracking system|http://bugs.osuosl.org/secure/BrowseProject.jspa?id=10000], we also link to it from here. |
| | |
| | Feel free to add your own ideas to this page, following the same list style as the other suggestions. |
| | |
| | h2. Simple Tasks |
| | |
| | * Bug Fixes |
| | _If you need somewhere to start, you can look through the issues filed as bugs in_ _[_JIRA_|http://bugs.osuosl.org/secure/IssueNavigator.jspa?mode=hide&requestId=10130]__. Most bug fixes are fairly simple._ |
| | * Documentation |
| | _Documenting code that is currently undocumented._ |
| | * Module Hooks |
| | _Adding hooks to meaningful places in the Maintain code. Meaningful means giving the most possible flexibility with the fewest number of hooks._ |
| | * OpenID authentication ([MNT-1531|http://bugs.osuosl.org/browse/MNT-1531]) |
| | _To learn more about what OpenID is: [What is OpenID?|http://iwantmyopenid.org/about/openid]_ |
| | * Authentication module for a forum or [CMS|http://en.wikipedia.org/wiki/Content_management_system] |
| | _Write a module to allow shared authentication between a forum or CMS application and maintain. This would allow network administrators and users to discuss changes in the network without having to keep the authentication information in several places._ |
| | |
| | h2. Moderate Tasks |
| | |
| | * Central Cron Job Facility ([MNT-1565|http://bugs.osuosl.org/browse/MNT-1565]) |
| | * Make distribution specific packages |
| | _Make Maintain packages for Debian, Gentoo, Fedora, SuSE etc._ |
| | * Network Creation Wizard |
| | _Make a wizard to walk people through the creation of a new network, including creating a zone, domains, subnets, ranges etc._ |
| | |
| | h2. Complex Tasks |
| | |
| | * Internationalization ([MNT-1543|http://bugs.osuosl.org/browse/MNT-1543]) |
| | * Logging |
| | _A more sophisticated way of logging what people are doing in Maintain. Currently, there is a log table that gets written on every change, but a more dynamic way of logging (e.g._ _[_PEAR:Log_|http://pear.php.net/package/Log/]_ _would be very helpful. Especially when it comes to displaying and/or analyzing logs._ |
| | * Maintain Core and Module Update Service ([MNT-1544|http://bugs.osuosl.org/browse/MNT-1544]) |
| | * Modularize core Maintain functionality |
| | _Take current Maintain core functionality that is self-contained, put it into a core module and add a module hook._ |
| | * Module Hooks in Datalists ([MNT-1466|http://bugs.osuosl.org/browse/MNT-1466]) |
| | * Move configuration into the Database ([MNT-1407|http://bugs.osuosl.org/browse/MNT-1407]) |
| | * Network Import |
| | _Especially big networks need functionality to import their hosts etc into Maintain. Maintain would have to access their DHCP and DNS configs or servers and suggest a "best fit" representation of the data in there._ |
| | * Native BIND support |
| | _Even though Maintain already supports BIND through TinyDNS export and DNS zone transfers, a module that exports data natively to BIND configs would enable the user to run BIND without the need for a TinyDNS instance._ |
| | |
| | h2. Overhauls |
| | |
| | * Create a testing suite |
| | _Implementing a PHPUnit test suite and/or a_ _[_phing_|http://phing.info/]_ _build script_ |
| | * IPv6 Support |
| | _Add support for the IPv6 protocol into Maintain while retaining the current IPv4 functionality. There have already been a few thoughts about that_ _[_here_|Some Future Ideas]__._ |
| | * PHP5 compatibility ([MNT-1541|http://bugs.osuosl.org/browse/MNT-1541]) |
| | * Add database modification ability in modules |
| | _Modules currently cannot_ easily _have their own entries in the database (a module writer could currently do it with raw SQL). There is a [wiki page|Maintain Overhaul - Modules and the Database] discussing this issue._ |
