Andreas Jellinghaus wrote: > A small follow up: As far as I know the server does: > * svn server / code repository > * svn server / release tar.gz repository (also containing binaries) > * build robot to create nightly builds and or automated builds (jenkins?) > * many trac repositories - wiki, browser for svn, bug tracking (the bugs > are not very helpful if noone works on them) > * mailing lists > > So I don't know if all svn code repositories have been migrated to githup > etc. > I have little knowledge what plattform would be best to fill the gaps so > that we can shut down the server.
If source code repos haven't been converted to git I suggest to do so right away. Release tarballs can and should be hosted separately from source repos. I suggest that they are only ever uploaded manually. (Makefile) A build robot can and should be hosted separately from source repos. Trac integrates with git, it's not stellar in any way, but it works. Modern Trac versions support multiple repos. I would suggest to merge the different Trac instances into a single one. This will take manual labor, messing around with the Trac databases. Mailing lists aren't very fun to self-host IMO, but can certainly be done. I run integrated Trac and git hosting for several projects for years, I'm happy to do so also for the opensc projects, in particular the small ones. //Peter _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
