Le 12/05/2011 17:10, Nicole Engard a écrit :
As a librarian that's just you not giving them enough credit. I agree you don't ask the customer (unless the customer wants to do it) but you can ask and train your project manager. We have customers test our patches and then they're passed on to one of us for a sign off. It's simple, it takes 1 minute more time and it means our patches make it to QA. Can I say you're saying: "BibLibre has a problem, fix BibLibre"? So you've inclined to vote 2 to my previous question? (Or do I go too far, and it's not what you want to say)
Paul wrote:
So, here is the final question. Please vote: 1- Paul, OK, the problem you rise is a real one, you're a valuable contributor, let's try to find a solution to retrieve agility (without loosing stability) 2- Paul, shut-up, everything is perfect we don't need to change anything. [In this case, BibLibre only option will be to explain to our customers they've a de-facto fork and they must choose between their features and stay "community". And that probably means we will start an official fork, with all our cool -and stable- new stuff. Sorry, but I don't see an other possibility] -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08