Hi Team Was looking through http://bugs.koha.org today, and saw that the issue for the z39.50 Server has been resolved (thanks Joshua) I am thinking that we should create a seperate Bugzilla component for the z39.50 server to allow us to track issues etc. I was about to create the component, and stuck a mild problem which I would like your comments on ... do we (a) Create a component for the z39.50 server, and leave the z39.50 client as part of the Catalogue component (b) Create a seperate component for the server and the client (c) Create a z39.50 component to handle both client and server. or (d) Don't create any components as both client and server belong the in current Catalogue compnent Your thoughts would really be appreciated Cheers Mike (Dragon28)
Hi Team hiya...
Was looking through http://bugs.koha.org today, and saw that the issue for the z39.50 Server has been resolved (thanks Joshua) no prob...
I am thinking that we should create a seperate Bugzilla component for the z39.50 server to allow us to track issues etc. I was thinking the same thing...
I was about to create the component, and stuck a mild problem which I would like your comments on ... do we
(a) Create a component for the z39.50 server, and leave the z39.50 client as part of the Catalogue component
(b) Create a seperate component for the server and the client
(c) Create a z39.50 component to handle both client and server.
or
(d) Don't create any components as both client and server belong the in current Catalogue compnent I vote for creating a seperate component for the server and the client since they were developed by different folks. BTW: while you're at it, I don't mind being the assigned "contact" for bugs/feature-requests for the server.
Thanks, Joshua
On 2004-01-14 18:13:25 +0000 Mike Mylonas <dragon28@ihug.co.nz> wrote:
(a) Create a component for the z39.50 server, and leave the z39.50 client as part of the Catalogue component
I think this is best, but there's a danger that people will get confused and we'll have to reclassify lots. advert:
Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms.
I'd rather use GNU Arch. http://www.gnu.org/software/gnu-arch/ -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
Mike Mylonas a écrit :
Hi Team
Was looking through http://bugs.koha.org today, and saw that the issue for the z39.50 Server has been resolved (thanks Joshua)
I am thinking that we should create a seperate Bugzilla component for the z39.50 server to allow us to track issues etc.
I was about to create the component, and stuck a mild problem which I would like your comments on ... do we
(a) Create a component for the z39.50 server, and leave the z39.50 client as part of the Catalogue component
I vote for this, as the client is used by the catalogue !
(b) Create a seperate component for the server and the client
Maybe I could work with this solution too.
(c) Create a z39.50 component to handle both client and server.
NO
(d) Don't create any components as both client and server belong the in current Catalogue compnent
NO. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Thanks for all of the replies, and following the general concensus I have added a "z39.50 Server" component to http://bugs.koha.org. (thanks Joshua for volunteering to be the owner of this component) I have not changed/or added a component for the client at this point in time, this is based on peoples comments and reponses. But this is easily changed in the future if we so desire. Cheers Mike (Dragon28)
participants (4)
-
Joshua Ferraro -
Mike Mylonas -
MJ Ray -
paul POULAIN