Re: [PHPiCalendar-DEV] Rebooting phpiCalendar

[Rich B. <rb...@rc...>]

On Dec 3, 2010, at 4:40 PM, Jason Oster wrote:

> TL;DR:
>
> 1) Scrap phpiCalendar 2.x.
> 2) Pick up work on phpiCalendar 3.x. (Follow coding and style  
> conventions!)
> 3) Move the code to Git or Mercurial.
> 4) Move the issue tracker to Trac.
> 5) Reimplement the user interface in CSS3 using a simple template  
> engine
> like phpSavant.

+1 to the concept, certainly.

I'm not great fan of Mercurial or Git. Of the two, I think that Git is  
a wiser choice, in that you won't be excluding quite as many people  
due to SCM-ignorance. However, I think that svn is a wiser move, in  
terms of learning curve. Of course, I suppose that's wholly a matter  
of preference.

The more modular and OO the code can become, the easier it is for  
someone to plug into the development effort without having to  
understand every other part perfectly, but learn it over time.

--
Rich Bowen
rb...@rc...