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

Package distribution #20

Closed
alexei opened this issue Aug 30, 2016 · 10 comments
Closed

Package distribution #20

alexei opened this issue Aug 30, 2016 · 10 comments

Comments

@alexei
Copy link
Contributor

alexei commented Aug 30, 2016

I gather this package is no longer maintained by it's original authors. I think every user would benefit if either Zapier transferred ownership to another developer or one of the contributors (e.g. @DisruptiveLabs) renamed their fork and published it on PyPI.

Thoughts?

@roycehaynes
Copy link
Contributor

@alexei - Are there issues in particular that you want addressed?

@bryanhelmig - Happy to own repo and maintain.

@alexei
Copy link
Contributor Author

alexei commented Aug 30, 2016

We have some issues with messages sent from Live email accounts (I think) that do not get parsed at all. The original message is not quoted in any way (i.e. no >) albeit the headers are included so I guess that's the culprit. I think this DisruptiveLabs@6eac05f addresses that issue.

Besides that, the package published on PyPI hasn't been updated for a while.

@bryanhelmig
Copy link
Member

bryanhelmig commented Aug 30, 2016

Seems like we ought to at least bring in #19.

Also, perhaps it is appropriate for a CONTRIBUTORS.md? Would be happy to take some folks on to help maintain with @roycehaynes (I just (re?) added you @roycehaynes).

@kageurufu would you be open to maintaining?

@kageurufu
Copy link
Contributor

I'd be happy to maintain this if you want

Also @alexei, our fork is currently on pypi as py-email_reply_parser.

@bryanhelmig
Copy link
Member

Awesome, I added you @kageurufu - let me know if you want me to push a new version to PyPi, we can look into some automated way to do that too. (Maybe via Travis? Not sure.)

@kageurufu
Copy link
Contributor

https://docs.travis-ci.com/user/deployment/pypi is an easy way to turn that on, I'll go ahead and close #19, branch our changes seperately from readme/setup.py changes, and create a new PR for that.

@bryanhelmig
Copy link
Member

Awesome!

@alexei
Copy link
Contributor Author

alexei commented Aug 31, 2016

Guys, you are amazing! Thank you for the positive and quick response!

@kageurufu
Copy link
Contributor

v0.5.9 is now deployed on pypi, enjoy!

@alexei
Copy link
Contributor Author

alexei commented Sep 2, 2016

Awesome, thanks!

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

4 participants