Hi all, I would be glad to contribute typo and spelling fixes to the new pylons docs at docs.pylonshq.com. I have been reading through them and I have such volume of small fixes to offer that it would not be most efficient to package them up in email, have someone else read through the correspondence, and so on. So I'm thinking I could help out more directly.
Is it possible for me to acquire access to editing the docs, given the following proposed understanding? I would make no changes that significantly alter meaning; would not mess with original intent and would ask before altering anything that seemed to border on doing so; and would in general fix only obvious errors -- typically limited to spelling, grammar, readability issues and typos. I was blessed (read: cursed) with an eagle eye for typos, and frequently find them in late editions of books and other first class publications. For some reason this does not apply as perfectly to my own code as it does to reading others' writings, but I suppose that is to be expected. I would enjoy putting this ability to work for the betterment of Pylons. I am continuously impressed with the project and wish to contribute, but my Python hacking is not yet what I consider up to production level, so I would love to buff out the docs as an alternative to working on code. I can't promise a ton of hours, but as long as I'm reading them through 100%, I might as well fix the numerous blips I'm coming across. As far as my credibility and level of understanding: I have been working on a sizable web application built on Pylons/SA/Mako for a year now. (Why so long, what's wrong with my project? I have to tackle it in my spare time, after a full time non-tech job.) I am familiar with the major sources of reference material related to Python, sqlalchemy, HTML, CSS, Mako, Javascript, etc., and have in the past two months of trying 0.9.7 dug much deeper into Pylons to understand the guts of the system. Thus I have developed a reasonably good sense of what does what and what goes where. Still, to reiterate what I stated above, it would be better to begin by contributing simple grammar/spelling/typo fixes. As for "can I back this up, am I serious" and so forth, I have watched my available time for development work over the past two months and it is clear that I will have at least a small time slice per week for reviewing Pylons-related documents for the foreseeable future. Sometimes this will temporarily not be the case, but over time it should average out to a level of commitment that is reasonable, relatively low and therefore absolutely achievable. Respectfully yours, "grault" --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
