Moving this out of #11 as it allows for a bit more room to plan strategy regarding migrating the extensions. And might reach a more broad audience.
First of all, what would be the very best method of migrating all extensions.
All in bulk with shared git commit history
Individually with git history
Don’t care about the git history
The primary reason we should preserve git history is to not lose the credibility that previous contributors have done over the years.
Migrating extensions individually would give the benefit of having a better understanding of what’s going on, and allow fixing what’s broken more easily but it will break those commits as some commits may have touched multiple extensions. Which is not the most positive outcome for existing contributors.
The suggested approach I have in mind is:
- Migrate all extensions at once assuming it will break
- See what's broken
- Fix it (which likely will be DTD entities that we need to change to XML entities
Once that's done, I suggest we do a docbook-cs sweep so it will help contributors to make changes. We don't need to care about translators being overwhelmed by big changes.
Then finally we can prepare to publish this new doc-extensions repo by making a plan for:
- Infastructure
- Redirects
- Etc, etc (will be a separate discussion once we are more ready for it).
Moving this out of #11 as it allows for a bit more room to plan strategy regarding migrating the extensions. And might reach a more broad audience.
First of all, what would be the very best method of migrating all extensions.
All in bulk with shared git commit history
Individually with git history
Don’t care about the git history
The primary reason we should preserve git history is to not lose the credibility that previous contributors have done over the years.
Migrating extensions individually would give the benefit of having a better understanding of what’s going on, and allow fixing what’s broken more easily but it will break those commits as some commits may have touched multiple extensions. Which is not the most positive outcome for existing contributors.
The suggested approach I have in mind is:
Once that's done, I suggest we do a docbook-cs sweep so it will help contributors to make changes. We don't need to care about translators being overwhelmed by big changes.
Then finally we can prepare to publish this new doc-extensions repo by making a plan for: