I think the most important step is to get it out there. So:
- Choose a license. These resources might help:
- https://fontsarena.com/licenses-explained/
- https://choosealicense.com/
- https://opensource.org/licenses
I'd stick with the licenses made for fonts or in use by other font projects, as there are some specifics to fonts licensing.
- Choose a name
- Sign up and create a repo. Upload your project.
That is the "get it out there" step. If you want to be open, generally speaking you want to include a LICENSE file, your creation in the format you're editing it and other people can load and edit it, too. And the exported file in case of something like this, so people can directly use it without learning how to convert a font into a format that is usable. It's also good practice to include a README.md with explanations and a summary of what this is.
I think that's a sound approach for open source. And it's generally alright to learn as you go. Even if you don't get everything perfect at once, the most important thing is that it's available. People might pick up on it. And they will file bug reports and issues if they like it some other way. So you'll be directed into the right direction anyways. And once you have something to show off, you can start talking about it or make people aware of its existence.
(And maybe skip all the boilerplate and complicated extra stuff at first. You don't need an AUTHORS file, no code of conduct, no documentation if there isn't anything complicated to explain... Just stick to the important stuff and don't make it unnecessarily complicated and distracting for your users.)
I think the more important file is the fontforge one. As this is the thing people can edit and build upon. (the "source")
The otf, ttf and woff are just a bonus for people who don't want to install fontforge and and go through the process of exporting it themselves.
Ultimately it's your decision what you release. It's a similar concept whether you share a cake, or a recipe for a cake. The free software / open-source movement is concerned with sharing the recipes. That's why they share source code and files in the format they've edited it in. (And often include instructions on how to build it, since that is usually a bit more complicated with software.) It enables people to also load it in their editors and customize it, adapt it to their use-cases and fix issues.
You can also just publish the end-result, which are the otf and ttf files in your case. But people can't really modify or customize those. It'd be called a freeware font, then. It'd help people who just want to use it, but doesn't provide much more.
I'd invite you to upload both the sfd and the resulting otf and ttf. Usually that's how people do it. Distributing digital files comes at practically no cost. On the internet you can share a recipe and the actual cake alongside at no extra cost.