I have a working copy of TG 1.0.1 API at http://tg.maetico.com/api/,
it's been there for a while but the URL was not public, we can use
that as a reference until we get the proper one set on the TG server.
I have just one request, don't kill my bandwidth.


new people
- be patient, as Mark has reported on the docs list yesterday we had
160 edits on the last docsprint, things are moving and fast.
- contribute with comments
- go to the docs list ([email protected]) and say I
want <list of items> I promise I'll ban everyone that makes fun of
you. (not sure if I can ban myself but I'll have someone to do it if
it's me)
- if you do the above please be specific the more the better, things
like "there is no docs on foo" or "foo's docs suck" are not useful,
they are just a waste of our (yours and mine) time.
- write something even if it's crap, crap is better then nothing.
After this one of two things will happen someone is going to a) say
"this is crap" and fix it b) say "OMG! this is the worst doc I have
ever seen" and start from scratch. Machiavelli at it's best.
- check out http://docs.turbogears.org/1.0/RoughDocs/DocumentationWishList
some stuff there demands no knowledge of TG for example  some is
already written (in the trac tickets) all it needs is someone with a
little time and some ReST, if your not sure about something read the
above.

old people
- don't be lazy lets have a big push so we can go on.
- if you wrote some code please sit down and try to write a tutorial
of how to use it, add docstrings or make them better, write tests
(those are great for showing how to call it)
- lets review what we have and write stuff for the most complex components.
- find the proper docs on other projects and link to them.
- lets listen to the new people some things that are obvious to us
(for example SQLObject) are not for new people
- remember the time you got lost inside a TG project, or when you had
no idea what CherryPy or kid was for, before replying to a post.
- lets write more tutorials,like turbotunes and wiki20. In the past
they where very good at solving many questions.

both
- stop posting stuff to this list about docs, it just makes everyone
spend more time here, and get people to argue that is not good.
- lets stop looking for someone to do it and do it.
- we got over 2500+ people on this list and I'm sure many are no
longer using TG, at least half don't read it and even less actually
post but we the ones that try to get this to "0 unread posts", need to
show all of them that this issue is going to resolved for ones and for
all. (read until 1.1 is released)
- look for stuff, there is more out there then what you think, we got
some gems still stuck on trac, there has been excellent blog post that
are lost in messy archives (read wordpress), and some docstrings have
full explanations if each and every detail if you don't believe me go
look at 
http://trac.turbogears.org/browser/tags/1.0.1/turbogears/widgets/base.py#L77
that's almost a 100lines docstring)

I really want TG fully supporting genshi, CP3, SQLAlchemy, and TW and
I want Catwalk or fastdata or whatever to be finally done, I want to
build all kinds of interesting stuff on top of TG. but we can't go
into all that if this minor issue is not finish, yes I said minor
because the hardest part is making it.

This is no longer Kevin's baby it's ours and it will end where we want it to be!

I just counted 47 projects on the cogbin I remember the time when I
have try them all now I can't recognize half the names in there, and
that is just the ones correctly label in pypi and are publicly
released. That to me is enough reason to say people think TG rocks.

Now come on lets stop wasting time here and using it at docs.turbogears.org ok?

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