[Solar-talk] Tipos & Community SVN Repo

Antti Holvikari anttih at gmail.com
Thu Sep 21 23:24:25 PDT 2006


On 9/22/06, Rodrigo Moraes <rodrigo.moraes at gmail.com> wrote:
> On 9/21/06, Paul M Jones wrote:
> > Perhaps "Google Code" is a good tool for this?  I have "solarphp"
> > reserved as a project name with some placeholders there (even though
> > I don't think Solar proper is going to use it).  No wiki or other
> > stuff though, just the repository and some basic pages.  Google
> > Groups could tie into it, though.
> >
> >    <http://code.google.com/p/solarphp/>
> >
> > Maybe solar-users or something would be a more appropriate name?
> >
> > Just a thought, it might not be well-suited for our purposes after all.
>
> I didn't knew about it and definitely like the idea. It's simple
> enough and could work: no server needed, no overhead, no setup time,
> and SVN is already tied to a google group :-). If we need more, we can
> setup some other tools in solarphp.org, and we can always move to
> somewhere else after some time (and if we have some time, hehe). What
> do you guys think?

I've tried google code too. One bad thing was that the svn was really
slow, I don't know if this has changed though (it's Google after all).
But I think I will give a +1 for it nevertheless because I like simple
solutions.

Should we register a new project there since "solarphp" sounds a bit
too official? Or just stick with that? "solar" seems free too if we
want official... :-)

Travis' svn dir structure seems the way it should be. But where should
we put the tests dir, own dir for every vendor? So I'd have:

/svn
    /halo
        /trunk (?)
            /Halo
        /tests (?)
            /Test

How do you see this?

-- 
Antti Holvikari <http://phphalo.com>


More information about the solar-talk mailing list