Thanks to all for feedback and contributions. I should also note that Ian Bicking added some bits before most of you probably got there, so it's not all me.
On Nov 28, 4:28 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > One meta-issue is that the Pylons Cookbook space has become the > dumping ground for everything because it's the only space everybody > has guaranteed write access. There are topics such as this, improving > the Pylons core, etc, that aren't really Cookbook material. > > Likewise, the Pylons Community space has tutorials which arguably > *are* Cookbook material. It has never been made clear what the Pylons > Community space is for. Is it for marketing/branding/website topics? > Is it a miscellaneous space for community members to put anything in? I agree on all points. I think the need to get some of those things moved to the right places has been acknowledged, but the wider need for clarification is a good point. On Nov 28, 5:09 pm, Christoph Haas <[EMAIL PROTECTED]> wrote: > Web:http://workaround.org/pylons/beginning-pylons.html > Mercurial:http://workaround.org/cgi-bin/hg-beginning-pylons I found your cheatsheet when I first came to Pylons, and it's great. Hadn't seen this though, that's quite a comprehensive introductory article (or well on the way). Planning a little evangelism talk for the local user group soon, and you've covered most of what was in my initial outline. > (No, I wouldn't want to write it online in the wiki. A traditional text > editor and a good repository system is what I need to work. Confluence > just got me mad.) It might be for the good of all if we cooked up a little tool to submit your VC commits via XML-RPC. ;-) > The worst thing is planet.debian.org where fellow Debian > developers bore me to death and later claim that "the information > has been published" by blogging it there hidden underneath a pile > of soporific personal spam. Argh! Geez, that is bad. The usefulness does kind of depend on people being judicious about what they give the 'pylons' tag to, I guess... That was a sudden brainstorm, but I do think it would be cool as a resource *and* an example Pylons site in production, if hosting resources were made available from somewhere. Doesn't hurt that in feedparser Python has the best lib around for the purpose. -- Ches Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
