Future
So what features does Devalot have in its future? This is a brief list of the candidate features that might find their way into a future release. Leave your vote in a comment on this page.
Search System
It doesn’t take long to build up a lot of content. Devalot edge has an experimental search system based on Ferret that is getting closer to production quality. This will be in the 0.2 release.
Page Watch
Would you like e-mail notification when a particular page or ticket is updated? The watch feature will make this happen. This feature is targeted for the 0.2 release.
Anonymous Comments
Not everyone wants to create an account just to leave a comment, and who can blame them for not wanting to go through all the trouble? Support for anonymous comments is targeted for release 0.3 or 0.4.
Project Planning and Milestones
Add a target release and time estimate to a ticket, and assign that ticket to a milestone for a rough idea of how long it will take to reach that milestone. You’ve seen these before, we want to make them even better in Devalot.
Forum
Part mailing list, part bulletin-board, the forum will be a great place for developers and users to interact.
Code Repository Integration
Want to browse your source code repository, see commit messages and tie commits to tickets? So do we, and we’re planning how this feature works. Subversion will likely be the first supported system.
File Manager/Asset Manager
Developers need to be able to upload files, right?
Updated Jun 17, 2008 by Isaac Foraker
Tags:
Comments:
How about integration on Continuous Integration system?
Very interesting tool and very promising for new features on development. It would be nice to have a Timeline page like Trac, that lists all changes on every site sections: tickets, milestones, repository commits, wiki pages, etc.
You mentioned "File Management" and I would have to emphasize image management as well. I suppose you could even shortcut it, and add something like tinymce and let people purchase MCImageManager.
Absolutely. The file management part would be for uploading files that other users can then download. To put images on pages and articles, I plan on having a system where you can attach arbitrary files to those objects. The code is mostly there already, it just needs an interface.
I would like second Eivind and strongly urge you to write an SCM abstraction API/layer. Subversion is certainly not the be all/end all and requires a lot more set up than some more fully featured and distributed version control systems such as darcs, mercurial, and git.
I'm discovering your software and all the features I see you want to implement are EXACTLY what we are looking for. Hang On !
I am compelled to add the comment that SCM integration is the target of ticket 139
Have something to say? Login to post a comment.
Eivind Uggedal, Feb 07, 2007
Level 2 (Tourist with 1 point)
It would be great if Devalot could get a SCM abstraction API/layer right from the start with regards to the plans for Subversion integration. Distributed SCM systems as Mercurial, Bazaar, Darcs and others are starting to get more common each day. Thinking about a solution that integrates both centralized and distributed SCM systems from the get go would therefore be a feature that could set this project apart from it’s competition in my humble opinion.