Since you're asking, the two features separating our office from a trac deployment:
- Easy inclusion of embedded pictures in tickets - Some editor that doesn't require non-devs to learn wikitext while they can get the basics done (basic formatting and linking). Probably just the first one would probably get it through the powers that be here. On Jun 25, 2007, at 11:44 AM, Erik Bray wrote: > > This discussion has always driven me nuts. Undoubtedly there are > things that could be done to improve Trac's UI, but to what extent? > First of all, if there's anything in specific that needs to be > changed, one can always edit the templates. But when you ask users > what they would prefer to see, you just get into the age-old dilemma > faced by web designers (actually, software developers in general) that > the users don't know what the hell they want. > > We have managers who would prefer to use SharePoint instead of Trac. > They thing the UI is niftier (I think it's utterly hideous compared to > the clean simplicity of Trac--and nowhere near standard-compliant, but > managers don't care about that). They also completely fail to > understand that SharePoint is utterly useless to developers. I don't > know about you guys, but I don't code in MS Word >_> > > Making Trac more non-developer friendly *is* a worthwhile task, but > other than HTML e-mails (people can't get work done if their e-mails > don't come in pink with a flower pattern in the background) I'm not > sure where to begin... Maybe make it more "Web 2.0"-ish? > > Erik > > On 6/22/07, hal_robertson <[EMAIL PROTECTED]> wrote: >> >> I agree with your customer. Trac's interface and usability is great >> for programmers, but quite difficult for business managers. The >> problem becomes apparent when developers and other business units >> need >> to interact, common in agile development team structures, which >> ultimately hurts Trac's adoption. >> >> I have been a continually strong advocate for Trac in my development >> teams. While we continue to hold strong onto Trac, for sure, >> basecamp >> and other similar collaborative tools online have gotten the >> attention >> and the popularity. Business managers view Trac as archaic compared >> to newer collaboration tools with better usability and a cleaner user >> interface design. I am getting constant pressure from other business >> units to dump trac in favor of tools with cleaner design and better >> usability. >> >> >> >> On Jun 22, 2:58 pm, David Abrahams <[EMAIL PROTECTED]> wrote: >>> I have a customer who is unsatisfied with the default look-and- >>> feel of >>> Trac and wants to pay someone to improve it. In his words, "it >>> has to >>> be more attractive, or my domain experts, who are non-programmers, >>> won't use it." I expect this job to involve some graphic design, >>> some >>> CSS, possibly some Genshi template work, and probably some >>> javascript >>> to add slick responsiveness. >>> >>> For best results the designer should have at least some Trac 0.11 >>> knowledge, starting with Genshi -- so that s/he is familiar with the >>> problem domain and I'm not left having to integrate the results into >>> the Trac sourcebase -- and, most importantly, **excellent webGUI and >>> graphic design skills**. >>> >>> I'm excited about this project because it could result in real >>> overall >>> usability improvements for Trac. If you know the person for this >>> job, >>> or if you yourself /are/ that person, please send me an email. >>> >>> Thanks, >>> >>> -- >>> Dave Abrahams >>> Boost Consultinghttp://www.boost-consulting.com >>> >>> The Astoria Seminar ==>http://www.astoriaseminar.com >> >> >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
