Re: Documentation overhaul specifics
Hi all, chipin is pretty easy to use, they don't take any fees: http://chipin.com/ I'd love to donate 50€. Cheers, Domen On Feb 13, 9:52 pm, Eric Rasmussen ericrasmus...@gmail.com wrote: I originally wrote the Akhet auth demo at a time when there weren't any examples showing how to integrate Pyramid's auth features with SQLAlchemy. It might still be useful in that sense, for people who need a quick start guide to get from the standalone examples (usually global lists or dictionaries of users/groups) to a working example with SQLAlchemy. Aside from that, I think Michael's demo (which I read and found quite helpful!) takes precedence as a learning tool. I could have sworn I had also found a demo of Michael's that used bcrypt for password hashing, and if the Akhet demo is going to include users/groups it should probably be updated to use bcrypt. I've started using it in my newest projects, but I can't seem to find the example at the moment. Thanks, Eric On Mon, Feb 13, 2012 at 12:30 PM, Michael Merickel mmeri...@gmail.comwrote: On Mon, Feb 13, 2012 at 2:06 PM, Mike Orr sluggos...@gmail.com wrote: On Mon, Feb 13, 2012 at 11:49 AM, Michael Merickel mmeri...@gmail.com wrote: Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. Where is this article publicized? I didn't know it or your website existed. It's not publicized other than some linking in IRC, the cookbook, and as part of my PloneConf talk. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Tue, 2012-02-14 at 10:19 -0800, Domen Kožar wrote: Hi all, chipin is pretty easy to use, they don't take any fees: http://chipin.com/ Sounds good. If it doesn't work out with Kickstarter, I'll try that. I'd love to donate 50€. Great, thank you! Cheers, Domen On Feb 13, 9:52 pm, Eric Rasmussen ericrasmus...@gmail.com wrote: I originally wrote the Akhet auth demo at a time when there weren't any examples showing how to integrate Pyramid's auth features with SQLAlchemy. It might still be useful in that sense, for people who need a quick start guide to get from the standalone examples (usually global lists or dictionaries of users/groups) to a working example with SQLAlchemy. Aside from that, I think Michael's demo (which I read and found quite helpful!) takes precedence as a learning tool. I could have sworn I had also found a demo of Michael's that used bcrypt for password hashing, and if the Akhet demo is going to include users/groups it should probably be updated to use bcrypt. I've started using it in my newest projects, but I can't seem to find the example at the moment. Thanks, Eric On Mon, Feb 13, 2012 at 12:30 PM, Michael Merickel mmeri...@gmail.comwrote: On Mon, Feb 13, 2012 at 2:06 PM, Mike Orr sluggos...@gmail.com wrote: On Mon, Feb 13, 2012 at 11:49 AM, Michael Merickel mmeri...@gmail.com wrote: Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. Where is this article publicized? I didn't know it or your website existed. It's not publicized other than some linking in IRC, the cookbook, and as part of my PloneConf talk. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Documentation overhaul specifics
Thanks to the amazing generosity of everyone here, it looks like we'll be a go for a Pyramid documentation overhaul project (see the need your help to overhaul docs thread for the genesis of this idea: http://groups.google.com/group/pylons-discuss/browse_thread/thread/7bd833209369bc5f ). We currently have a little over $3K in external pledges, and I have a pretty good feeling we'll get some more over the next few months. I still have yet to actually collect the pledged funds; I've applied for a Kickstarter.com project to do that, and I'm awaiting their response. Once I get it I'll likely be asking folks who pledged to put those pledges into that system. I have a really good feeling about what will come out of this effort, and I hope you do too. I've created a page at https://github.com/Pylons/pyramid/wiki/Documentationoverhaul describing what I'd personally like to see done during the effort. My suggestions are mostly about rearranging and prioritizing the content. Although I'd really like to see shorter docs, I didn't mention at all any removals of content because it's not terribly important to chop content unless it's in the context of something printed on paper. In a print version we can chop content very simply by not including the API reference (it's 200 pages long). We'll still want to tighten the wording and get rid of overlong descriptions, but omitting the API reference is both reasonable and easy for producing shorter printed versions of documentation. If you have further suggestions/concerns, please add them to the wiki (ideally with your name next to them so we can see who added them), or bring them up here. Thanks and congratulations for coming together as a community, - C -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Mon, Feb 13, 2012 at 4:59 AM, Chris McDonough chr...@plope.com wrote: Thanks to the amazing generosity of everyone here, it looks like we'll be a go for a Pyramid documentation overhaul project (see the need your help to overhaul docs thread for the genesis of this idea: http://groups.google.com/group/pylons-discuss/browse_thread/thread/7bd833209369bc5f). We currently have a little over $3K in external pledges, and I have a pretty good feeling we'll get some more over the next few months. I still have yet to actually collect the pledged funds; I've applied for a Kickstarter.com project to do that, and I'm awaiting their response. Once I get it I'll likely be asking folks who pledged to put those pledges into that system. There is also a new open source kickstart competitor, haven't used it though: https://www.crowdtilt.com/ I have a really good feeling about what will come out of this effort, and I hope you do too. I've created a page at https://github.com/Pylons/pyramid/wiki/Documentationoverhaul describing what I'd personally like to see done during the effort. My suggestions are mostly about rearranging and prioritizing the content. Although I'd really like to see shorter docs, I didn't mention at all any removals of content because it's not terribly important to chop content unless it's in the context of something printed on paper. In a print version we can chop content very simply by not including the API reference (it's 200 pages long). We'll still want to tighten the wording and get rid of overlong descriptions, but omitting the API reference is both reasonable and easy for producing shorter printed versions of documentation. I think that is actually better. I've seen countless times books getting negative reviews for duplicating the online API reference, and it just doesn't make sense to have that in book form really, it's a case where the hypertext part of the web is so much better. Great job on this initiative Chris! hard to believe that the docs will get even better ( I already think they're the best out there ) but I'm sure they will! Iain -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Mon, Feb 13, 2012 at 10:13 AM, Iain Duncan iainduncanli...@gmail.com wrote: On Mon, Feb 13, 2012 at 4:59 AM, Chris McDonough chr...@plope.com wrote: I think that is actually better. I've seen countless times books getting negative reviews for duplicating the online API reference, and it just doesn't make sense to have that in book form really, it's a case where the hypertext part of the web is so much better. There are people who prefer a printed manual, especially when reading offline or when their eyes are tired. And there are companies willing to pay money for such a book for their employees. If the organization is government, it can't donate money to a project but it can purchase a product at the prevailing price. I have the 5-volume PostgreSQL docs in book form, both because it made it easier to get my head around Postgres, and also because it's convenient to quickly look up a SQL command or program. In this age, you can even arrange for an on-demand publisher to print the current manual whenever a customer orders it. -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
Sorry to be late to the party, but I would like to pledge £50 (~$80 USD). In terms of concerns/suggestions, I'd particularly like the documentation relating to authentication and authorisation to be expanded - relying on it recently I felt that references to the Glossary from the tutorial didn't go far enough in explaining what is going on there. More examples would do a lot to give a better grounding in the subject. Thanks for coordinating this and for all the great work, Ben On 13 February 2012 12:59, Chris McDonough chr...@plope.com wrote: Thanks to the amazing generosity of everyone here, it looks like we'll be a go for a Pyramid documentation overhaul project (see the need your help to overhaul docs thread for the genesis of this idea: http://groups.google.com/group/pylons-discuss/browse_thread/thread/7bd833209369bc5f). We currently have a little over $3K in external pledges, and I have a pretty good feeling we'll get some more over the next few months. I still have yet to actually collect the pledged funds; I've applied for a Kickstarter.com project to do that, and I'm awaiting their response. Once I get it I'll likely be asking folks who pledged to put those pledges into that system. I have a really good feeling about what will come out of this effort, and I hope you do too. I've created a page at https://github.com/Pylons/pyramid/wiki/Documentationoverhaul describing what I'd personally like to see done during the effort. My suggestions are mostly about rearranging and prioritizing the content. Although I'd really like to see shorter docs, I didn't mention at all any removals of content because it's not terribly important to chop content unless it's in the context of something printed on paper. In a print version we can chop content very simply by not including the API reference (it's 200 pages long). We'll still want to tighten the wording and get rid of overlong descriptions, but omitting the API reference is both reasonable and easy for producing shorter printed versions of documentation. If you have further suggestions/concerns, please add them to the wiki (ideally with your name next to them so we can see who added them), or bring them up here. Thanks and congratulations for coming together as a community, - C -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Mon, Feb 13, 2012 at 1:23 PM, Benjamin Sims benjamins...@gmail.comwrote: Sorry to be late to the party, but I would like to pledge £50 (~$80 USD). In terms of concerns/suggestions, I'd particularly like the documentation relating to authentication and authorisation to be expanded - relying on it recently I felt that references to the Glossary from the tutorial didn't go far enough in explaining what is going on there. More examples would do a lot to give a better grounding in the subject. Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/ and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Mon, Feb 13, 2012 at 11:49 AM, Michael Merickel mmeri...@gmail.com wrote: Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/ and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. Where is this article publicized? I didn't know it or your website existed. We needed a supplemental explanation of auth for the Akhet manual, so Eric Rasmussen wrote one, although it's probably less extensive than this. The chapter is here, BTW, although it's about to go offline when I release Akhet 2, and it may reappear later in the Pyramid Cookbook. http://docs.pylonsproject.org/projects/akhet/en/v1.0.2/auth.html -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
On Mon, Feb 13, 2012 at 2:06 PM, Mike Orr sluggos...@gmail.com wrote: On Mon, Feb 13, 2012 at 11:49 AM, Michael Merickel mmeri...@gmail.com wrote: Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/ and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. Where is this article publicized? I didn't know it or your website existed. It's not publicized other than some linking in IRC, the cookbook, and as part of my PloneConf talk. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Documentation overhaul specifics
I originally wrote the Akhet auth demo at a time when there weren't any examples showing how to integrate Pyramid's auth features with SQLAlchemy. It might still be useful in that sense, for people who need a quick start guide to get from the standalone examples (usually global lists or dictionaries of users/groups) to a working example with SQLAlchemy. Aside from that, I think Michael's demo (which I read and found quite helpful!) takes precedence as a learning tool. I could have sworn I had also found a demo of Michael's that used bcrypt for password hashing, and if the Akhet demo is going to include users/groups it should probably be updated to use bcrypt. I've started using it in my newest projects, but I can't seem to find the example at the moment. Thanks, Eric On Mon, Feb 13, 2012 at 12:30 PM, Michael Merickel mmeri...@gmail.comwrote: On Mon, Feb 13, 2012 at 2:06 PM, Mike Orr sluggos...@gmail.com wrote: On Mon, Feb 13, 2012 at 11:49 AM, Michael Merickel mmeri...@gmail.com wrote: Out of curiosity have you read http://michael.merickel.org/projects/pyramid_auth_demo/ and did it help at all? It was originally written as an auth tutorial/demo separately, but I did have goals of incorporating its ideas into the docs somehow, but unfortunately I haven't gotten much feedback on whether it's actually useful for people or not. Where is this article publicized? I didn't know it or your website existed. It's not publicized other than some linking in IRC, the cookbook, and as part of my PloneConf talk. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
