Recruiting maintainers for django-cors-headers

[ottoyiu]

Hey community,

First off, I would like to apologise for the inactivity of this middleware project. When I first started this small little project in university, I didn't know it was going to be adopted this widespread. I understand with large adoption comes large responsibilities.

I am currently incapable of properly maintaining this project due to two main reasons:

1. I have not been following the Django space, nor worked with it since Django 1.8.
2. Pending paperwork with my current employer to actively work on this project.

With that said, I'm looking for maintainer(s) to take good care of this project in my absence. I have thrown out some invites through the collaboration system in GitHub, to those who have personally contacted me, or have contributed to a fork of this project. Those who accept the invite, I will be in contact to setup PyPi maintainers for this project.

Once again, apologies for the inactivity and I hope the spirit of the open source community can bring this project back to life.

Feel free to contact me if you see yourself a good candidate to be a contributor/maintainer of the project.

Cheers,
Otto

[adamchainz]

Thanks very much @ottoyiu , as one of the maintainers I'll look after it! 😄

[ottoyiu]

Thanks @adamchainz!

[adamchainz]

Hi @edmorley !

[edmorley]

Hi! Delayed reaction (a work project keeping me busy), but happy to help out with ongoing maintenance if needed moving forwards :-)

[adamchainz]

Cool. Well most of the issues are shut now, looking at putting #153 into a 2.0.0 release because it removes the model, a breaking change but I'm pretty sure 99.9% of users aren't using it because it wasn't documented until I added the documentation. Other than that have a few small things to tidy up like #150 .

[kantanand]

@ottoyiu @adamchainz Sorry for delayed reply . i am very happy to help out with ongoing functionalities at my best to contribute .
thanks by lover of Open Source Kantanand US

[mikofski]

Sorry if this is the wrong place this. Can anyone comment on the django-cors-middleware fork. Are there plans to merge the two? Which is recommended? I can't find anything in the documentation that compares them or explains how they differ, although it appears that their version 1.3.1 are not the same commit. Any information would be appreciated.

[adamchainz]

@mikofski would have been better as another issue.

When I came in as maintainer I merged a lot of commits, including most of the unique features in django-cors-middleware. So you should find django-cors-headers adequate. I created #212 to add a little documentation there.

I'm going to close this issue because it's old now and myself and @edmorley are maintaining it.