Yeah no offence taken, it's a fair question and luckily I already have the answer up my sleeve. My point was more that the OP needs to have an answer to why he's creating something new rather than re-using something already in existance. It's usually the first topic that comes up when people say "hey, check out my new CMS" and it's a fair question to ask. If there is a valid reason for creating from scratch, great.

Good luck open-sourcing your project, it's a cool thing to do. The main reason we did this with Jojo CMS was to avoid being labelled as proprietary. Personally I hate vendor lock in, and customers should be able to choose a new provider if they happen to get slack service, or requirements change, or they move country or whatever - without having to throw away the $xxxx they just spent on their website.

Cheers,

Harvey.

On 30/11/2010 10:07 a.m., Keri Henare wrote:
I wasn't taking a stab at JojoCMS or it's creators but merely pointing out that 
people in glass houses shouldn't throw stones.  Although I guess that Harvey 
was predicting replies rather than making a statement of his own.  Sorry if 
what I said came across a bit insulting.

Did "Drupal, Wordpress, Silverstripe" not all exist when JojoCMS was started?

As I briefly mentioned, we've been using out own CMS in house for a year now 
and the reason for creating it was because with the thousands of CMSes out 
there, nothing fulfilled our needs, not even close.  We recently showed the new 
version that we're working on at the last Auckland PHP Meetup. You will all be 
able to pass judgement on it mid-next year after we open source the next 
iteration (to be powered by Symfony2).

That said, we are utilising other technology rather than rolling everything 
ourselves. Tech includes Symfony, Doctrine and ExtJS. Writing your own ORM, 
Framework and CMS all from scratch would be rather silly.

Kind regards,
Keri Henare
---------------------------------------------------

--
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]

Reply via email to