Re: [Koha-devel] Proposed addition to the development-meetings:
Along with the first homework assign I will also be setting a date for us to vote on the (homework)
bug/enh/thought at the meeting after a sufficient discussion has occurred.
Brendan: What do you exactly mean here? The bug/enh thought is kind of vague :) There will always be discussion if some patch is just a bugfix or an enhancement. Ideally, every bug fix should be an enhancement. And what about the difference: enhancement vs. new feature? Marcel
Hello Marcel - I feel that some things that are put into discussion just take too long to get out of discussion or don't really ever get any feedback. So the idea is that I'll bring these up at Dev-meetings so we get some movement on them. The example I used was the DBIC - we've been talking about this for a few years now and I think it's time we all vote and decide on the correct path forward. That is it - nothing more complicated than that. Thanks, Brendan On Mon, Oct 13, 2014 at 12:52 AM, Marcel de Rooy <M.de.Rooy@rijksmuseum.nl> wrote:
Along with the first homework assign I will also be setting a date for us to vote on the (homework)
bug/enh/thought at the meeting after a sufficient discussion has occurred.
Brendan: What do you exactly mean here? The bug/enh thought is kind of vague :)
There will always be discussion if some patch is just a bugfix or an enhancement. Ideally, every bug fix should be an enhancement. And what about the difference: enhancement vs. new feature?
Marcel
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info@bywatersolutions.com
Hello Marcel -
I feel that some things that are put into discussion just take too long to get out of discussion or don't really ever get any feedback. So the idea is that I'll bring these up at Dev-meetings so we get some movement on them. The example I used was the DBIC - we've been talking about this for a few years now and I think it's time we all vote and decide on the correct path forward. That is it - nothing more complicated than that. I think that the problem comes from the fact that TIMTOWTDI. ie: there is not "one correct path". We should give deadlines for proposals and POC, then call for a vote, and once we've voted, let's do it like this. There's probably another way to do it, probably a better way according to someone, but it's the way we've decided to go, that's it. And the ones who will do it should have a big voice (in french we say something like "persuaders are not
Le 14/10/2014 17:27, Brendan Gallagher a écrit : paying", to express that it's easy to say what to do when you don't have to do it yourself ;-) ) -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert
+1, I've been feelng we need 'deadlines for decisions' fro some time now and have voiced it a few times to various people. Great to hear your intent on stepping up to the post in the leading of such discussions Brendan :) Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Landline: 0203 286 8685 Mobile: 07725985636 http://www.ptfs-europe.com On 21 October 2014 09:02, Paul Poulain <paul.poulain@biblibre.com> wrote:
Le 14/10/2014 17:27, Brendan Gallagher a écrit :
Hello Marcel -
I feel that some things that are put into discussion just take too long to get out of discussion or don't really ever get any feedback. So the idea is that I'll bring these up at Dev-meetings so we get some movement on them. The example I used was the DBIC - we've been talking about this for a few years now and I think it's time we all vote and decide on the correct path forward. That is it - nothing more complicated than that.
I think that the problem comes from the fact that TIMTOWTDI. ie: there is not "one correct path". We should give deadlines for proposals and POC, then call for a vote, and once we've voted, let's do it like this. There's probably another way to do it, probably a better way according to someone, but it's the way we've decided to go, that's it. And the ones who will do it should have a big voice (in french we say something like "persuaders are not paying", to express that it's easy to say what to do when you don't have to do it yourself ;-) )
-- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (4)
-
Brendan Gallagher -
Marcel de Rooy -
Paul Poulain -
Renvoize, Martin