Generalize Trusted Book Provider so anyone can propose a TBP via a PR
mekarpeles opened this issue · comments
Problem
A clear and concise description of what you want to happen
Similar to #9234, refactor the Trusted Book Provider flow so that:
- A new trusted book provider is added by opening a PR request with a yml entry for the new provider
- Minimize coding requirements for submitter: e.g. No new button template file or python class is required
- On app start, TBP's are loaded from the yml and registered with Open Library
Additional Context
The goal is to unblock some of these github issues that propose new providers and also this google form
Proposal & Constraints
What is the proposed solution / implementation?
Is there a precedent of this approach succeeding elsewhere?
Which suggestions or requirements should be considered for how feature needs to appear or be implemented?
Leads
Related files
Stakeholders
Note: Before making a new branch or updating an existing one, please ensure your branch is up to date.