-
-
Notifications
You must be signed in to change notification settings - Fork 613
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
Is @Hopding ok? #1616
Comments
Just looked around a little bit, seems like there is no activity anywhere from him. Best chance, someone at GitHub knows whats up, since they are the last employer listed. |
Zero activity on github from him on any repo since 2021. He has a medium.com blog, last post was also 2021. |
He should be fine, since he's active as @andrew-dillon (https://github.com/andrew-dillon). There could be many reasons why he isn't using his old user anymore. |
@ueb375 Are you sure? Could also be the start of the next XZ-Utils situation: Using the identity of someone inactive under a new username to get a head start on trust. |
We're probably the most active maintainers of a fork that you can find here. You can have more details in this discussion: #1631 Unfortunately, I couldn't reach Hopding in order to handle the lifecycle of this project (defining new maintainers, or deprecation + redirection). We'd better acculturate people to slowly switch from one project to the other, unless someone has a better idea. |
What were you trying to do?
The project hasn't been updated in 2.5 years and I haven't seen any activity from @Hopding in any issues or PRs on GitHub in general. I hope that they're alright.
Is there a primary fork & npm package where the project will live on and continue to be updated?
How did you attempt to do it?
What actually happened?
What did you expect to happen?
How can we reproduce the issue?
Version
1.17.1
What environment are you running pdf-lib in?
Node
Checklist
Additional Notes
No response
The text was updated successfully, but these errors were encountered: