2.4. Release Manager? Bugzilla assignments?
Do we have a Release Manager for 2.4 yet? We had discussed the possibility of Emiliano taking the position (here, in IRC: http://koha.org/cgi- bin/logs.pl?recall=recall&saved_query=Koha%20Organizational%20M eeting%202004-09-21), but we haven't heard from him in a long time. Part of the reason I'm asking is that I'm wondering how we should handle the many bugs in Bugzilla which are now assigned to inactive developers (mostly Steve Tonnesen). Is it time to re-think the default assignments in bugzilla? Who should be the fall-back assign-to person for new bugs? Is anyone hungrily sifting through Bugzilla looking for the next tasty treat to work on? :) -- Owen ---- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us
Dear Owen Few days ago I've taken contact with Rachel, Paul and others to communicate the proximity for the finish from our local development tasks. We've discussed with Paul the best way to integrate our changes and enhacements to Koha, part by part. Actually we've changed and added many features that I'm looking to see if they cumpliment some rules as English comments and code quality. As we announced we added: - Borrower cards for identifying users with a time validity configurable. - Borrower academic information (Faculty & Career). Reports asociated with this. - Suspensions or fee features, configurable for branch and user category. - Calendar used from very part that a date is asked - Circulation, Reserves were rewritten admiting: items for only-on-library circulation, suspension considered, borrower card validation, date-or- num days loans, reserve consideration, circulation slip configurable for branch, etc - OPAC Searches rewritten, Dictionary using, virtual shelves rewriting for admiting bibliography shared between careers, RSS Feeds configurable inside Intranet and visible inside OPAC. And many other features. At the end of the project we'll summarize all of this inside http://biblio.fisica.unlp.edu.ar We'll not use Cataloging module, we'll use UNESCO's IsisMarc data entry tool. Also we made a module for admiting MARC Import zipped files for adding or updating. Some of the features could be seen as an answer to our local need and by that way, many others not. We'll be testing all the software package in February, and start the contribution in a organized way to the new R2.4 manager. Personally for continuing the wonderfull Paul's tasks as 2.2 R Manager I purposed Ernesto Silva or Andres Tarallo from ORT University, they are doing a very good job integrating their proper code inside Koha cvs. Kind Regards Emiliano.
Dear Emiliano, We're glad to hear from you, we're really impressed by all the achievments you've made. Most of the SIU contributions will be of great value for latin american libraries. However we can't accept the offer of becoming the new release manager. As we said before, the Library ILS project in Universidad ORT will end by the end of february. By mid month we hope to have the system in production. Andres Tarallo contract will end with the project, he might or might not continue working here. We won't have man power to become a release manager since I have other duties and maybe new projects to jump into. On the other hand since we haven't seen the code developed by SIU we can't help to integrate it to current source tree, nor test it. We think that there're people with deep knowldge of koha and greater contributions that deserve better this post (maybe someone of SIU?) I will continue mantaining our koha installation, doing my best to keep it current with new releases. As far as I can, I plan to continue enhancing it and contributing back patches, bugfixes and enhacements. I hope to do this in the true spirit of libre/free software: releasing early and often, sharing our code with all the development community. Regards, Ernesto Silva. Emiliano Marmonti wrote:
Dear Owen
Few days ago I've taken contact with Rachel, Paul and others to communicate the proximity for the finish from our local development tasks. We've discussed with Paul the best way to integrate our changes and enhacements to Koha, part by part. Actually we've changed and added many features that I'm looking to see if they cumpliment some rules as English comments and code quality.
As we announced we added:
- Borrower cards for identifying users with a time validity configurable. - Borrower academic information (Faculty & Career). Reports asociated with this. - Suspensions or fee features, configurable for branch and user category. - Calendar used from very part that a date is asked - Circulation, Reserves were rewritten admiting: items for only-on-library circulation, suspension considered, borrower card validation, date-or- num days loans, reserve consideration, circulation slip configurable for branch, etc - OPAC Searches rewritten, Dictionary using, virtual shelves rewriting for admiting bibliography shared between careers, RSS Feeds configurable inside Intranet and visible inside OPAC.
And many other features. At the end of the project we'll summarize all of this inside
http://biblio.fisica.unlp.edu.ar
We'll not use Cataloging module, we'll use UNESCO's IsisMarc data entry tool. Also we made a module for admiting MARC Import zipped files for adding or updating.
Some of the features could be seen as an answer to our local need and by that way, many others not. We'll be testing all the software package in February, and start the contribution in a organized way to the new R2.4 manager. Personally for continuing the wonderfull Paul's tasks as 2.2 R Manager I purposed Ernesto Silva or Andres Tarallo from ORT University, they are doing a very good job integrating their proper code inside Koha cvs.
Kind Regards Emiliano.
Owen Leonard a écrit :
Do we have a Release Manager for 2.4 yet?
Good question ;-) seems we have no more. Anybody candidate ? Otherwise, I'm afraid i'll have to be nominated again :-(
We had discussed the possibility of Emiliano taking the position (here, in IRC: http://koha.org/cgi- bin/logs.pl?recall=recall&saved_query=Koha%20Organizational%20M eeting%202004-09-21), but we haven't heard from him in a long time.
Part of the reason I'm asking is that I'm wondering how we should handle the many bugs in Bugzilla which are now assigned to inactive developers (mostly Steve Tonnesen). Is it time to re-think the default assignments in bugzilla? Who should be the fall-back assign-to person for new bugs? Is anyone hungrily sifting through Bugzilla looking for the next tasty treat to work on? :)
As Release Maintainer of 2.2.x, I think I should be the default person (but i'm not sure bugzilla can handle bugs-owner by version, just by module). In fact I already began to read bugs. I solved few of them, but I'm in a dramatic lack of time this month. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (4)
-
Emiliano Marmonti -
Ernesto Silva - Webmaster -
Owen Leonard -
Paul POULAIN