Pauli Virtanen napisał(a): > I think the "change suggestions" should be something similar to bug > reports, with fixed workflow that enables developers/doc editors to > easily find out present suggestions, possibly discuss them with the > submitter, and finally mark them as done or invalid. At least to me this > looks something similar to what an issuer tracker software does.
That's exactly how I see it. Thanks for confirmation, Pauli. > Adding support for other VCSes in Pydocweb is reasonably straightforward > (write a suitable pull script specific for your repository arrangement, > see eg. www.pymvpa.org/edt where it's running with Git). There's actually > no Subversion-specific code in Pydocweb even though it says "SVN" in the > UI. Uh, greping through the sources too fast :) Good point, thanks. > But perhaps Georg had something more lightweight in mind; not so much an > app for editing documentation, but one for just hosting static versions > of Sphinx docs with search/feedback features. OK, but then, don't you think that creating such web app is not enough for whole summer? Looking at the ideas list I think that adding a MediaWiki output builder should fit as a second part of my project. What's your opinion? Thanks for your insights, -- Regards, Wojtek Walczak, http://tosh.pl/gminick/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" 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/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
