Re: [opensc-devel] How to deal with the gerrit backlog in an effective way?
Peter. If you were a book editor waiting for a perfect book, you could be waiting for ages and as a result would NOT edit ANY book. This is what is happening to OpenSC, with dozens of patch waiting for the perfect developer. The perfect patch just does not exist. Quality is a continuous process of people working together and you have to let them the necessary freedom. As for my current work, I am setting-up an independent compilation farm. The first Debian packages are coming out in a few days: https://opensc.fr/jenkins/job/OpenSC-SM-Debian/ https://opensc.fr/jenkins/job/OpenSC-SM-Ubuntu-1/ https://opensc.fr/jenkins/job/OpenSC-SM-Ubuntu-2/ RPM distros are coming next. When this is done in around 1 week, we will call for clarification of the OpenSC project. This call for a clarification will allow us to discuss on release dates and the project goals. Don't think we are going to fork, this will not happen. > You clearly have no desire to work together with all members of the > community. You've decided that only your own philosophy is the > correct one, and you only want to work with those who follow you. > All this while not sending an overwhelming amount of perfect patches, > even for documentation, meaning that you have zero technical > credibility. You are not in any position to make demands. -- Jean-Michel Pouré - Gooze - http://www.gooze.eu smime.p7s Description: S/MIME cryptographic signature ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] How to deal with the gerrit backlog in an effective way?
Jean-Michel Pouré - GOOZE wrote: > ease the collaboration process quickly or the community will set-up > its own tools. Please stop blowing smoke. You want to fork so GO AND DO IT ALREADY! You clearly have no desire to work together with all members of the community. You've decided that only your own philosophy is the correct one, and you only want to work with those who follow you. All this while not sending an overwhelming amount of perfect patches, even for documentation, meaning that you have zero technical credibility. You are not in any position to make demands. You do not want to work within the established opensc-project.org structure, even though it allows you and everyone else to work quite freely thanks to Martin's effort of setting up gerrit and jenkins. Please go do your thing, but you obviously need to use a different name for your project. //Peter pgpwUiC0bQdin.pgp Description: PGP signature ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] How to deal with the gerrit backlog in an effective way?
Dear Ludovic, > That may be the best solution: to restart from a synchronised state. > I hope Martin will have more free time in a few days to implement > that. As written several times before, we need more people with admin rights on OpenSC projects. There is no reason to limit to two people: Ludovic and Martin. What happens if one falls into cold water or does not show up as this happened before. OpenSC looks more and more like tokend or pcsc-lite: one admin and no collaboration. We are asking you to ease the collaboration process quickly or the community will set-up its own tools. We already have an independent build farm, this is a clear information that our next to-do on the list would be to wipe OpenSC project and open it to collaboration. -- Jean-Michel Pouré - Gooze - http://www.gooze.eu smime.p7s Description: S/MIME cryptographic signature ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] How to deal with the gerrit backlog in an effective way?
Le 4 avril 2012 09:49, Viktor Tarasov a écrit : > On Tue, Apr 3, 2012 at 8:36 AM, Ludovic Rousseau > wrote: >> >> Le 3 avril 2012 00:30, Viktor Tarasov a écrit : >> > Le 02/04/2012 10:01, Ludovic Rousseau a écrit : >> >> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE a >> >> écrit : >> I don't think there is. >> >>> Here is the address of the secure messaging branch: >> >>> https://github.com/viktorTarasov/OpenSC-SM/tree/secure-messaging >> >>> >> >>> We are using it, as it includes most fixes. >> >>> >> >>> Binaries are published in: >> >>> http://www.opensc-project.org/downloads/nightly/sm/ >> >>> >> >>> Why not use Opensc-SM for OpenSC developing branch? >> >> The solution is very simple. >> >> 1. rebase the SM branch over the OpenSC version in gerrit/staging >> >> 2. submit the changes to gerrit >> >> 3. review the changes on gerrit (they should be OK) >> >> 4. someone (Martin/Viktor/me) will accept the changes in gerrit and >> >> they will be merged >> >> >> >> You do not need extra power for that. It is just normal developer work. >> > >> > How the 'staging', that you are working on, is related to the 'staging' >> > branch of the OpenSC.git from github ? >> > Looking onto the git workflow >> > (https://www.opensc-project.org/opensc/wiki/DevelopmentPolicy) >> > I do not quite understand the place of 'staging' on the >> > opensc-project.org . >> >> The "official" repository should be on opensc-project.org. github >> should be a mirror. > > > > So, the presented schema of the git workflow is invalid, and you are going > to redesign it, isn't it? > > >> >> But gerrit was not working (or I did not know how to use it) so I >> merged pull request on github, that was a mistake. Then the two >> repositories diverged in incompatible ways. >> >> Maybe OpenSC on github should be deleted and recreated as a copy of >> opensc-project.org repository. > > > > Why to not do the same with the opensc-project.org repository and to > recreate it as a copy of github ? > This way looks more respective to the number of people who have forked the > github OpenSC.git project. > It's the opensc-project.org repository could be the mirror of the github's > one -- the main development base. That may be the best solution: to restart from a synchronised state. I hope Martin will have more free time in a few days to implement that. Bye, -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] How to deal with the gerrit backlog in an effective way?
On Tue, Apr 3, 2012 at 8:36 AM, Ludovic Rousseau wrote: > Le 3 avril 2012 00:30, Viktor Tarasov a écrit : > > Le 02/04/2012 10:01, Ludovic Rousseau a écrit : > >> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE a > écrit : > I don't think there is. > >>> Here is the address of the secure messaging branch: > >>> https://github.com/viktorTarasov/OpenSC-SM/tree/secure-messaging > >>> > >>> We are using it, as it includes most fixes. > >>> > >>> Binaries are published in: > >>> http://www.opensc-project.org/downloads/nightly/sm/ > >>> > >>> Why not use Opensc-SM for OpenSC developing branch? > >> The solution is very simple. > >> 1. rebase the SM branch over the OpenSC version in gerrit/staging > >> 2. submit the changes to gerrit > >> 3. review the changes on gerrit (they should be OK) > >> 4. someone (Martin/Viktor/me) will accept the changes in gerrit and > >> they will be merged > >> > >> You do not need extra power for that. It is just normal developer work. > > > > How the 'staging', that you are working on, is related to the 'staging' > branch of the OpenSC.git from github ? > > Looking onto the git workflow ( > https://www.opensc-project.org/opensc/wiki/DevelopmentPolicy) > > I do not quite understand the place of 'staging' on the > opensc-project.org . > > The "official" repository should be on opensc-project.org. github > should be a mirror. > So, the presented schema of the git workflow is invalid, and you are going to redesign it, isn't it? > But gerrit was not working (or I did not know how to use it) so I > merged pull request on github, that was a mistake. Then the two > repositories diverged in incompatible ways. > > Maybe OpenSC on github should be deleted and recreated as a copy of > opensc-project.org repository. Why to not do the same with the opensc-project.org repository and to recreate it as a copy of github ? This way looks more respective to the number of people who have forked the github OpenSC.git project. It's the opensc-project.org repository could be the mirror of the github's one -- the main development base. > Or maybe we can achieve the same result > in a soft way and make the 2 repos to converge again. > Maybe. If someone will have the time and motivation. > Bye > Kind regards, Viktor. > > -- > Dr. Ludovic Rousseau > ___ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel > ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
