Skip to content
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

Remove cornice.ext & move to a separate org #379

Closed
tarekziade opened this issue Sep 8, 2016 · 3 comments
Closed

Remove cornice.ext & move to a separate org #379

tarekziade opened this issue Sep 8, 2016 · 3 comments

Comments

@tarekziade
Copy link
Contributor

tarekziade commented Sep 8, 2016

Looking at #340 and #373

I am wondering what's the real value of keeping swagger, spore, integration inside cornice. It seems simple enough to have them packaged at PyPI under cornice-xxx and just use them.

Also, maybe we could have cornice becoming a github org and host cornice-related packages alongside the cornice package there, so people can work in their integration there and be part of the Cornice project.

What do you think?

@Natim
Copy link
Contributor

Natim commented Sep 8, 2016

I tend to agree with you on this. It works pretty well like that for kinto. 👍

@leplatrem
Copy link
Contributor

I agree with that!

An alternative to creating a dedicated org -- in case it looks overkill -- would be to have a section in the docs with links to cornice related projects.

tarekziade added a commit that referenced this issue Sep 28, 2016
Removed cornice.ext
@leplatrem
Copy link
Contributor

Done

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

No branches or pull requests

3 participants