Re: PGDN and CVS

Is this Framewerk the same as www.Framewerk.org?

> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org [mailto:pgsql-www-
> owner(at)postgresql(dot)org] On Behalf Of Josh Berkus
> Sent: Wednesday, September 21, 2005 9:15 PM
> To: Gevik babakhani
> Cc: pgsql-www(at)postgresql(dot)org; 'Magnus Hagander'; 'Dave Page'
> Subject: Re: [pgsql-www] PGDN and CVS
>
> Gevik,
>
> > I'm not discouraged in anyway... I have just been looking over and over
> > for a CMS that we could use in our project. Time after time I end up
> > with commercial products. And even if they are opensource, they need to
> > be so much customized that one has to put more time in customizing the
> > CMS framework rather than building the actual requirement.
>
> What is it you're trying to implement, exactly, that you don't find
> supported? Is it the tree structure?
>
> Even if existing CMSes require customization, I think it'd be better to
> work with that project and try to get them involved in the feature. As
> far as I know, the only CMS you've really tried is Drupal.
>
> Both Bricolage and Framewerk are intimate with the PostgreSQL community
> and
> could be counted on to work with you. I don't think you even looked at
> Bricolage after Marc set it up.
>
> I also don't think you've evaluated "more time to implement" using valid
> criteria. If you do a custom CMS, you're going to need to impement all of
> the common stuff yourself:
> Authentication
> User management (including "e-mail me my password, etc.")
> Approval/rights structures
> Versioning admin
> Editors (inc. wyswyg and/or bbcode edit)
> RSS
> etc.
> Did your really add up coding all of the above compared to customizing an
> existing system?
>
> Again, I'm not trying to discourage you, but from my perspective half a
> CMS
> is worse than none.
>
> --Josh
>
> --
> --Josh
>
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match