Le mercredi 21 mars 2012 à 23:03 +0100, Peter Stuge a écrit : > Thanks for taking the time! It really helped understand what you > mean!
Peter, what I read in your previous post, you seem to be too picky.
IMHO, quality is a circle: you write code, ask for review, commit a
first version, ask for review, commit a second version, publish
packages, reach thousands of users, get bug reports, fix in code and
slowly the quality of code grows until it reaches perfection. At the
same time, you have to convince people to join and give them some
freedom, especially if they write code for free.
What you are proposing us is a bureaucratic organization which might
work in a company writing closed-source software, not free software.
The way OpenSC is getting organized recently is using collaboration
tools: Gerrit, Jenkins. But these tools are used to limit the freedom of
developers. They are being used conversly to traditional goals.
Setting-up collaboration tools with ONE or TWO admins and an army of
developers is just a huge lost of time and efforts.
Now from a personal point: why are you afraid of freedom in a Free
software development? Can't you trust recognized developers who have a
life and a family to make useful commits after having a discussion on a
mailing list. And why do you need to set passwords to limit our freedom?
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
