Skip to content
This repository has been archived by the owner on Apr 3, 2018. It is now read-only.

Archive this project #47

Open
codefromthecrypt opened this issue Mar 29, 2018 · 4 comments
Open

Archive this project #47

codefromthecrypt opened this issue Mar 29, 2018 · 4 comments

Comments

@codefromthecrypt
Copy link

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

codefromthecrypt pushed a commit to openzipkin/zipkin-aws that referenced this issue Mar 29, 2018
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
@codefromthecrypt
Copy link
Author

@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.

@codefromthecrypt
Copy link
Author

Got some offline nods on this:

@llinder

No objections here for sending sparkstreaming to the attic. It was a really neat idea but not something we currently rely on.

@devinsba

I've put our spark stuff on hold for now due to cost/benefit.

@codefromthecrypt
Copy link
Author

codefromthecrypt commented Apr 3, 2018

@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

codefromthecrypt pushed a commit to openzipkin/zipkin-aws that referenced this issue Apr 3, 2018
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
@codefromthecrypt
Copy link
Author

https://github.com/openzipkin-contrib/zipkin-flink for those who wish to follow a successor. Hopefully it works out better.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant