Also, are you saying any newly packaged libraries *must* make it in to Debian? Can we not host our own packaged libraries on our apt server? Why must packages meet the Debian requirements? This seems like it's adding yet another barrier to entry for new Koha developers. Now we all need to be Debian package maintainers as well? It seems like we're taking away one of the most powerful features of Perl, it's extensive library of available modules. Just a thought. http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Tue, Mar 8, 2016 at 6:03 PM, Galen Charlton <gmc@esilibrary.com> wrote:
Hi,
On Tue, Mar 8, 2016 at 12:50 PM, Brendan Gallagher < info@bywatersolutions.com> wrote:
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?)
We do now, seeded with my view of the position:
https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager
On a side note, the overall page is new; I'm figuring that it might be a useful exercise to outline minimum role responsibilities for all of the named project positions.
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 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/