Call for maintainers! about open_api_spex HOT 10 CLOSED

I've moved the repo to a new org.
@cstaud and @fenollp are org level owners, so you can add further users/teams as you need.
@fenollp I've added you as an owner on the Hex.pm package, so you will be able to mix hex.publish new package versions - Ideally this could be put in a travis-ci script but I've been doing it manually so far.

from open_api_spex.

@moxley Great to hear, and thanks for the recent contributions.
I've invited you to the organisation, which should allow you to merge PRs, moderate issues etc. 👍

from open_api_spex.

Hi @mbuhot, me and @ThomasRueckert are willing to maintain this project. We would like to move the repo to our team @unifysell.

from open_api_spex.

I'm down to help with this project. I plan on fixing #47 sometime this month too.

from open_api_spex.

Thanks @cstaud, @ThomasRueckert @fenollp and @tapickell.

I was originally thinking to create a new github org for the project, and invite a couple of admins who can then add additional members with commit access.

Would that work for you?

from open_api_spex.

Sure.

from open_api_spex.

Yes, of course. :)

from open_api_spex.

We at github.com/GhostGroup (Weedmaps) are still very much interested in being maintainers or co-maintainers of this repo. We have 15 Elixir developers building JSON-API-complaint APIs, and we are just starting to ramp up adoption of open_api_spex. We have plans to make improvements to the casting and validation part of the package (you've seen the first two PRs so far). These improvements are very important to us, so any leverage you can provide in supporting their integration would be helpful.

from open_api_spex.

Ah so I'm the one with publishing rights. Anyone has a premade script that can publish to Hex on new tags?

from open_api_spex.

Haven’t tried it but looks like it would work: https://elixirforum.com/t/deployment-an-elixir-project-with-using-travisci/4875

from open_api_spex.