I'll throw in my proof-reading offer as well, send it my way and I'll run
through it as soon as possible. But I am just getting started with Pylons
and don't have the experience to tackle writing either of these docs,
unfortunately.

On Wed, May 19, 2010 at 7:55 AM, Mike Burrows <[email protected]> wrote:

>
> Hi Ben (and all),
>
> I don't think I can help write either of the docs mentioned but I too
> would be very happy to do some proofreading.  When you're ready, drop
> me an email or a tweet (I'm @asplake) and I should be able to turn it
> around in a day or two.  I have also fixed a few issues with tests
> under Windows; if anyone needs tests run there, give me a shout.
>
> Would it be premature to discuss what comes afterwards?  Validation
> must come high on the list, and my guess is that the work involved
> will be not so much about Pylons code - that will be the easy bit once
> we're happy with patterns to recommend for application code (I
> hesitate to limit it to just controller code).  JSON and AJAX fit in
> there somewhere too.
>
> Anything else in the pipeline to look forward to?
>
> But while I'm here, let me say thank you!  Though a risk, going for
> Pylons well before 1.0 has definitely been a good decision; now
> looking forward to it hitting that milestone.
>
> Mike
>
>
> On May 19, 2:59 am, Ben Bangert <[email protected]> wrote:
> > You, (Yes, You!), can help get Pylons 1.0 out the door sooner. So what's
> holding up the release at this point?
> >
> > Two documentation tickets:
> http://pylonshq.com/project/pylonshq/query?status=assigned&status=new...
> >
> > I put in a summary of what should be in them, and I'd be happy to help
> with proof reading, etc. for anyone that wants to take a crack at these two.
> >
> > At this point, Pylons 1.0 and 0.10 are stable and I think WebHelpers is
> close to being ready for a 1.0 release as well. While there's some minor
> tickets in Beaker/Routes, I don't see anything that warrants holding back a
> Pylons 1.0 release.
> >
> > How to Help
> > ==========
> >
> > To work on these tickets, please indicate that on the ticket, and assign
> it to yourself, then:
> > 1) Fork the project on Bitbucket:http://bitbucket.org/bbangert/pylons/
> > 2) Check out your fork
> > 3) Apply your fixes to the documentation, and push your changes back
> > 4) Send a pull request on BitBucket
> >
> > Other ways to help (fixes should be done the same as above):
> > - Proof-read the existing documentation
> > - Test the documentation against Pylons 1.0 to ensure it actually works
> (Installing Pylons 1.0:
> http://pylonshq.com/docs/en/1.0/gettingstarted/#installing)
> > - Ensure the QuickWiki works against Pylons 1.0 (I believe Graham has
> updated the code for it recently, it'd be great to have some ppl test it)
> >
> > Also, I know some people have asked and are curious about what future
> changes are planned for Pylons post-1.0, so I'll be writing up a blog post
> in the next few days outlining a rough future roadmap for where Pylons is
> going, and what new features are planned.
> >
> > Cheers,
> > Ben Bangert
> >
> > --
> > 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]<pylons-discuss%[email protected]>
> .
> > For more options, visit this group athttp://
> 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]<pylons-discuss%[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