/** \page akonadi_todos Junior Jobs & Todos \section akonadi_jj Junior Jobs Jobs that might be easy for beginners to fix. find JJ in bugs.kde.org \section akonadi_bugs Known Issues find bugs in bugs.kde.org \section akonadi_todo Todos There are serveral ways to keep a list of todos up to date. One method is to use `\@todo` in comments, those todos will end up on a todo page generated by Doxygen: - akonadi todo list - server todo list - libakonadi todo list It is not always feasible to place the todo direclty in comments. If the todo is to create a new class where are you going to write your `\@todo`? For Akonadi we decided to maintain a public developer Todo list in bugs.kde.org. find Todos in bugs.kde.org \htmlonly
Enter new Todo
\endhtmlonly \par Why keep Todos in bugs.kde.org and not in a Wiki? - we have only one place for wishlist, JJ and Todos - users interested in the development or looking for a feature can see what we are working on - the Todo and the corresponding commit are linked (don't forget \c Bug: in your commit message ;-) - we can use the 'owner feature' from bugzilla to see who is working on what \par What is the difference to a Junior Job? JJ are usually more suitable for beginners than Todos. If you think you can solve it anyway, take ownership of the todo item by assigning it to yourself or by posting a comment. If the bug is already assigned to someone it might be wise to ask first ... */