> > > I want to propose (well voice a proposal from Alec) that we move the > > > official documentation in to the repo. There is a growing problem > > I really can't take credit for any innovation here, I'm just proposing > we emulate what Chris did for Genshi and Babel:
That seems like a reasonably good solution. > > Do we have the human resources to move to this model? I have strong > > doubts about this point. > > In what way? I echo this question. I don't know that it's going to take more effort for sure. > > OTOH, I think the first thing to do about the docs is to "branch" it: > > one area for Trac 0.10, another area for Trac 0.11 - which means > > duplication of info - but we really need to create two areas rather > > that to add those "since 0.11" stuff. 0.11 is really different than > > 0.10, and I agree: t.e.o. is getting more and more confusing each day. Indeed, it's confusing. But we also need to keep in mind how search engines are going to return docs. If someone searches for "tracmercurial" and arrives at the wrong version, we need to make it obvious how to switch to the right version of the docs. > There's another potential opportunity here too: removing the user > visible wart of having all the documentation in their Wiki and timeline. > A request handler could be written to serve Trac documentation instead. Have you already started any work on this? I'd like to see a proof of concept before I say this is obviously better than the wiki (because the wiki currently handles all the linking issues). Tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
