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. What I can do is make all configurations available to whoever wants to setup a new server, or help with migrating to whatever plattform. If I had to pick one, I would try code.google.com (as I work for google now), but not having much clue what plattform has what features I can be persuaded to any plattform I guess. As people mostly focused on opensc, I would be happy if the other small projects do not get lost / don't get a second class treatment. Those should be very easy to migrate as they are tiny (e.g. libp11 and pam_p11, pam_pkcs11, engine_pkcs11) and I know for sure there are many users of those code parts around that need them (e.g. many people using TPM also use engine_pkcs11 and thus libp11 and also use pkcs11-tool from opensc for testing the TPM pkcs11 module). I don't want to be the one deciding where to go, as I find little time for OpenSC these days (maybe "none" would be more correct). Thus I think you guys should find a compromise on the options people are offering here. Thanks and regards, Andreas
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
