Skip to content

Call for maintainers! #48

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

Closed
mbuhot opened this issue Sep 9, 2018 · 10 comments
Closed

Call for maintainers! #48

mbuhot opened this issue Sep 9, 2018 · 10 comments

Comments

@mbuhot
Copy link
Collaborator

mbuhot commented Sep 9, 2018

I'm no longer using swagger in my day job, so I haven't had the need to make many improvements to this package.

If there are any users who are relying on open_api_spex in commercial / production settings that are willing to share in the maintenance of the project, please respond in the comments, or email me ([email protected]).

I'm happy to move this repo to a Github org and share ownership of the Hex package.

cc: @ThomasRueckert @fenollp @slavo2

@cstaud
Copy link
Contributor

cstaud commented Oct 17, 2018

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

@fenollp
Copy link
Contributor

fenollp commented Oct 17, 2018

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

@mbuhot
Copy link
Collaborator Author

mbuhot commented Oct 17, 2018

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?

@fenollp
Copy link
Contributor

fenollp commented Oct 18, 2018

Sure.

@ThomasRueckert
Copy link
Contributor

Yes, of course. :)

@mbuhot
Copy link
Collaborator Author

mbuhot commented Oct 25, 2018

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.

@mbuhot mbuhot closed this as completed Oct 25, 2018
@moxley
Copy link
Contributor

moxley commented Nov 2, 2018

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.

@mbuhot
Copy link
Collaborator Author

mbuhot commented Nov 4, 2018

@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. 👍

@fenollp
Copy link
Contributor

fenollp commented Nov 6, 2018

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

@mbuhot
Copy link
Collaborator Author

mbuhot commented Nov 6, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants