https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21833
--- Comment #14 from Pedro Amorim <[email protected]> --- (In reply to Katrin Fischer from comment #13) > Our own backend has quite a bit of code using the medium, but it might date > back to the type when it was still used. It would certainly need some work > to clean-up. > > What could a deprecation process look like? How and where do we anounce it > and how can we make it the most visible? Katrin, very fair points. I think you're bringing up a bigger issue. Maybe we should consider a koha-ill mailing list, a koha-ill IRC chat, or something similar where these sort of topics could be discussed. As it stands, there's no way of telling how many backends exist and what they're using. Furthermore, we're also missing proper documentation on every backend capability that core checks for, and what their purpose is (e.g. "should_display_availability", "unmediated_ill", or "create_api" (this last one is only introduced in bug 30719). These are useful to know as a backend developer, because they effectively function as 'hooks' for core functionality that backends can make use of. I believe we need a place where every ILL invested individual/organization can give their input on - and become aware of - updates and changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
