On 11/23/07, Christian Boos <[EMAIL PROTECTED]> wrote: > * go on with the fine-grained permissions work: > - the browser svn_authz should be transformed into a permission > policy (maybe even a 0.11.x thing, as this will be transparent to the user)
I always envisaged this being the case. It makes sense. However perhaps we should wait until we move to the "next" stage of the permission system? Then we can have a single policy that does everything. Perhaps authz for all of Trac. > - the permission checks could be performed also in the data model layer We've discussed this quite a bit on IRC. Enforcing permissions at the data layer seems a bit wrong for some reason, but it certainly offers consistency as an advantage. Perhaps it wouldn't be too bad if you could pass an optional perm object to the model object, or abstract it further by adding a filtering system on top of models - views, effectively. I'd be happy to look into this. > - fix the implementation of group providers, as outlined in the > "[RFC] get_user_groups" thread > * improve the search feature: I'm not talking about that grand redesign > that keep being postponed, just about some incremental improvements that > have a very good benefit/effort ratio: > - sorting by relevance in addition to sorting by date, > - "send ticket matches to custom query" feature. +1. I'd be happy to take a look at this. > Then, there's the very important topic of all the known tickets already > scheduled for 0.10.x and 0.11.x maintenance lines. > > That is a really /huge/ amount of work there: > - there are still *80* open tickets for 0.10, some of them quite > critical. We should g through that list and retarget some of those to > 0.11.x and 0.12, as I don't think they'll ever get fixed on the 0.10.x > line at this point. > - there are already *192* tickets for 0.11.1 tickets. Last week, I made > a copy of that list and annotated it with a more realistic estimate, > planning to move most of them to 0.12 and beyond. > - among the 130 un-triaged tickets, a good deal of them are probably > worth addressing as well. You're right, that's many, many tickets :(. I just had a quick look, and the majority of them certainly warrant attention of some sort. > So here's a summary of the future steps as I see them. > > Main features for Trac 0.12: > - rendering refactoring (cboos, cmlenz?) > - wiki engine refactoring (cboos) > - SQLAlchemy, if it proves to be successful (jruigrok, cboos) > - i18n, even partially (cmlenz, jruigrok) > > Later steps (beyond or started parallel to 0.12): > - advanced search (aat?) I'm absolutely still planning on this. > - alien technology (jonas?) +1! -- Evolution: Taking care of those too stupid to take care of themselves. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
