On Sun, Jan 30, 2011 at 8:58 AM, bvdb <[email protected]> wrote: > Ok, I am one of those, and started this thread from a superficial > position of someone switching over to Python/TG from another platfrom > and following just the "Build app in minutes" claim. > So I do not have the knowledge and experience and not the time to > achieve them to be able to contribute, and there will be more people > with a similar situation out there. > In return I'd advise the TG team to focus on the ressources they have > and rather cut down the ambitions a bit (or two).
We don't expect everybody to contribute. That will not work. But we do ask that, if you can, you contribute. We're going to need to help people figure out where and how to do so (and I've just added that as a line item on my to do list. As for toning down ambitions, I can only say this: No way. If I'm going to dream, I'm going to dream big. I've got tons of ideas on what to do. However, the first thing to do is to iron out the infrastructure changes. Switching servers, switching hosting platforms, switching trackers, vcs... the list goes on and on. I'm just hoping we can complete the move, and have all the details cleaned up, within a month. > Regarding the 2.1 issues, the bottleneck might not be to add some > explanations here and polish the layout there. The problem that > occured with deployment looks more like an unclear responsibility, so > maybe a _decision_ has to be made what's important and what not, in > order to simplify not only the docs but parts of the framework. And > for a decision there has to be someone in charge. Actually, I used those same docs to do my own deployment using Apache and mod_wsgi. In fact, I wound up doing it multiple times: Once to my private testing server, once to a public deployment, and twice at my previous job (testing and production). I even had to figure out why FreeBSD wasn't compiling things properly for (blasted python threads on FBSD are a pain). So, the docs are sufficient to do it. The fact that it wasn't easy was known, though I never updated those docs as there were hints of others working on them. My new attitude about such hints is going to change to "I have an answer? Good. I'm getting it out there for people to see. If somebody has a better one, then they can get it to me and I'll replace mine with theirs. But I'm not letting a vaporware answer hold me back anymore." > Talking about popularity, there is no "community" tab on the TG > homepage, and there seem to be no forums or blogs about it, or none > the TG team cares about. > There's only "About.. Documentation Install Development News" - so the > message is somehow "Take it and don't bother us with your questions". My blog has fallen into a bit of disrepair lately. I'm going to be fixing that starting this week sometime. http://planet.turbogears.org/ shows a bunch of the options, and I'm planning on finding a way to incorporate that into the sf.net setup, somehow. We are going to be making the new setup a lot more lively, and make us more able to take feedback from the community. > Maybe the TG team does not want that? > Or where's an invitation like "Tell us your success story with > TurboGears here (form-link)" or "Become an official sponsor, contact > [email protected] for details"? I'd love to have full corporate backing, I really would. But I'm not sure of the best way to go about that. It's also a very very low priority item, what with everything else that needs to be done first. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- 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.
