Maybe you can ping the author on GitHub? I'm not sure myself, but you're right there should not be two copies.
On Sunday, November 11, 2018 at 3:21:35 AM UTC-8, Tom Wilkie wrote: > > Hello! > > (I'm not that familiar with the situation and couldn't find any previous > discussion of this, sorry if its already been covered. This email is cross > posted to both the opentracing and grpc groups.) > > github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc seems to have been > forked to github.com/opentracing-contrib/go-grpc, and there now seems to > be more activity on the fork than on the original. This is based on a very > small sample size though... > > Its confusing to users to have two copies of the code, so should be either > (a) recognise the fork as the now "official" home, and at least add > something to the README to direct users here or (b) perhaps invite the > maintainer of the fork to the original repo so we can move it along, and > close the fork? > > Either repo seems a reasonable home to me. For reference, here is the > discussion that triggered this email: > https://github.com/cortexproject/cortex/pull/1113 > > Thanks > > Tom > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/484175e7-2a49-4ef1-b04c-9123336efb85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
