The example repo is using a direct git reference for the dependency to my branch (seen here https://github.com/tobbbles/ory-elixir-example/blob/main/mix.exs#L24) but I'm a bit hesistant to add some docs to the README at this moment in time as there will be a couple of phases 1. Reference my branch to be used directly for testing and validation 2. Merge of the branch to ory/sdk, where then we can update the git reference to reference the official repository, but this wouldn't be the "ideal" published package version (similar to how NPM can reference git repositories, or the npm package repositories) 3. Publishing to https://hex.pm on tagged versions, in which we can provide official guides on adding the dependency, such as: `{:ory_hydra, ">= 0.9.0"} The last phase will likely need some work on the pipelines, and a setting up the Ory organization on Hex, and making sure everything is publishing happily

pinging @famous-art-85498 as you were involved in the PR Looking at the Hex organization setup, perhaps its best to just publish as multiple standalone packages - this seems to be most common in other open source multi-product elixir packages (https://hexdocs.pm/hex/Mix.Tasks.Hex.Organization.html) Lastly the package definition in Mix can take some extra fields, such as license https://github.com/tobbbles/sdk/blob/master/clients/client/elixir/mix.exs#L43 (which will be displayed on the package repository and documentation.) this is currently unset, would we want to make sure Ory clients have the respective license, or would reference to the source code license be enough?

And lastly, looking at the extra fields we could set in the package are links back to the GitHub org (Example from phoenix, a very popular elixir web framework https://github.com/phoenixframework/phoenix/blob/master/mix.exs#L107) openapi-generator doesn't support adding these fields yet (https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator/src/main/resources/elixir/mix.exs.mustache#L40-L46), but perhaps in future if we upstream that change we can introduce it to the ory sdk clients