Re: [opensc-devel] OpenSC and gerrit
Alon Bar-Lev wrote: > I think you are trying to make opensc something it is not. I am not trying to do a single thing beyond pointing out that there is alot of complaints and wasted time over no *actual* problem. > The bureaucracy and lack of flexibility will inhibit contributions > and healthy *SMALL* community. What bureaucracy do you mean? Requiring no build failure and review in gerrit? I think those are acceptable requirements. They're also not exactly unique for OpenSC. What lack of flexibility do you mean? Anyone in the whole world can clone the gerrit repo, make changes, and push them back to gerrit for review. > That's true that it may eventually lead to more stable > implementation, but the cost may be lack of progress, > thus not able to achieve the stability goal as well. Quantity is IMO completely irrelevant without quality. > Until now I did not notice gerrit to be so good solution > that all other methods should be dropped for of it. I'm afraid I don't understand what exactly you mean by this. Gerrit helps track patches. I'm not sure that the current configuration is completely ideal, but it is also not in any way causing a critical problem for further development. > However, a proper build server with multiple platforms and > configurations is something that is vary useful to have in > order to test branches before merging. Of course there is no replacement for testing, but I really can not agree if you are arguing that being unable to extend jenkins is a critical problem for further development. > I quite miss the previous method in which people could work on this > project progressing (and may do mistakes), but invest their time in > proactive way. What is stopping that? Please be specific. > I don't think that in current process I [or anyone similar] could have > contributed whatever I've done before, so I don't think it is going to > a good place. Why not? Please be specific. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Hello Peter, I wrote this before, but I think I need to write again... I think you are trying to make opensc something it is not. The bureaucracy and lack of flexibility will inhibit contributions and healthy *SMALL* community. That's true that it may eventually lead to more stable implementation, but the cost may be lack of progress, thus not able to achieve the stability goal as well. Until now I did not notice gerrit to be so good solution that all other methods should be dropped for of it. However, a proper build server with multiple platforms and configurations is something that is vary useful to have in order to test branches before merging. I quite miss the previous method in which people could work on this project progressing (and may do mistakes), but invest their time in proactive way. I don't think that in current process I [or anyone similar] could have contributed whatever I've done before, so I don't think it is going to a good place. Alon. On Sun, Mar 18, 2012 at 1:39 AM, Peter Stuge wrote: > Viktor Tarasov wrote: >> > What is it that does not currently work and which is >> > critical for developing perfect commits? > .. >> - replication in gerrit > > If you mean the mirroring of commits to github.com I don't see how > that is critical. Work with the repo in gerrit instead. Many projects > have no other. > > >> Should we manually push the perfect commits from gerrit's repo to >> staging? > > Define staging? It's not at all clear which repository you refer to. > The staging branch in gerrit's repo gets updated when changes are > submitted in gerrit. > > >> - nobody from the active persons has an admin access to jenkins -- >> no possibility to extend the current jobs, create the new ones >> and to build linux packages in continuous manner. > > I also don't see how jenkins is critical. > > > //Peter > ___ > 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
Re: [opensc-devel] OpenSC and gerrit
Viktor Tarasov wrote: > > What is it that does not currently work and which is > > critical for developing perfect commits? .. > - replication in gerrit If you mean the mirroring of commits to github.com I don't see how that is critical. Work with the repo in gerrit instead. Many projects have no other. > Should we manually push the perfect commits from gerrit's repo to > staging? Define staging? It's not at all clear which repository you refer to. The staging branch in gerrit's repo gets updated when changes are submitted in gerrit. > - nobody from the active persons has an admin access to jenkins -- > no possibility to extend the current jobs, create the new ones > and to build linux packages in continuous manner. I also don't see how jenkins is critical. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Le 17/03/2012 22:32, Peter Stuge a écrit : > Viktor Tarasov wrote: >> Could you explain here how can we 'move forward', preferably >> without appealing to the absent persons and to the non-working >> services? > No, a "move forward" idea is broken from the start. > > Be specific. What is it that does not currently work and which is > critical for developing perfect commits? I posit nothing. Probably you have not read my mail. - replication in gerrit do not working. Should we manually push the perfect commits from gerrit's repo to staging? (In the github's pull requests the commits are also perfects, almost perfect.) - nobody from the active persons has an admin access to jenkins -- no possibility to extend the current jobs, create the new ones and to build linux packages in continuous manner. For these two points there is no visibility on when they could be resolved. This situation is lasting for months. Personally I would prefer to develop the OpenSC's card middleware, but in the current situation do not see the possibility. That's why I'm spending my time to get knowledge of jenkins and gerrit and to install an alternative way of 'moving forward'. > //Peter Kind regards, Viktor. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Viktor Tarasov wrote: > Could you explain here how can we 'move forward', preferably > without appealing to the absent persons and to the non-working > services? No, a "move forward" idea is broken from the start. Be specific. What is it that does not currently work and which is critical for developing perfect commits? I posit nothing. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Le 17/03/2012 22:03, Peter Stuge a écrit : > Viktor Tarasov wrote: >> I still propose to temporarily use the alternatives jenkins & gerrit. > It's IMO really stupid to fork anything, regardless if it is code or > infrastructure. You are amazedly brief. Could you explain here how can we 'move forward', preferably without appealing to the absent persons and to the non-working services? > > //Peter > ___ > 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
Re: [opensc-devel] Managing the queue line of a compilation farm
Le 16/03/2012 19:29, Jean-Michel Pouré - GOOZE a écrit : >>> For example, in https://opensc.fr/jenkins/ the build on two windows >>> platform depend-on and triggered-by the build on debian. > To build under Debian packages, we probably need: > https://launchpad.net/jenkins.pbuilder.plugin > > pbuilder is the Debian chrooted package builder. > > If you allow us, we may trigger pbuilder on our farm using SSH. The > problem with pbuilder is that it runs under root account (or sudo which > is the same). So we will probably need to install a fresh server with > all Debian and Ubuntu chroots. Builds will auto-sign packages. Priority > should be set to zero, just like in Debian backports. Ok. > I am guite disapointed by OpenSC-SM naming under Windows. From a user > point of view, it should be more explicit and include a readable naming > space, like for example name-year-date-32x.msi. Even if this means a > single build everyday. You should not be disappointed - the naming policy is open for suggestions. The current one is just the rapid 'working' solution. > Can we proceed with Debian stuff? We can cope with all GNU/Linux builds > under all platforms including x32, x64 and ARM, providing signed > packages and APT/RPMs repositories. Excellent, I will prepare the guidelines for the procedure. Thanks. > Kind regards, Kind regards, Viktor. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Viktor Tarasov wrote: > I still propose to temporarily use the alternatives jenkins & gerrit. It's IMO really stupid to fork anything, regardless if it is code or infrastructure. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Le 17/03/2012 19:13, Jean-Michel Pouré - GOOZE a écrit : > Le vendredi 16 mars 2012 à 23:36 +0100, Ludovic Rousseau a écrit : >> I finally succeeded in rebasing and approving some patched in the >> backlog. I still do not understand everything. I subscribed to the >> OpenSC project on gerrit so I should receive a email for any submitted >> patch. >> >> I also added Viktor Tarasov as a member of the Integrators group. >> Viktor, you should be able to approve patches now. > Thanks a lot for your work and adding Viktor in the group. Thanks. Gerrit still has replication problem -- 'staging' of OpenSC/OpenSC.git do not updated by merges of Gerrit's repository. Certainly, gerrit is nice tool to play with, but, without replication it looses much of it's utility. More important, from my point of view, is jenkins. Somebody has to administrate jenkins to extend the existing jobs, create the new ones and include the build of Linux packages in continuous manner. Anybody can do it? I do not have such rights. That's why I still propose to temporarily use the alternatives jenkins & gerrit. Both were tested with 'staging' of OpenSC and 'secure-messaging' of OpenSC-SM on Debian, Win32 and Win64. With the graceful cooperation of Jean-Michel this jenkins should include the MacOS and other slaves and to build the linux packages. Kind regards, Viktor. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] OpenSC and gerrit
Le vendredi 16 mars 2012 à 23:36 +0100, Ludovic Rousseau a écrit : > I finally succeeded in rebasing and approving some patched in the > backlog. I still do not understand everything. I subscribed to the > OpenSC project on gerrit so I should receive a email for any submitted > patch. > > I also added Viktor Tarasov as a member of the Integrators group. > Viktor, you should be able to approve patches now. Thanks a lot for your work and adding Viktor in the group. -- 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
