You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note
TL;DR This repo is no longer maintained. Please open all issues and PRs here. The pip package stays the same.
The general situation
As you probably noticed, this repo hasn't been updated for almost 8 months as of today. About the same amount of time Ilya Zhelyabuzhsky, the person responsible, has not been active on Github.
I would also like to thank @2union for sharing the unfortunate news and providing more information via email.
What this means
Since Ilya was the only maintainer of this project and unfortunately also the only one who has push access to this repo, it is not possible to continue the project here as it was before.
But despite the inactivity of the repo, issues were opened and PRs were made, which indicates that this package is still actively used. Personally, I would find it a great pity if the project died and I assume that many other people feel the same way. That's why @johndoknjas (who has been working on the project for a long time as top contributor) and I decided to continue the project on a fork. So in the future, any work on this project will take place in this new repo. This results in some necessary procedures for specific areas.
Issues
Please create all new issues in the new repo.
For the already existing ones, the plan would be to transfer the issues that have not been commented under and therefore can be easily transferred from the person who created them (by copying the issue body into a new issue on the other repo). This way we have the issues where they are solved and the person who opened them will be informed directly when changes are made. If you transfer an issue, please close it here.
For issues, with comments where more than one person was involved, it is a bit more difficult. We will open a corresponding issue in the other repo and link the one from this repo. Then all interested people can also subscribe to the new issue.
We will also comment under all active issues and give more detailed information if necessary.
PRs
Please open all new PRs in the other repo.
We also want to transfer all existing PRs to the new repo and review them. To prevent everyone from having to keep updating their PRs and having to deal with merge conflicts, we want to transfer the PRs one at a time. We will inform all people who have opened PRs (thanks by the way) and ask them to open their PRs for the other repo as well and close them here.
PyPi package
Besides the repo, there is also the official PyPi package, through which pip releases are made. John is already registered there as a helper. However, in order to get all the permissions, we have opened a request to transfer the package and assume that we will then soon be able to publish the releases there and thus the current user base will not have to change anything in their dependencies.
Other
Feel free, if you starred this repo, to star the new repo as well to show that development is going on there from now on.
If you have any questions or suggestions, please comment under this or open a new issue in the new repo.
The text was updated successfully, but these errors were encountered:
The general situation
As you probably noticed, this repo hasn't been updated for almost 8 months as of today. About the same amount of time Ilya Zhelyabuzhsky, the person responsible, has not been active on Github.
Unfortunately, we had to learn that this is because Ilya passed away in July last year. I would like to express my condolences to all his relatives and friends. May Ilya's soul rest in peace.
I would also like to thank @2union for sharing the unfortunate news and providing more information via email.
What this means
Since Ilya was the only maintainer of this project and unfortunately also the only one who has push access to this repo, it is not possible to continue the project here as it was before.
But despite the inactivity of the repo, issues were opened and PRs were made, which indicates that this package is still actively used. Personally, I would find it a great pity if the project died and I assume that many other people feel the same way. That's why @johndoknjas (who has been working on the project for a long time as top contributor) and I decided to continue the project on a fork. So in the future, any work on this project will take place in this new repo. This results in some necessary procedures for specific areas.
Issues
Please create all new issues in the new repo.
For the already existing ones, the plan would be to transfer the issues that have not been commented under and therefore can be easily transferred from the person who created them (by copying the issue body into a new issue on the other repo). This way we have the issues where they are solved and the person who opened them will be informed directly when changes are made. If you transfer an issue, please close it here.
For issues, with comments where more than one person was involved, it is a bit more difficult. We will open a corresponding issue in the other repo and link the one from this repo. Then all interested people can also subscribe to the new issue.
We will also comment under all active issues and give more detailed information if necessary.
PRs
Please open all new PRs in the other repo.
We also want to transfer all existing PRs to the new repo and review them. To prevent everyone from having to keep updating their PRs and having to deal with merge conflicts, we want to transfer the PRs one at a time. We will inform all people who have opened PRs (thanks by the way) and ask them to open their PRs for the other repo as well and close them here.
PyPi package
Besides the repo, there is also the official PyPi package, through which pip releases are made. John is already registered there as a helper. However, in order to get all the permissions, we have opened a request to transfer the package and assume that we will then soon be able to publish the releases there and thus the current user base will not have to change anything in their dependencies.
Other
Feel free, if you starred this repo, to star the new repo as well to show that development is going on there from now on.
If you have any questions or suggestions, please comment under this or open a new issue in the new repo.
The text was updated successfully, but these errors were encountered: