Hi, The gsoc works are going to fork a branch for refactoring the current implementation...
There are 2 ways to deal with php-cvs in my mind... 1) After refactoring, submit to php-cvs 2) Fork a branch on php-cvs, do the refactoring directly with the php-cvs branch For me, both are fine for my works ^^" If 1) is preferred as php practice, then please ignore this cvs request =] ks. On Wed, Apr 29, 2009 at 6:50 PM, Hannes Magnusson < hannes.magnus...@gmail.com> wrote: > On Wed, Apr 29, 2009 at 05:56, yannick <yannick.tor...@keliglia.com> > wrote: > > +1 > > > > Welcome Ks on this great project ! > > > > Someone can give him doc-editor karma ? > > We usually require some work beforehand, a patch here and there or > otherwise substantial contributions. > It is even more important for the GSoC students to follow this rule so > they get an overall feeling on how things work (which is the whole > point). > > -Hannes > -- I, have a dream. I want to make my dream come true. Anyway, OLPC Rocks! http://mr.kschan.googlepages.com
