REQUEST: "graduate" Hera from argoproj-labs to argoproj

[flaviuvadan]

Hera

Goal

Support the growth of the Hera project and the community!

Summary

Hera has been part of the Argo ecosystem for ~3 years now. The project has undergone a lot of development to achieve a point of feature parity with Argo Workflows. In addition, Hera provides users with numerous features to facilitate access to Argo Workflows via integrations with Pydantic. In addition, everything that can be expressed in Argo Workflows can be expressed in Hera! The project:

• has a great community
• has a mature and stable codebase
• has grown a lot in the last 3 years
• is used in production
  • incomplete users list
• has 3 active maintainers
  • @samj1912
  • @elliotgunton
  • @flaviuvadan
• is approaching the 500 stars mark
• is vendor neutral, licensed under Apache 2.0
• ~1M downloads
  • https://www.pepy.tech/projects/hera

In addition, there are now companies who hire SWEs to work on Hera exclusively. Maintainers have the vision of using Hera to bring to MLOps what FastAPI brought to web development :) That's all to say: the project has an amazing community and plans to keep growing!

Next steps

A potential next step in the growth of Hera is to "graduate" it to argoproj. Concretely this means:

• move the repo from argoproj-labs to argoproj to make Hera an "official" Argo project
• establish a clear path for onboarding/offboarding Hera maintainers in accordance with Argo guidelines

Asks

Support the graduation of Hera from argoproj-labs to argoproj!

Support

To support this initiative please leave a comment on this issue expressing your support. Alternatively, please use 👍🏻 to showcase support or 👎🏻 to vote against this initiative. If you do not support this initiative please express any feedback you might have!

Sponsors

• @

[JPZ13]

Given how well Hera is maintained and how loved it is by users, I'd suggest graduating Hera and deprecating the Argo Workflows computer-generated Python SDK in favor of Hera

[terrytangyuan]

We will probably need to establish a formal "graduation" process for projects like Hera. There are a couple of other projects that are also "popular" in argoproj-labs and may have similar requests at some point.

[flaviuvadan]

Thanks @terrytangyuan - do you think it's reasonable to evaluate Hera on its own and then derive "graduation" process requirements from this experience rather than make a process first?

[terrytangyuan]

Could you bring this up in the maintainers meeting? It's open to everyone. There's an upcoming meeting next week https://docs.google.com/document/d/1C71GA0XCxsyGP7Q4SYveHak5ZZcJOuaOiDCt_xHG10U/edit#

[flaviuvadan]

Thanks @terrytangyuan added to the March meeting: https://docs.google.com/document/d/1C71GA0XCxsyGP7Q4SYveHak5ZZcJOuaOiDCt_xHG10U/edit#heading=h.y5xnyirokxg4

[terrytangyuan]

Per discussions at the maintainers meeting, we'll discuss this among the Argo project leads and provide a recommendation on how to proceed.

[agilgur5]

For reference, I brought this up at last month's Maintainers meeting and today's Maintainers meeting to get this some traction. See the in-line links for notes there, and I think Argo has recordings somewhere too. Terry has summarized next steps above

[hblixt]

Recommendation to get traction and close this

• Discuss with Argoproj leads and come up with an agreed on solution and plan, the more details the better.
• Bring to maintainer meeting

Once we have a more detailed proposal, it will be easier to make some decisions and move forward.