On Fri, 2012-02-10 at 10:36 -0800, Iain Duncan wrote: > On Fri, Feb 10, 2012 at 10:26 AM, Chris McDonough <[email protected]> > wrote: > > On Fri, 2012-02-10 at 10:23 -0800, Iain Duncan wrote: > > The docs overhaul project isn't about a new website, > it's just > > about > > overhauling the existing narrative and API docs. > > > > Currently the Cookbook is where to put howtos (you > can fork it > > and add > > new howtos via > https://github.com/Pylons/pyramid_cookbook). > > You can > > create Pyramid extensions and publish them to PyPI > at your > > will. > > "Official" extensions (ones which have good docs and > good test > > coverage, > > and have been accepted into the project) are > collected at > > > > http://docs.pylonsproject.org/en/latest/docs/pyramid.html#pyramid-add-on-documentation > > > > > > > > Is there a guideline anywhere for those standards? I know > we'd have a > > lot of work to do to meet them, and whether or not it turned > out to be > > worth having something become an "official extension", it > would > > behoove us to get our grungy work up to that standard. > > > Yes, there is. Somewhere. ;-) I wrote it but now cannot > find it. > I'll try to find it later this evening and point at it. > > > > > > that would be great Chris, thanks.
http://docs.pylonsproject.org/en/latest/community/codestyle.html http://docs.pylonsproject.org/en/latest/community/addons-devenvs.html - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
