Patrick Hartling wrote: > Marcus Lindblom wrote: >> Should I post these as patches on pyopensg's trac, >> or should I get >> commit-privliges in the trunk_update branch (or a branch of that, if you >> feel safer that way)? > > It may be easier for you to post the patches. I don't know if PyOpenSG > repository can be accessed without having a local account on the > machine. If a local account is required, then I don't know how to set it > up to allow access in the manner that the OpenSG repository supports.
svn doesn't necessarily require that, but, yes, it depends on the config. > We are considering relocating PyOpenSG to Google Code, and that could > simplify matters such as these quite a lot. Google Code would work. I already have an account there since I've added a project for a Django-webapp I'm hacking on for my band. :) Cheers, /Marcus ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
