Change Details

As a follow-up to T257543, CommTech will look into what it would take to remove WSExport's reliance on the tool that it uses to create books' lists of contributors. This could involve moving this logic into WSExport, or perhaps replacing the credits list with a link to the book on Wikisource, or maybe a dynamic credits list produced by WSExport. This would have the advantage of improving the speed of book generation (fewer API requests etc.). What are the legal implications of the credits list (i.e. is it a hard requirement)?

**Background: **As a follow-up to T257543, CommTech will look into what it would take to remove WSExport's reliance on the tool that it uses to create books' lists of contributors. This could involve moving this logic into WSExport, or perhaps replacing the credits list with a link to the book on Wikisource, or maybe a dynamic credits list produced by WSExport. This would have the advantage of improving the speed of book generation (fewer API requests etc.). What are the legal implications of the credits list (i.e. is it a hard requirement)? **Acceptance Criteria:** * Remove dependency on phetools/credits.py

**Background: **As a follow-up to T257543, CommTech will look into what it would take to remove WSExport's reliance on the tool that it uses to create books' lists of contributors. This could involve moving this logic into WSExport, or perhaps replacing the credits list with a link to the book on Wikisource, or maybe a dynamic credits list produced by WSExport. This would have the advantage of improving the speed of book generation (fewer API requests etc.). What are the legal implications of the credits list (i.e. is it a hard requirement)? **Acceptance Criteria:** * Remove dependency on phetools/credits.py