On Tue, Jun 23, 2009 at 10:10 AM, Iain Duncan<iaindun...@telus.net> wrote: > > On Tue, 2009-06-23 at 06:25 -0700, Mike Orr wrote: >> >> Perhaps we could have an IRC documentation party this Saturday and go >> over how the documentation is structured and make some decisions on >> how the subprojects should integrate with the Pylons site and a common >> format for them so they're not all going off in different directions >> depending on who's writing them. > > That sounds promising. Do you want user feedback on the docs/examples?
Well, mostly I need Ben's feedback on where things should go and how it's structured. As for patches, I'm not sure that's the bottleneck. There's little to do in the Pylons core, so what would all these patches cover? Maybe they'd be rejected as bloat or not the way the developers want to implement things. And anybody can make a public fork of a BitBucket repository and implement their changes there, and then petition Ben to pull the changes. That also allows others to install the alternate Pylons version if they want to. > Is it possible to remove the website dependency on Ben only? Philip can also make changes on the website. > Given that the source for the PylonsHQ website itself is on bitbucket: > http://bitbucket.org/bbangert/kai Well, yes it's there, but what do you do with it? What are the standards for third -party docs such as Routes and WebHelpers that need to be both standalone, on their own website, and integrated with the Pylons docs? What are the markup codes he's using for variable names and such? -- Mike Orr <sluggos...@gmail.com> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
