Le mardi 27 mars 2012 à 03:19 +0200, Peter Stuge a écrit : > There was always a way for the ccid package to work around the > problem, I don't know why this wasn't done, but I guess that it would > have required too much effort, and noone contributed such effort to > the ccid project. I guess that a perfect patch for ccid would have > been most welcome.
I agree there is a lot of work around libusb. But ...
In bazar development, we should agree to release unperfect code in one
"unstable" branch and let the community fix it.
One reason is the limited time of reviewers. You write "we will not work
for you". We noticed, thanks and this is NOT a problem. This is where
the process should evolve to take the notion of limited resources into
account and give the community at large more power and freedom.
I am worried that OpenSC GIT development is too scattered. It looks
like: Scooby-Doo, Where Are You! In Scooby-Doo, whenever there is a
challenge, the team decides to split and look for the monster. Then when
a monster shows up, the character is alone to fix it and receives no
help.
In other words: too many branches => No review => No testing from
end-users => no contribution => nothing. Notice this is what happened to
tokend, so we should worry.
Unless patches are committed to GIT unstable branch very quickly, let's
say in days, there will be no testing/review of patches. So I would be
in favor of letting main developers commit their changes to ONE SINGLE
git staging branch directly and let developers/users fix the code.
Anyway, let's give some time to Gerrit to see if we are still in the
"Scooby-Doo, Where Are You!" situation. If this does not work, let's get
back to one single unstable branch to be united again.
Kind regards,
--
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
