Here is my  $.02, as someone who reads the pylons, tg, pyjamas, webp2y lists.

As has been mentioned: a clear statement of intended direction, esp. with 
regards to pylons\pyramid, i.e. how tg fits in.

Documentation:

-          clear, up to date (i.e. remove obsolete stuff or move it somewhere 
where its clearly marked as old or put it in versioned 'directories' of some 
sort)

-          clear starting points, i.e. definitive quickstart tutorial, 
definitive how do I contribute/make changes doc

-          make it as easy to change or make comments on as possible. Pylons 
originally used Moin then is/was using confluence. I'm not sure what they found 
lacking in Moin, but the idea that things could be reviewed appeals to me. 
Confluence (which I'm lukewarm about) has the ability but it has never been 
used on the pylons site. Django had a good app (still do?) that allowed users 
to comment directly on the documentation when they were putting the book 
together. Very useful imho and allowed easy, easy commenting, which was 
reviewed and either accepted or not.

-          Just looked at http://pylonsproject.org/ (hadn't for awhile) and it 
looks polished but not very 'approachable', perhaps because major development 
is not apparent

A few comments on the landing page: http://turbogears.org/, maybe these have 
been made before?

-          Don't have all the initial links go offsite!

-          Instead, have links that go down a level in the docs, where more 
detail/info is presented.

-          As an example, the 'browser side' link goes to 
http://beta.toscawidgets.org/apache2-default/, where your presented with an 'It 
works' page. Wtf?! Very poor.

-          Why link to AJAX on wikipedia? Just encourages people to wander 
off...

-          keep people wanting to dig deeper

-          make the last 'points' on the page link to deeper explanations, i.e. 
- Real multi-database support, make it a link to a page that explains that 
feature and has links to relevant material (i.e. sqlalchemy)

-          'Support for a variety of JavaScript toolkits, and new widget system 
to make building ajax heavy apps easier'

o   This is the major draw, for me, to tg. Yet it still is not linked/explained 
as well as it could be

Finally, enough ranting on my part, as I'm not really answering your question: 
re What would it take? My direct answer to that is your doing the right thing. 
I was wandering away from tg, but have been encouraged by your, Michael's, 
efforts at shepherding tg (as well as the other 'regulars' on the ml, you know 
who you are).  I'm also encouraged and happy to see Alessandro on the ml, as 
all cooperation is beneficial.

Finally (for real), the docs are one thing but the ml (and irc, etc) are 
important. It is a community. Even though I am mostly an observer, I will say 
that it is an important community to me.

Cheers,
john

From: [email protected] [mailto:[email protected]] On 
Behalf Of Michael Pedersen
Sent: Monday, June 20, 2011 10:47 PM
To: tg-trunk; tg-trunk
Subject: [TurboGears] What Would It Take?

Some moons ago, I posted a question, but it deserves its own thread, and it's 
finally time to ask it:

What would it take for anybody reading this post to become a contributor to 
TurboGears? And I mean in any way. Writing docs, writing tests cases, posting 
bug reports, triaging bug reports, writing widgets, writing extensions, making 
any contribution, no matter how small, to improving TurboGears?

I want to know. I want to know if I can provide it. And, if I can, I will. I 
want to have the community more involved.

We've completed our infrastructure issues. We've gotten the next release out. 
It's time for us to reach out and try to pull the community back in.

So, what's holding you back?

--
Michael J. Pedersen
My IM IDs: Jabber/[email protected]<mailto:[email protected]>, 
AIM/pedermj022171
          Yahoo/pedermj2002, 
MSN/[email protected]<mailto:[email protected]>
My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen
Twitter: pedersentg
--
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.

-- 
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