Wow,

That's about the most negative response I've seen in sometime.  Yes, I
could have held up the 2.1 release, I saw this happen back in the days
of 0.8/1.0 TG, and it ultimately hurt the community.  I would
encourage anyone seeing a hole in our documentation to please ask how
to contribute and I will be more than willing to send some info their
direction.  I did care that the docsprint got cancelled.  Yes, I would
like to see more people help with the work that has to be done.  Yes,
I plan to support TG for the coming future and I am not looking at a
merger as an absolute solution to our challenges.  We have a user-base
that provides 300 unique visitors to our documentation a day.  If 1%
helped out on that we'd have more than enough contribution to give the
docs the necessary love.  On the other hand, I understand the asking
folks to write documentation is nearly impossible, and I do what I can
with my free time to provide the software updates that are so required
to keep the framework modern.

cheers.
-chris


On Nov 21, 5:00 am, Christoph Zwerschke <[email protected]> wrote:
> Am 21.11.2010 05:37 schrieb Victor:
>  > Thanks, I thought this should be added to document, it would be help
>  > for people who encountered same issue. :)
>
> I think the same, and had hoped the docs would be brought in shape
> *before* the 2.1 release, but the planned doc sprint was cancelled and
> nobody cared. Our main developers don't have enough time and our users
> don't get involved, contribute or help out. Sadly, that's the state of
> Turbogears for some time already and we have to live with it or put our
> hope on the merge with Pyramid/Pylons.
>
> -- Christoph

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en.

Reply via email to