awesome-python
awesome-python copied to clipboard
Remove abandoned project merchant
What is this Python project?
Remove abandoned project. Looks like it died 8 years, with no contributions since then
What's the difference between this Python project and similar ones?
NA
Anyone who agrees with this pull request could submit an Approve review to it.
Thanks for the quick review!
I think a great awesome list for a programming language is a starting point to find awesome packages that one can use. I don't expect to encounter packages that are dead and cannot be used, I'd call that not so awesome! Or maybe, formerly-awesome or awesome-abandoned-packages.
In this specific case:
- Abandoned 8 years ago - we agree on that
- Outdated - well, the package is for payment integrations, my best guess is that a bunch of those integrations will be entirely broken due to underlying API changes. Let's just say, I won't be using it!
Thanks for the link - though I don't know how it relates. The link is about Github retention policy. I would suggest that the retention policy for awesome software might have some stricter requirements like, the project is maintained, usable and the documentation site doesn't return a 404 e.g. like merchants.
I guess we have different definitions of awesome! Would be good to update the contribution guide as to what criteria should be met for an entry to be removed. Here are some that have been removed on this list, for being abandoned much more recently
- https://github.com/vinta/awesome-python/pull/2297
- https://github.com/vinta/awesome-python/pull/274
@st4r-w4rs what makes this PR different to the above two examples?
Have a good weekend!
Anytime!
I agree with you that their webpage returns a 404 error; however, their main webpage is still up, and their code is available on their GitHub page.
Regarding the term "outdated," I stated that being abandoned doesn't automatically mean outdated. It might be, but it also might not be. So in other words, I neither denied nor confirmed whether it is outdated or not. What I intended to convey is that just because a project is "abandoned" doesn't instantly render it unusable or, in other words, "outdated". If you choose not to use it, that is your decision, but you are free to fork the project and work on its code. That is the spirit of open source, after all... :)
About the link that you don't know how it relates... : Once again, I think was deliberately clear enough earlier to prevent any future disagreement, and yet here we are... So, as I said, the topic is indirect and doesn't directly relate to this specific PR, but in general there is a logical (common sense) interpretation concept related to the topic here (hence the word "indirect").
Yes, we both agree that the contributor guide should be updated to be a bit more specific and straightforward.
@ucg8j, the previous PR acceptances do not change the fact of my own individual position, which I still maintain.
You too have a nice weekend!
Thank you sure did 😉SalinasOn Jan 19, 2024, at 2:13 PM, Vajda Örs @.***> wrote: Anytime! I agree with you that their webpage returns a 404 error; however, their main webpage is still up, and their code is available on their GitHub page. Regarding the term "outdated," I stated that being abandoned doesn't automatically mean outdated. It might be, but it also might not be. So in other words, I neither denied nor confirmed whether it is outdated or not. What I intended to convey is that just because a project is "abandoned" doesn't instantly render it unusable or, in other words, "outdated". If you choose not to use it, that is your decision, but you are free to fork the project and work on its code. That is the spirit of open source, after all... :) About the link that you don't know how it relates... : Once again, I think was deliberately clear enough earlier to prevent any future disagreement, and yet here we are... So, as I said, the topic is indirect and doesn't directly relate to this specific PR, but in general there is a logical (common sense) interpretation concept related to the topic here (hence the word "indirect"). Yes, we both agree that the contributor guide should be updated to be a bit more specific and straightforward. @ucg8j, the previous PR acceptances do not change the fact of my own individual position, which I still maintain. You too have a nice weekend!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Closing this PR as the maintainer @vinta removed this package in a clean up see this commit/diff: https://github.com/vinta/awesome-python/commit/8524f28e77fe169bd248c0a18ea7635ee43d9434#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L524