The KOffice Developer Resources have now a few task lists. Please note that the tasks are meant for KOffice CVS HEAD. Nevertheless some can be done on KOffice 1.3.x too and some are even general enough to be done elsewhere in KDE too.
Keeping lists of TODOs and such in the codebase is a useful thing; heck, that's why KDevelop red-flags comment lines containing FIXME. But is it really necessary to set up yet another infrastructure here? Just last week we had the JJ: article on the dot, explaining that trivial or easy wishlist items and small bugfixes can be entered in bugzilla and marked with JJ: in the summary field in order to attract new volunteers that feel they need a little handholding, but would still like to help out. Why doesn't KOffice do the same?
Sorry, I was aware of the JJ: idea well after I had started the task lists. (I would not mind to mark a bug as JJ: if I would find a wish in KDE Bugs that fits into this category.)
As for TODO and FIXME, that is how it is done in KOffice too, but practice has shown that mostly potential new developers do not search tasks in code. That is why this method is explicitely explained in the task list index.
Have a nice day!
I think it is a great idea to supply customised task lists. These are just some things that popped up in my head as I was reading...
Perhaps some kind of task tree could be constructed, so each kind of developer, from junior to pro, can find appropriate tasks at one place and see the relations between tasks. I do not know whether a similar system already exists, but some kind of graphical representation of the bug tracking system would certainly render a lot mare accessible, an additional tree-representation, for instance. (A picture says more than 1000 words...)
What about presenting the current task lists and properties (difficulty and shareability) as a table? It will probably yield a more compact representation and overview of the tasks.
As I am not doing anything with KDE Bugs, I cannot answer your anser about a graphical (or any better) representation of the bugs. KDE uses Bugzilla and will remain so in at least near future.
As for the KOffice Task Lists, yes, the look could be improved. (I will keep your idea of a table in mind.) The current look was more make quickly to fill a need, as some developers seemed to think that KOffice is too difficult for them.
I'd like to see KOffice adhering to the JJ bug marking in the future, it is much easier to find bugs and features to implement that way.
Just my comment.
There are currently 3 KOffice bugs marked as junior jobs:
#63011, #63015, #76412
Personally I am hesitating to put these 2 bugs as junior jobs:
#76297 and #76298
Otherwise in the KWord and KOffice "products" of KDE Bugs, I do not see what other bugs could be marked as junior jobs. However that does not mean that they are not any easy tasks to do in KOffice, but reported bugs are mostly not easy.
By the way, a query for Junior Jobs was added directly in the entry page of KDE Bugs: http://bugs.kde.org
The query is KDE-wide.