Marcus von Appen wrote:
After discussing certain things with Julian, something like this might
make the most sense:
SVN hosting on google.
Trac (which I'd prefer over google's homebrewn software) on
dev.pygame.org.
Why that? First of all, one of the website requirements is to have a bug
tracker and wiki integrated instead of having anything hosted on
different domains as it is at the moment.
dev.pygame.org could act as central platform for pygame-related
development. Users can keep track of pygame projects, which are in a
planning and early development state and the trac system running there
can act as routing station to the different SVN repositories hosted
elsewhere (google, pygame, ...).
In the long term, this also allows us to have a development wiki and bug
tracking already around and the only thing left to do would be to
integrate them seamlessly into the final pygame.org website.
For the current time, we could redirect dev.pygame.org to Julian's
webserver, then, once trac is up and running on pygame.org (which should
be relatively easy to be realised), let it point to the local trac. That
way we have no dead URL mess and people do not need to visit various
sites (and create different accounts) just to file bugs for (either)
pygame project.
We also do not have the data scattered ony google's wiki, pygame.org and
wherever else.
Keeping the web site development on a separate site, google, seem
appropriate for now. I have just been looking again at Trac and at first it
looks like a good choice. The wiki has a clean markup that accepts Python
code without mangling it. But I have two questions. One, how easy will it be
to import the existing Pygame wiki pages into Trac? Two, can we really use
the Trac with the Web SVN and Pygame SVN? (*)
Lenard
(*) I believe no to the first, yes to the second
(http://trac.edgewall.org/wiki/TracInstall#OptionalRequirements).