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 <[email protected]> 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 [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.
>
>

-- 
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.

Reply via email to