-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is Omegaconf maintained? #1200
Comments
I would be interested in this as well. Hydra is used quite heavily in the machine learning community and omegaconf hasn't seen any (pre)releases in over a year. |
Short answer == it's not really maintained, though I don't know to which extent @Jasha10 is still around. I was trying to keep an eye out up until ~last year, but then got too busy. AFAIK Meta isn't supporting it anymore. I'm still using it myself and I still hope to get back to it to check out PRs / issues and hopefully trigger a new release sometime this year, but I can't commit to it unfortunately. If someone from the community wanted to step up and help, I'm pretty sure we can make them a maintainer on the project. [EDIT: and yeah, same for Hydra] |
Sad to hear, this package is amazing, and core to the infrastructure of my company. I have tested some equivalent libraries and this one is the best. |
Hi folks, I think the answer to "Is Omegaconf maintained?" is "sort of." Former mainstay contributors, including myself, are no longer working on the project professionally. It appears to me that the hydra project, which is owned by Meta and uses OmegaConf as a dependency, is still active (and therefore I conclude it's still in use within Meta). As mentioned above I've been working to get CI jobs working for python 3.12 & 3.13. |
Our team also heavily uses Omegaconf: https://github.com/oumi-ai/oumi If you're willing to take volunteers from the community, do y'all have a rough estimate for how long it would take for a newcomer to trigger a new release? I'm assuming the bulk of the work may not be the release process itself, but ongoing maintenance to patch issues afterwards? |
Our project will heavily use Omegaconf: https://github.com/RapidAI/RapidOCR |
The torchtune project also relies on OmegaConf ! |
First of all, thanks for creating and maintaining Omegaconf all these years 🙏🏼
I've been following this repo closely for the past few months, especially after we started hitting #1000. There's a couple of issues asking for a new stable release (#1158, #1185) and nothing has been said so far.
I notice that @omry, creator of the project, has moved on. @Jasha10, who has been maintaining Omegaconf in the past few months, is still reviewing PRs, but seemingly doesn't have much time for the project lately.
For the record, Omegaconf seems to still be in use in Hydra, the sister project, but equally there are no news about release dates yet.
About other products coming out of Facebook Research, I notice that fairseq2 is supposed to replace fairseq, and the newest version doesn't use Omegaconf (yet).
I'd like to ask what are the plans for the future, and whether the maintainers need help bringing the project forward.
Full disclosure: I'm the PM for https://github.com/kedro-org/kedro/, which uses Omegaconf heavily.
The text was updated successfully, but these errors were encountered: