yammer->codahale->dropwizard? I'm confused...

[Kevin Burton]

So I can't really figure out what's going on here.

From my perspective, and what I'm interested in, it seems like the 'metrics' component here is itself an important project.

but it's not codahale metrics anymore... right?  It's dropwizard metrics?

I don't see anywhere documenting that it was formerly codahale metrics but not it's dropwizard metrics.  Unless I'm missing it.

And all the package change up isn't' really helping the community.

For example, there's this:

https://github.com/coursera/metrics-datadog

I suspect that it would just work fine on the latest packages.  

But it doesn't support the same package.  It's using the yammer namespace.  So I can't pass it my MetricRegistry... so now I have to fork the whole project.

Can someone explain what's happening?

[Kevin Burton]

Here's an example of why it's confusing:

https://www.datadoghq.com/integrations/

"Submit custom metrics from your Java applications using the excellent Yammer Metrics library. See them in Datadog for graphing, slice-and-dice, and correlation."

which links to.. 

https://github.com/codahale/metrics

... but that actually points to:

"This is not the Java library.

 

https://github.com/dropwizard/metrics"

[Shan Syed]

this project: https://github.com/codahale/metrics is similar but for Go:

"A Go library which provides light-weight instrumentation for your application."

the handy note at the top is probably just for someone that found this repo but was looking for the similarly named Java one instead that was created by the same person

--
You received this message because you are subscribed to the Google Groups "dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Justin Miller]

Too bad it wasn't named "gometrics". :)

On a separate note, who would I talk to about getting involved in
development of Dropwizard. I've read the FAQ but didn't see a point of
contact. I could pick a story off of Github but I wasn't sure what the
highest priority is.

Best,
Justin

[Thomas Sundberg]

On 16 September 2014 02:09, Justin Miller <justin...@gmail.com> wrote:
> Too bad it wasn't named "gometrics". :)
>
> On a separate note, who would I talk to about getting involved in
> development of Dropwizard. I've read the FAQ but didn't see a point of
> contact. I could pick a story off of Github but I wasn't sure what the
> highest priority is.
>

I think you should clone the code, add an improvement or fix a bug and
create a pull request.

I am haven't done it myself due to time restrictions, but that is what
I would do if I wanted to contribute.

Asking for permission to contribute doesn't feel to me as the way forward.

/Thomas

Thomas Sundberg
M. Sc. in Computer Science

Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com/
Twitter: @thomassundberg

Better software through faster feedback

[Justin Miller]

Forget it.

[Nathan Fisher]

There's a dropwizard developers list join there and ask.

Nathan Fisher

 w: http://junctionbox.ca/

[Justin Miller]

Cool, didn't know about the dev list, thanks!

[Ryan Kennedy]

Long story short…metrics and dropwizard both started as Coda's personal projects. At some point they were important enough to the functioning of Yammer that we moved them to com.yammer. Eventually we reached a point where community participation was high enough that it made more sense to re-brand as io.dropwizard and put together a community of committers and maintainers. That brings us to where the projects are at today. I suspect package changing is now a thing of the past now that both projects are squarely in the hands of the community.

As for metrics-datadog, I'd suggest forking and making the necessary changes for compatibility and then sending them a pull request.

Ryan

--

[Ryan Kennedy]

As Thomas mentioned, pull requests are a welcome way of participating. There are 37 open issues in github (https://github.com/dropwizard/dropwizard/issues). If one of those seems important to you or your project, by all means feel free to cherry pick.

As someone else mentioned there's also the dropwizard-dev list. I think both users and dev have been discussing roadmap things of late. One of the big priorities right now is finishing up 0.8.0, which is shaping up to largely be a library upgrade release (new Jetty, new Jersey, new JAX-RS…all stuff we've been lagging on for some time). There are some pull requests mostly ready to go for those. We just need a little bit more sense of urgency to tie off the release and get it into people's hands.

Ryan

[Kevin Burton]

OK... the situation is kind of confusing now.  I would create a page in the about section of dropwizard.io and explain this... and how modules should move to using the right namespace.

It's difficult trying to figure out which one to use... 

Also, this way people can start cutting projects over.

For example.. the metrics-user list doesn't have a mention of dropwizard and that the projects are being moved.

[Ryan Kennedy]

Is the difficulty caused by old modules, blog posts, outside module documentation, or something else?

Ryan

[Tatu Saloranta]

I am not sure this should be particularly confusing: I think Ryan's explanation pointed out which of the variants is the latest; and that is to be moved wherever possible. This is also evident from version numbers, where Maven and Java package name changes did not reset versioning.

So as a rule of thumb, use of variant with highest numbers (and most recent releases) works. I think most developers will be able to follow this simple rule of thumb.

-+ Tatu +-

​

[Kevin Burton]

Sort of... you have to know that the projects are related of course.  And when your'e changing packages you have to dive in and start looking at the classes.

There's nothing that actually says "X became Y which is now called Z"

[Ryan Kennedy]

The reason I ask is because beyond this particular case versioning for modules has been problematic. I.e. How do I know this module is compatible with that drop wizard and vice versa. There are some other discussions in the list talking about that, but I don't remember the conclusions offhand. 

Ryan

--

[Tatu Saloranta]

Right, I am not saying that additional simple documentation would not be beneficial -- it would, and I'm sure a PR would be appreciated -- just that it hopefully is just initial state of affairs. And that once migrations occur, this problem will be history; no new renamings are planned as far as I know.

-+ Tatu +-

--

[Justin Miller]

Agreed. When we started building out the new back-end here, I started
with dropwizard-0.6.2 for the POC but quickly upgraded to 0.7.x. It
sucked, but it wasn't too bad, and I'm glad it happened before we
built out the half dozen services we now have powered by DW.