The latest milestone in the OpenTF journey happened yesterday, with the release of OpenTF’s public repository. As promised, this happened 10 days after our initial fork announcement.
Within the first 12 hours, the repo already reached over 2,700 stars and - once more - made a series of splashes on social channels.
That conversation is still going, and it includes some (very welcome) feedback, which marked our first opportunity for true two-way community interaction.
Also, on what-used-to-be-Twitter, Fireship chimed in again to provide his warning:
So yeah, you should definitely avoid doing that. 😉
With the public repo open you can now join our journey and impact its direction by directly contributing to the OpenTF project.
The easiest way to do that is by opening an issue. Feature requests, bugs, improvements, old issue reposts… Every idea, comment, or feedback is welcome.
For major changes/upgrades, we would ask you to provide an RFC. To open an RFC go to Issues, select Submit NewIssue, and choose the Submit RFC option, which will ask you to fill this template.
All RFCs, including the ones prepared by the core team, will go through the public RFC process to facilitate open and transparent discussion and decision-making. You can also always check on all open RFCs using the ’by label’ filter:
Please note that all code changes should be related to an issue, to which you've been assigned.
If an issue with the change you're adding already exists, please communicate that you are taking ownership of it. If it doesn’t, please create one and express your interest in working on it, and discuss it first, prior to working on the code.
Also note that signing your commits ensures you are accepting the Developer Certificate of Origin (DCO), which is required for making code contributions to OpenTF.