I tried to stay out of the discussion just to see what was the general opinion regarding the issue, and also because I promised my family that I would have spent the holidays without spending all my time on open source ;)
Regarding the documentation I think it greatly improved since it got refactored in 2.3, and recently I have been able to answer questions just by pointing people to the documentation more often. On the other side I'm aware that it incomplete, I'm the major contributor to documentation currently and so it highly reflects whatever I think it might be useful, for example as I never ever needed to use LDAP in my whole life I never thought about writing a documentation section. So I think it would greatly help to receive more specific feedbacks on what it is missing, they will help for sure to cover topics that me or other contributing people might have not thought about. On the community side I know a lot of people currently using TG day by day for their work, and I can say that since 2.3 visits to website and posts on the ML has been growing again, so I'm pretty confident that _there is a community_. On the other side I'm terribly aware that it is without any doubt a really passive community. I tried to improve things by writing documentation on how to write extensions: http://turbogears.readthedocs.org/en/latest/turbogears/Pluggable/index.html and by releasing tgext.pluggable with quickstart-plubbable, but it seems that it is not enough as practically all the extensions and pluggable apps in the past year have been all release by myself. I would really love to see a great reusable components ecosystem grow around TG and so I would love to hear what it is keeping people back from releasing extensions and pluggables. I think that technically speaking it is now fairly easy to roll them out. Just let me know what it is keeping you back and I'll try to fix it. On Mon, Jan 5, 2015 at 6:09 PM, lebouquetin <[email protected]> wrote: > Hi all, > > I worked with turbogears for years, starting in 2008. I always (and still) > feel TG2 is better than other frameworks because : > > - it is full-stack and authentication ready (similarly to django) > - it is based on existing solutions like babel, sqlalchemy, genshi / > mako... > > For a few month I face a growing frustration : > > - TG2 supports python3 but tgapplications do not > - I'd like to configure my urls like > (@route('/some/path/to/content/<id>') which is not available (except with > tgroute which duplicates standard routes) > > But the main frustration is from the following points: > > - do not find documentation about what I'd like to do (which is > possible) > - do not find any help about information I do not find in the > documentation. > > There are very few people reading the mailing list and I have several > questions with no reply at all. > > As I start again to work on professionnal projects using turbogears, I was > thinking about re-activating the community... but I can't help because I > stay myself without any answer. > > What about you ? Who is reading this ML ? Who is still working with TG ? > Is there any reason to still work with it (I know that Alessandro is doing > a great job, this is not my point, but using open source need a community > and I feel like there is no TG2 community anymore). > > > Damien > > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
