On Mon, Mar 23, 2009 at 7:35 AM, [email protected] <[email protected]> wrote:
>
> Hello,
>
> I'm interested in a TurboGears CMS development for this GSOC.
>
> Idea mentions the CMS itself and the library of CMS components which
> should be extensible outside the CMS framework.
>
> I see it as some minimal core application (cms), to which components
> are plugged in. In the best case everything should be a pluggable
> component.
>

right, your suggestion seems a lot like what we are aiming for with
pages and so far we got 4 commiters (all of us are tg commiters too)
so yes you are welcome to join.

> I gave a look at tg-registration [1] package, which works only with
> TurboGears 1.0 branch. So I have a question, which version should
> support the application? 1.0, 2.0 or both?
>
this is also on our TODO list, tgext.registration and tgext.profile,
in general we (everyone in TG) is doing either a rewrite  or a non
compatible upgrade of tg1 apps. Doing it both tg1 and tg2 compatible
is doable (I have done two experiments on this and they work really
nice)but I don't think it's worth the troubles to maintain long term.

> In the beginning I would port tg-registration to get knowledge and
> understanding, how components are working. Is it good starting point?
>
well keep in mind the whole concept of a "component" is a TG2.1 goal
so you will actually be making policy rather than learning how it's
don. That in itself is the other goal of pages (goal 1, a cms that
doesn't sucks, goal 2 learn how to write a "plugable app"

> [1] http://patrickhlewis.googlepages.com/registration.html
>
> --
> Dmitrijs Milajevs
>
>
> >
>

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