On 8/30/06, Eric Radman <theman@...> wrote:
> On 21:25 Wed 30 Aug , ke han wrote:
> > On Aug 30, 2006, at 7:58 PM, Claes Wikstr?m wrote:
> > > Yariv Sadan wrote:
> > >> Claes,
> > >>
> > >> I heard that many developers have moved their projects from
> > >> sourceforge to code.google.com. The Google offering is much cleaner
> > >> and nicer and they support SVN. They will also add more features over
> > >> time.
> > >>
> > >> I'm just giving you a heads up in case you're looking for a SF
> > >> alternative :)
> > >
> > >
> > > Hmm, what's the phrase ... "If it works - don't fix it"
> > I think the trouble is it "works for you" and maybe a few others.
> > But since svn is now mainstream and sourceforge has only made modest
> > advances in recent years, I would venture that something as small as
> > changing to a more "accessible" online project tool, may increase
> > contribution to yaws.
> Subversion is only "more accessible" for Windows users. On older systems
> Subversion is monster because it has SO MANY dependencies:
Is this a problem for anyone's workstation? Also, if you're compiling
it, most of those dependencies are included in the source tarball.
> I also doubt that meaningful contributions are going to come from people
> who think CVS is difficult.
The issue isn't so much that CVS is difficult, but old and annoying.
CVS and sourceforge's reliability are definitely reasons why I have
not contributed any patches to yaws yet. Instead, I've simply worked
around Yaws problems, because I didn't want to deal with sourceforge.