> > 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.
I would loooove if we could at least get one person to agree to maintain each of the per-platform guides (someone that actually knows how to install Trac, since this seems to not be the case with many guide writers). Having official solutions for common platforms (perhaps standardize them all to Apache+FCGI as that is probably the most n00b friendly option) would help a lot of people. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
