Integrate Ğ1 monetary license

Integration to benefits all Python programs

• Integrate Ğ1 monetary license as a git subtree:
  • squash?
• Integrate g1_monetary_license folder into the Python package:
  • Add g1_monetary_license folder to the pyproject.toml
  • Add __init__.py in g1_monetary_license folder (will be in the git history of duniterpy repository, shouldn't be an issue to pull g1_monetary_license changes)
• Add helper to get the path of the licenses
• Write documentation in CONTRIBUTING.md on how to proceed:
  • Create link from the README.md
  • Warn to not modify the monetary license here but on its repository
  • Procedure on how to pull changes from g1_monetary_license repository (remote, subtree)

changed milestone to %1.0.0

added Feature label

marked this issue as related to silkaj#221 (closed)

mentioned in issue silkaj#221 (closed)

changed the description

@vtexier, are you agree on the principle of distributing g1_monetary_license (integrated as a subtree) into DuniterPy?

The problems I see are:

• How to be agnostic of the I18n system of the client? In Tikka, I use gettext and the licence files are renamed to be used easily by gettext :
  • tikka/locale/en_US/licence_g1.txt
  • tikka/locale/fr_FR/licence_g1.txt
• Adding a git subtree for the licence in DuniterPy add a strong coupling. We should do a new release each time a translation changes or is added to the licence. I prefer that the client maintainer take care of that without having to wait for DuniterPy to be updated.

So, this strong dependency will add too much coupling, and will not be used if i18n is managed differently. I do not think it has significant benefits.

changed milestone to %Backlog

changed the description

unassigned @moul