Thank you for the pointers and for the additional sources to check for issues. I had not thought to check the milestones, so I will ensure I read up on them. I also didn't think to look at the L10N stuff, but will also review those.
As mentioned (and I personally abhor duplication whether code or documentation) if this information already lives somewhere, then IMHO pointers to this information should be provided rather than duplicating the information. I will take the responsibility to update the .rst files with pointers and update where appropriate for the process (installation as well as pointers to resources for additional information) and provide it for everyones review and comment. Should this information also be updated on the wiki? I must admit I am a little confused with regards to the wiki and the *.rst files. I followed the conversation yesterday in the (hijacked (my apologies)) thread on "Trac [Recipes]" and gathered that the consensus seems to be to continue to provide end user based documentation in (trac) wiki (this seems reasonable to me), but that developer documentation should be maintained in the *.rst files (also seems reasonable); however, what about the developer documentation that is currently on the wiki? Should this be deprecated and only provide enough information to allow a developer to get access to the sources (location of svn repo and directions on which "set" of code to checkout) and then point them to the *.rst or should there be more info in the wiki? What is the plan for use of the *.rst files, that is, will they be published or how will they be incorporated into the project? Apologies for all the questions, but I also want to ensure that I don't go in a direction that is contrary to where you guys are headed and I don't have enough experience on the project IMHO to really understand the nuances of these issues as yet, so I tend to ask more than a few questions. An appropriate answer might be "grow a set, take ownership, and get it done" which I can do, but again, I don't want to make assumptions based on my lack of experience and history with this project that go contrary to the direction or "spirit" of the project. So you'll have to let me know when the questions become too much and that I should just take ownership and "get it done". Lance Remy Blank wrote: > Christian Boos wrote: > >> Where should this information go? It's already mentioned in >> http://trac.edgewall.org/milestone/0.12 and >> http://trac.edgewall.org/wiki/TracL10N, but that's obviously not enough. >> What are the other places more likely to get consulted for such things? >> The trunk/INSTALL file? >> > > How about a big, fat warning on WikiStart? ;-) > > More seriously, is it possible to specify the Genshi dependency in > setup.py so that it downloads from the advanced-i18n branch? > > I agree that the milestones are the right place to list such issues, but > it seems people (including myself) don't think of looking there. And > trunk/INSTALL, well, I don't remember ever reading it :-/ > > >> Likewise, a link to http://bugs.python.org/setuptools/issue64 could be >> added, maybe directly in setup.py? >> > > How about a CurrentIssues (or maybe ThirdPartyIssues) page, listed on > WikiStart, that lists the most common obstacles for normal installation > / development setup? > > -- Remy > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
