Hi, that sounds great!
Do you plan to use the wiki for documentation and examples as well? And will this move also replace the current use of Launchpad? I suppose this will require something to keep the contributor access. Should be straightforward enough though. Best regards, Niklas (Btw, I've had too little time for participation for a while now, but I plan to change that. I want to look more at the planned package split and try out Chimezies (excellent) SPARQL-work, for instance..) On 11/13/07, Daniel Krech <[EMAIL PROTECTED]> wrote: > Hi all, > > I'd like to cut over to using code.google for the rdflib project > infrastructure. We've talked about this off and on for a while now on irc > and people seems to be for it. While there have been some advantages of > putting together our own project infrastructure I think we've been paying > the price by not having it up to par (others have brought this up in the > past too). And that we'd be better off focusing our bandwidth into the > project proper instead of into custom infrastructure for the project. We can > still do some additional bits on rdflib.net, but for the basic project > infrastructure bits let's leverage code.google. > > So, I'd like to start by checking to see if anyone has strong objects or > reasons why they think this might not be a step forward. And would like to > do the svnsync tomorrow if people are not in the middle of any changes? I'll > also plan on updating rdflib.net to point to all the relevant bits > on http://code.google.com/p/rdflib/ for svn, issues, etc. > > Cheers, > Daniel Krech, http://eikeon.com/ > > > > > _______________________________________________ > Dev mailing list > Dev@rdflib.net > http://rdflib.net/mailman/listinfo/dev > > _______________________________________________ Dev mailing list Dev@rdflib.net http://rdflib.net/mailman/listinfo/dev
