On 2/15/2012 5:39 AM, Jean-Michel Pouré - GOOZE wrote: > Dear all, > > I just got in contact with Stef Walter, who is integrating libp11-glue > into Gnome and Gnome keyring. > > He outlines that libp11-glue needs this patch: > PKCS#11 module shouldn't fail if mlock doesn't work > http://www.opensc-project.org/opensc/ticket/389 > > This patch and other waiting patches raise the question of OpenSC > guidance and the need to have more commiters to OpenSC main GIT. > > Martin, would you agree to add Viktor as a major OpenSC GIT member with > power to apply patches to main GIT trunk? I don't want to be paranoid, > but we need a more flexible approach rather than just Martin and Ludovic > applying and reviewing patches. > > We discussed that at FOSDEM in a small audience, but I would like to > discuss that issue in public and have your own opinion. Who would like > OpenSC GITHUB to be REALLY in control of the community? Martin and > Ludovic, could you agree to open your group to other members of the > community?
The question is not so much who is on the commiter list, but do commits get made when needed, and who decides a commit is ready and should be made. There are minor fixes, like 389 that is 4 months old with an additional fix 2 months ago, and looks like it needs to be made, as well as major changes such as the SM, ePass2003, and the ECDH modifications. Personally, I am quite interested in getting the ECDH in to the next release with or without the SM code and am willing to rebase the modifications as needed. I believe the ECDH has been ready for months. Viktor pulled the ECDH modifications into his SM on October 4, 2011 and he also pulled in the ePass2003 on January 29. The way forward is not necessarily more commiters, but a plan for the next release and some action. So can we consider adding ePass2003, SM, and ECDH to the next release as these are already being tested together. If giving Viktor commit authority would speed up the inclusion of both small and larger modifications, it would be OK with me. If we can get these included without giving him commit authority, that would be OK with me too. But we need action. > > Community, please advice and discuss this issue. > > Kind regards, > Jean-Michel > > > > > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel -- Douglas E. Engert <deeng...@anl.gov> Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
