Re: [opensc-devel] new release?
On 09/06/2012 08:06 PM, Viktor Tarasov wrote: > Hello, > > current github 'staging' is tagged as v0.13.0-pre1. > > If no objections, I will merge this branch into github 'master' -- it will be > base version to test > and to prepare the coming release candidate. Very good idea. I think it makes a lot of sense to have just one 'master' branch for development; this is what people coming over from other projects tend to expect. -- Kalev ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] new server hoster and adminstrator for opensc-project.org required
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
Re: [opensc-devel] new server hoster and adminstrator for opensc-project.org required
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
