-
Notifications
You must be signed in to change notification settings - Fork 12
Archive this project #47
Comments
sparkstreaming is pinned mostly to zipkin v1 and no-one is contributing. Others are thinking Flink. Seems a better idea to restart in v2 flink than keep doing drift-driven releases of code that isn't well adopted. Thoughts? See openzipkin-attic/zipkin-sparkstreaming#47
@mansu @naoman @xiaohongxiedaima @devinsba we've had this situation happen with other repositories in the past. Notably the old zipkin-csharp and ui projects. The decision there was to attic the repo, and recognise others can continue in a fork or whatnot. Wanted to ping you directly as you might be the only users of this. I do think that a flink option is promising, and if nothing else gives a chance to redo things for v2. However, history being what it is, such thing should incubate prior to being in the openzipkin main org (be that a contrib or personal module etc). Also, I wouldn't consider making things like finagle-specific helpers knowing we've had no-one help with them. In hindsight, basic scaffolding seems the smartest choice. |
@xoanteis you asked about this here, but unfortunately the repo is dead We will look at re-kicking this off as a flink job, and not in the core org for starters. If interested please monitor here or https://gitter.im/openzipkin/zipkin |
sparkstreaming is pinned mostly to zipkin v1 and no-one is contributing. Others are thinking Flink. Seems a better idea to restart in v2 flink than keep doing drift-driven releases of code that isn't well adopted. Thoughts? See openzipkin-attic/zipkin-sparkstreaming#47
https://github.com/openzipkin-contrib/zipkin-flink for those who wish to follow a successor. Hopefully it works out better. |
There have been no code improvements beyond maintenance for over a year, and almost no activity. We haven't met most promises in the readme and lack of activity suggests that won't happen. Moreover, @narayaruna is using Flink for exactly this use case, and technically it seems a better fit.
Regardless of fit, the act of maintenance comes at a cost of other work, so should be chosen wisely. I think this project should be sent to openzipkin-attic, and whoever wants to continue can on a fork. This will make room for a different approach to solve the more important technical problems.
cc @openzipkin/core
The text was updated successfully, but these errors were encountered: