Fwd: Packing needs - status to add to bugzilla and the dashboard?
Thanks Liz. ---------- Forwarded message ---------- From: Liz Rea <liz@catalyst.net.nz> Date: Tue, Mar 8, 2016 at 12:37 PM Subject: Re: [Koha-devel] Packing needs - status to add to bugzilla and the dashboard? To: Brendan Gallagher <info@bywatersolutions.com> Robin wrote a couple of quite good wiki pages on this subject: https://wiki.koha-community.org/wiki/Building_Debian_Dependencies https://wiki.koha-community.org/wiki/Building_Debian_Dependencies/Dependency... On 09/03/16 06:50, Brendan Gallagher wrote: Yup all good points. Not to put it all on the PM - but I think a way to track this in BZ is needed. A better workflow - perhaps based on Chris's point - a "failed QA - needs package" status (or some worded status)? Do we have a defined role description of responsibility of the Packaging Manager? (I've only read Robin's posts to the mailing list before - is that it?) On Tue, Mar 8, 2016 at 9:37 AM, Galen Charlton <gmc@esilibrary.com> <gmc@esilibrary.com> wrote: Hi, On Tue, Mar 8, 2016 at 12:30 PM, Chris Cormack <chrisc@catalyst.net.nz> <chrisc@catalyst.net.nz> wrote: I don't think it's fair to push this all on the package manager. If a dev introduces new dependencies that need packaging, it should be their responsibility to make sure this is done. Indeed. I am willing to build *some* packages (and submit them to Debian), but that willingness is decidedly not infinite. The first question that somebody who proposes to add a new dependency should ask themselves is this: is there a way to accomplish the task at hand without adding a new dependency? If not, can the task at hand be accomplished using packages that are already in Debian stable? If not, does the dependency at least have an active third-party ITP (intent to package) in the Debian bug tracker? Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org &http://evergreen-ils.org _______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttp://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/ -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7 -- --------------------------------------------------------------------------------------------------------------- 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
Lars Wirzenius sounded quite eager to do an extensive Debian packaging workshop for us if there is some funding available. He did the initial work on the Koha Debian packages sponsored by Catalyst, IIRC. He wanted to get back to me in April about the option of doing that at the Hackfest in Berlin the week before Kohacon. So if we found some money and some people to attend, the packaging problem could be solved in a sustainable way. -- Mirko Brendan Gallagher schrieb am 08.03.2016
Thanks Liz.
---------- Forwarded message ---------- From: Liz Rea <liz@catalyst.net.nz> Date: Tue, Mar 8, 2016 at 12:37 PM Subject: Re: [Koha-devel] Packing needs - status to add to bugzilla and the dashboard? To: Brendan Gallagher <info@bywatersolutions.com>
Robin wrote a couple of quite good wiki pages on this subject:
https://wiki.koha-community.org/wiki/Building_Debian_Dependencies https://wiki.koha-community.org/wiki/Building_Debian_Dependencies/Dependency...
On 09/03/16 06:50, Brendan Gallagher wrote:
Yup all good points. Not to put it all on the PM - but I think a way to track this in BZ is needed. A better workflow - perhaps based on Chris's point - a "failed QA - needs package" status (or some worded status)?
Do we have a defined role description of responsibility of the Packaging Manager? (I've only read Robin's posts to the mailing list before - is that it?)
On Tue, Mar 8, 2016 at 9:37 AM, Galen Charlton <gmc@esilibrary.com> <gmc@esilibrary.com> wrote:
Hi,
On Tue, Mar 8, 2016 at 12:30 PM, Chris Cormack <chrisc@catalyst.net.nz> <chrisc@catalyst.net.nz> wrote:
I don't think it's fair to push this all on the package manager. If a dev
introduces new dependencies that need packaging, it should be their
responsibility to make sure this is done.
Indeed. I am willing to build *some* packages (and submit them to Debian), but that willingness is decidedly not infinite.
The first question that somebody who proposes to add a new dependency should ask themselves is this: is there a way to accomplish the task at hand without adding a new dependency? If not, can the task at hand be accomplished using packages that are already in Debian stable? If not, does the dependency at least have an active third-party ITP (intent to package) in the Debian bug tracker?
Regards,
Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org &http://evergreen-ils.org
participants (2)
-
Brendan Gallagher -
Mirko Tietgen