Transfer zerologr to go-logr organization

[hn8]

https://github.com/screenleap/zerologr/tree/master

[hn8]

@thockin @pohly Moved most logic of zerologr to zerolog. Now, it is less than 100 LoC, minimal maintenance needed. Would you please consider hosting zerologr under go-logr? Will love to help maintaining with PRs in the future. Thanks!

[thockin]

I'm not hard against it, but I have a small worry that I end up putting myself into a flow I have no real context for. Why is this better?

Also, see go-logr/zapr#43

[hn8]

@thockin Totally understand your concern. Zap and Zerlog are popular alternatives for JSON logging. Originally we tried Zapr because it looks like the "official" implementation (being part of go-logr). If Zerologr is part of go-logr, I can convert 2 open source projects to use it (instead of my own repo). Zerologr's LoC is minimal, and I would love to help maintain it if you don't mind. Thanks!

[pohly]

My two cents: I don't know much about zerolog. It seems to be used less than zap (imported by is 3,952 vs. 24,820 according to pkg.go.dev). But it looks like a well-maintained project and as you did the direct comparison and found zerolog to be more suitable, I thing we should consider it.

The question "inside go-logr or elsewhere" boils down to maintenance. Loggers are not automatically becoming "official" just because they are hosted here, it just means that a certain set of people (recently mostly Tim, now also me) promise to maintain them.

As you have offered to help with that part, I'm inclined to include zerologr under go-logr.

[hn8]

Thanks! I tried to optimize Zapr initially, but Zerologr is always 2-3x faster on benchmark. I suspect the main difference is how Zap passes variadic argument spread down in call stack. I can help maintain both Zerologr and Zapr since those two are used by pion/ion-sfu and livekit.

[hn8]

@thockin @pohly I have added you as Admin role of Zerologr. Would you please try transfering repo if possible?

[thockin]

OK, I'll give it a shot