And what would you have your army do?  I'm not entirely sure how much
time i'll have this week, nor how useful I can be, but I'm willing to
contribute... heh.

On Sep 21, 7:40 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
> I have been out of touch most of last week, but I agree that having
> some better state-of-the-union docs would be good.   I also agree that
> Authorization needs some documentation love, and I'll try to get
> started on both of those things this week.
>
> But I also really want to get another beta out the door this week, so
> any help from the TG2 army would be much appreciated :)
>
> --Mark
>
>
>
> On Sat, Sep 13, 2008 at 11:16 PM, iain duncan <[EMAIL PROTECTED]> wrote:
>
> > Hey folks, first off I want to make it clear that I'm not whining. I am
> > totally in favour of taking the time to get the best foundational layers
> > possible for TG2.
>
> > That said, I'm terribly confused about the state of certain components,
> > the main one being auth&auth. I realize this is under hyperactive
> > development, but at the same time, I want to start learning what I need
> > to know to do it right for TG2 projects. So could anyone tell me what I
> > should be looking at for learning that stuff? Do I just dig in to repoze
> > docs or is the api used in tg still unsettled?
>
> > Secondly, maybe a good addition to the TG2 docs would be a "state of the
> > nation" page for the various components? Maybe a list of what's being
> > used for what and where that is at for development?
>
> > Thanks!
> > Iain
>
> --
> Mark Ramm-Christensen
> email: mark at compoundthinking dot com
> blog:www.compoundthinking.com/blog
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to