Hola! On Tue, Jun 7, 2011 at 18:59, Juan Antonio Martinez <jons...@terra.es> wrote: > El mar, 07-06-2011 a las 17:38 +0300, Martin Paljak escribió: >> It would be nice to split some "focus areas" to people who would deal with >> them on "daily basis", like Windows, OSX, PKCS#11, Initialization, PKCS#15 >> conformance/libopensc core and set up separate builders for those >> branches/developers. >> So that individual changes could be aggregated and pulled in bigger sets for >> releases. > > Does this "focus areas" org includes maintainers for each card driver, > or driver maintenance is a sort of "traversal work"? > Current "getInvolved" wiki page [1] shows a mix of areas/drivers list GetInvolved wiki page lists pages tagged with "maintained + <name>" which has essentially no organization whatsoever. Just pages me (or somebody else) has tagged like that and something that helps to keep an overview of "who is doing/interested in what"
Focus areas are units which "make sense at the moment", be that a active/important/huge card driver or a specific thing like "multithreading improvements". They are supposed to change in time, but some make sense most of the time (like "windows", "osx", "minidriver", "pkcs11", "pinpads", "gui" etc) Defining dependencies between them also help, like "pinpads would love to use a GUI notification for "please enter PIN". The setup of "focus areas" should be entirely organic. Setting up separate builders from current trunk/master is a matter of 10 minutes per platform per branch (with the verification that builds succeed and get uploaded) > About Testing: here in Spain we are talking [2] about the best way to > do automated testing, but unsure about the convenience of card driver > testing on every push (because need a "live" DNIe and a sort of > user-less pin handler). "automatic" and "regularly" with the period chosen to be sufficient. Could be daily, could be weekly. > IMO, for read-only cards compile and tarball is sufficient for "-svn", > with manual card testing for "-rc" and "-stable" releases. Anyway, we > are next to get ready a set of java automated tests for our card [3] > > Juan Antonio > > [1] http://www.opensc-project.org/opensc/wiki/GetInvolved > [2] http://forja.cenatic.es/forum/forum.php?thread_id=3968&forum_id=497 > [3] > http://forja.cenatic.es/frs/download.php/1263/JavaDNIeExamples.tar.gz > > > _______________________________________________ > 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
