Hi all, It should be interesting to have a new component for bugs related to ILSDI in bugzilla ? proposals are: - External services Component - ILSDI - Web services - Other ? - or not ? Any thoughts ? Thanks Alex
Web Services sounds great for me. (It can includes more than only ilsdi services) Claire; On 08/04/2011 11:09, Alex Arnaud wrote:
Hi all,
It should be interesting to have a new component for bugs related to ILSDI in bugzilla ?
proposals are:
- External services Component - ILSDI - Web services - Other ? - or not ?
Any thoughts ?
Thanks
Alex
_______________________________________________ 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/
Le 08/04/2011 11:09, Alex Arnaud a écrit :
Hi all,
It should be interesting to have a new component for bugs related to ILSDI in bugzilla ? well, i'm OK with "web services", BUT => I also propose to remove some components. I think we have too much details. For example: OPAC comments => OPAC. Patron import => Tools.
So, I'm throwing a proposition to reduce the number of components to 20 maximum. Your opinoin ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Hi, On Fri, Apr 8, 2011 at 8:22 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example: OPAC comments => OPAC. Patron import => Tools.
+1 to both.
So, I'm throwing a proposition to reduce the number of components to 20 maximum.
-1. We should have as many components as needed, and no more, but I don't think specifying an arbitrary limit is useful. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Hi,
On Fri, Apr 8, 2011 at 8:22 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example: OPAC comments => OPAC. Patron import => Tools. +1 to both.
So, I'm throwing a proposition to reduce the number of components to 20 maximum. -1. We should have as many components as needed, and no more, but I don't think specifying an arbitrary limit is useful. Well i've poorly explained my idea. It's not to put an arbitrary limit, but to think twice when adding a component. For example, do wee need a specific component for each tool of the Tools
Le 08/04/2011 15:08, Galen Charlton a écrit : menu ? I don't think so. As you said +1 to the previous propositions, I could write a more detailled proposition to reorganise the components if ppl agrees. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Hi, On Fri, Apr 8, 2011 at 9:24 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example, do wee need a specific component for each tool of the Tools menu ? I don't think so.
Agreed. Here's link to a report of the number of bugs filed by category: http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap As you can see, there are a number of components that have not been frequently used which would be candidates for merging. One thing to note, however, is that if a component might be infrequently used but should not be merged because there is somebody actively maintaining it. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Online help and documentation can be merged under documentation since I handle both of those and they're almost identical :) Nicole On Fri, Apr 8, 2011 at 9:34 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Apr 8, 2011 at 9:24 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example, do wee need a specific component for each tool of the Tools menu ? I don't think so.
Agreed. Here's link to a report of the number of bugs filed by category:
As you can see, there are a number of components that have not been frequently used which would be candidates for merging. One thing to note, however, is that if a component might be infrequently used but should not be merged because there is somebody actively maintaining it.
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com _______________________________________________ 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/
PS. Developer Documentation needs to stay separate since that is handled by developers and not me :) On Fri, Apr 8, 2011 at 11:06 AM, Nicole Engard <nengard@gmail.com> wrote:
Online help and documentation can be merged under documentation since I handle both of those and they're almost identical :)
Nicole
On Fri, Apr 8, 2011 at 9:34 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Apr 8, 2011 at 9:24 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example, do wee need a specific component for each tool of the Tools menu ? I don't think so.
Agreed. Here's link to a report of the number of bugs filed by category:
As you can see, there are a number of components that have not been frequently used which would be candidates for merging. One thing to note, however, is that if a component might be infrequently used but should not be merged because there is somebody actively maintaining it.
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com _______________________________________________ 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/
Hi, On Fri, Apr 8, 2011 at 11:06 AM, Nicole Engard <nengard@gmail.com> wrote:
Online help and documentation can be merged under documentation since I handle both of those and they're almost identical :)
Agreed. I've merged online help into documentation. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Hi, On Fri, Apr 8, 2011 at 9:08 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Apr 8, 2011 at 8:22 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
For example: OPAC comments => OPAC. Patron import => Tools.
+1 to both.
I've gone ahead and made both changes. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
participants (5)
-
Alex Arnaud -
Claire Hernandez -
Galen Charlton -
Nicole Engard -
Paul Poulain