-
Notifications
You must be signed in to change notification settings - Fork 171
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
please help with maintenance or archive this #536
Comments
Folks who can help with this, but currently don't have access to are free to mention in a comment! |
@codefromthecrypt What should be done here? Simply update dependencies? Introduce Typescript? Maybe PNPM? |
then cut a release on typescript I think we already have shims, and I forget what the pros and cons doing everything in that. main thing is to make sure polygot still works and users are keen on change, so any major changes, ping someone on build tool like pnpm, make sure this is done after a release so you are familiar with that. Once you have commits in fixing issues you didn't raise, you'll shortly get karma ;) |
Planning to archive this on July 10 unless someone updates the project to the point where it is releasable again, ideally closing out some user-raised issues along the way. |
@openzipkin/zipkin-js-champions @openzipkin/core we should archive this repo if it isn't updated in the next six months.
The text was updated successfully, but these errors were encountered: