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

Mark deprecated & archive repo #517

Open
gwern opened this issue Nov 2, 2023 · 3 comments
Open

Mark deprecated & archive repo #517

gwern opened this issue Nov 2, 2023 · 3 comments

Comments

@gwern
Copy link

gwern commented Nov 2, 2023

Development of this package seems permanently abandoned for the past 5 years or so, and it no longer works with Evernote with the latest change of ownership & API changes, AFAICT. The successor everyone seems to be using is the robert7 fork, which has been maintained up until recently and still works with Evernote (as I've verified just now by upgrading). However, people/search engines are still pointing to this repo and the Sourceforge repo (which claims that 20 people are downloading it every week still!).

Considering that, so users don't waste time installing or running or filing more bug reports on an obsolete & abandoned repo, all this should be tidied up & formalized: the README of this repo & the Sourceforge should be updated to point to the robert7 repo, and then repos archived/made read-only.

We salute the codebase & developer for their service all these years to Evernote users like us (ensuring, if nothing else, that there was always a working escape hatch for our notes), and wish them a happy retirement.

@robert7
Copy link

robert7 commented Nov 3, 2023

I did not hear from the original maintainer (Randy Baumgarte) since 2018, so unlikely he will answer.
Unfortunately, I neither have now time to continue development of my fork, but it should work still quite fine.

@gwern
Copy link
Author

gwern commented Nov 3, 2023

(It's my hope that Randy can take a few minutes to properly close down the repo and save himself any annoyance from additional notifications/people bugging him; if he can't, then this issue is still useful because people will click on 'Issues' and see "Mark deprecated & archive repo" at the top of the list and immediately understand the situation.)

@robert7
Copy link

robert7 commented Nov 6, 2023

Yes, that would be nice, but I'm afraid that Randy doesn't respond since years because he is not reachable for what ever reason.

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

2 participants