Jonas Borgström kirjoitti:
> Jani Tiainen wrote:
>> Now that 0.11 is really finally out I can roll it to my work environment
>> - together with SVN 1.5... And break things just before I leave for
>> summer vacation :D
>>
>> Well not really, even as an idea it sounds more than fun for my coworkers...
>>
>> Now three "outstanding" issues that I would like to point for future
>> releases, and preferably by contributing myself. At least by some noise
>> here.
>>
>> Last autum (around middle of November) there was short discussion about
>> information quality in tickets, and generally some other things about
>> documentation of Trac. And now I'm specially referring to end user
>> documentation. This area could do some improvement, something like "Trac
>> documentation team", which only takes care of that documentation is up
>> to date and collects relevant information from all that information
>> noise that is in tickets, here on mailing list etc. This is just an idea.
>
> I'm not yet that familiar with Odd's newhelp branch but I hope we're
> able to include this or some similar solution into 0.12. Forming a
> Documentation team also sounds like a great idea if there is enough
> interest.
Well, that's easily tested... :D
>> Advanced reporting. Current reporting methods are very much limited -
>> there is very basic form of search and list results but anything beyond
>> that - specially ad hoc reports are not easy to do with current
>> interfaces. I've already implemented in different context this kind of
>> generic reporting engine. I could try to do same for Trac. I think it
>> can be done as a plugin without hacking core itself. Unless this already
>> exists.
>
> This is a great example of a piece of isolated functionality that could
> initially be developed as a plugin both to make development easier and
> to make it usable before (and if) it's later included in trac-core. But
> as long as it's a general report system I think it's a good candidate
> for core inclusion.
Since 0.11 query is pretty powerful and customizable I don't see this
kind of functionality essential (except timetrackers would like to have
it :D)
>> And finally, more complex feature that might need some attention in core
>> itself. User centric data and interactions. Good example would be saving
>> your own favorite queries, having private tickets/wiki pages and finally
>> possibility to listen ticket changes. This would change a lot how Trac
>> works nowadays, but also it would give lot of new oppurtunities.
>> Specially if bundled together with AccountManager plugin.
>
> Agreed, this an area that has a lot of room for improvement.
> Unfortunately the current db schema and the way our authentication
> systems works makes this nontrivial.
I think I'll put some of my freetime to this feature since it's
nontrivial and would provide lot of added value. In theory it would
render CC-list unnecessary (not really, there is still use for that) but
most of the time you just need to mark "follow this" and you start
getting e-mail spam.
Basically my idea is to have:
- Extensible user profile
- Roles/Groups/ACL or what ever...
- Link user profile to other components (like ticket and wiki)
(as a listener for changes)
--
Jani Tiainen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
