In addition to our numerous providers, we maintain forks for hcl and registry-address. These repositories are currently behind their forks. A fork is meaningless if we do not have changes on top of it, and both of these have particular changes made by the OpenTofu team. We should keep these forks up to date and rebase our changes.
How? It's definitely a bit of a chore; how should the burden of this be managed among maintainers so that no one person is "the fork guy"? That is, how do we keep this duty robust to fluctuating availability of maintainers (sickness, vacation, etc)?
In addition to our numerous providers, we maintain forks for
hclandregistry-address. These repositories are currently behind their forks. A fork is meaningless if we do not have changes on top of it, and both of these have particular changes made by the OpenTofu team. We should keep these forks up to date and rebase our changes.How? It's definitely a bit of a chore; how should the burden of this be managed among maintainers so that no one person is "the fork guy"? That is, how do we keep this duty robust to fluctuating availability of maintainers (sickness, vacation, etc)?