-On [20061019 21:02], Björn Swift ([EMAIL PROTECTED]) wrote:
>Let me state four in a semi-prioritized order. All of them are in the roadmap.
> * Workflow: We, as many others (according to the mailinglist discussions),
> are very much looking forward to the workflow branch being merged into
> trunk.
I think that is either scheduled for 0.11 or 0.12. Alex or Christopher
probably know best.
> * Multiple projects: A lot of work needs to be done before this becomes
> a reality - but having a special environment for each project has it's
> disadvantages. We now try to use Components to divide into projects
> (where that is possible) - but as you can imagine that is not very
> efficient. Not a realistic feature request for the next release, I
> know, but something that will defiantly benefit a large number of the
> Trac userbase.
The multiple projects one is a pet peeve of myself. Unfortunately my Trac
internal clue is not that great yet to dedicate time to this.
> * Improved Search: As our Intranet Wiki grows it's getting harder and
> harder to search for what you are looking for. Even though we try to
> structure and tag our pages efficiently, being able to search for what
> you are looking for is very important.
I had a discussion with some people in a totally different market about
reinstating lupy. Would be interesting in the long run perhaps for this.
> * PermissionPolicy: In a company of 150, not all employees should have
> the same access level. If a proper ACL system were in place once could
> bump the Wiki's usefulness up to another level.
What kind of permission problems are you running into now? Just to get an
idea.
>These are the highlights of my "Official Trac wish/todo list". There re also
>quite a few smaller issues we have listed, ranging from changing the "Last
>Change" link to "Last Changed by {user}", to refactoring the Attachment
>module so other plugins can take use of it's features*.
Whenever you can, drop notes like these to the mailinglist, you might just
encourage someone to pick it up and work on it. Sometimes the idea hasn't
occured at all to a group of people and such ideas can really stimulate, just
like the current email. :)
>I hope it is well received. It is not meant as a criticism in any way, shape
>or form.
I think a person would be hardpressed to see it as a criticism. :)
>Finally; regarding release cycles. I would have to agree with Ilias Lazaridis
>and his comment regarding splitting tasks into multiple milestones. It might
>be worth assigning fewer tasks to each milestone and releasing more often -
>not to bite off more than one can chew. This might even work as a boost to
>developers, seeing as there is "so little work to be done for this next
>release". Not wanting to take it to the extreme, of course ...
I think this is essentially what the main developers --and Christopher or
Jonas, Alex or the likes can correct me if wrong-- are already working
towards.
A question back to you guys: would faster releases, say every 3 months to just
name a figure, cause upgrade issues?
I personally, for my pet project, found upgrades for just trac to take about 5
minutes in total of my system administration time. With plugins you will wind
up with some more time needed of course.
--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/
Seize from every moment its unique novelty and do not prepare your joys...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
