Hey Jeroen
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeroen Ruigrok/asmodai
> Sent: 19. október 2006 17:06
>
> I have played EVE Online in the past so it is, as both a user
> of Trac and ex-user on EVE Online, nice to see you guys using it. :)
;)
> I assume your Trac instance is private?
Correct.
> >We realize that all this takes a lot of work and we are
> thinking of how
> >we can speed up this process. We have some resources to dispense for
> >Trac, but those mostly go towards in house customizations and
> >specialized plugin development.
>
> Any bugfixes or the likes are more than welcome. :)
We have submitted a few bug fixes, although not many. More to plugins then the
Trac core itself, as running into bugs in Trac is pleasantly rare.
> Well, allow me, even though I am far from a core Trac
> developer, to throw the question at you:
>
> what are the top three things CCP missed within Trac as it
> currently is?
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.
* 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.
* 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.
* 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.
These are the highlights of my "Official Trac wish/todo list". There are 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*. These are thing we were going
to do ourselves one day and submit them back into the community - but as our in
house customization task list gets longer and longer each day I'm not sure when
we'll finally get around to it ;) !
* Currently hardcoded to only support wiki/tickets - although the module could
provide attachment support for external plugins with minor changes. The real
"issue" would be the solving permission mapping (perm_map) in an elegant
manner, but this could be defined in trac.ini..
> Such real-world commercial feedback is also quite important.
>
> All in all, nice to hear and thanks for the push! I am sure
> it is greatly appreciated.
I hope it is well received. It is not meant as a criticism in any way, shape or
form. We are very pleased with Trac's progress so far and feel we have a
similar vision as the Trac Development Team. As you can see the four "important
things" are all on Trac's agenda. However, this project - like any other for
that matter - could always use a few extra hands working towards the goal of
improvement.
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 ...
Cheers,
Bjorn Swift
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
