Notice: Looking for a new owner about go-micro

[asim]

I will give some thought to the things you've said. I haven't yet made a decision about the direction of the project.

[vtolstov]

this will not work =(...

[jochumdev]

@Davincible
@xpunch

[vtolstov]

I can take it and bring back many improvements to all packages. Mostly Kafka broker, http and grpc clients and servers, tracking across this building blocks and logging.

[vtolstov]

@asim what you think ?

[asim]

So I handed off go-micro to the community last year and did not feel like development was moving fast enough. Ultimately because no one owned it or was paid to work on it, any time invested was ad-hoc. And while that was greatly appreciated, it was not enough for the project to maintain momentum or relevance. I'm happy to accept contributions via PR but ultimately I'm going to find a corporate owner for this project or something sort of community funded organisation so that there can be some full time resource allocation.

[vtolstov]

@asim and so, i propose my account for such stuff. As you remember - i'm working on fintech bank, and now my fork used by 3 big fintech banks (not in Russia). So i'm interesting to move micro forward and have time for it (payed by employer that accept Apache-2.0 contributions).

And also i have own project that needs micro too.

[vtolstov]

i'm own unistack.org domain and my import paths used go.unistack.org

[vtolstov]

so, what the plan?

[asim]

Well there's only 3 options right now. The first, a corporate owner comes and takes it over. That would be a company with enough resources to allocate the time to maintenance and development. The second option is some sort of community maintained organisation that's funded through sponsorship with some full time maintainers. And the third is that I leave it as it is and let people continue to contribute through PRs. Any alternative approach won't really work.

[vtolstov]

so, i have own company that depends on micro and devs that works with issues in micro too.
i have employers that depends on micro and that have team to also fix bugs and improve micro.
what else do you need ?

[vtolstov]

p.s. also i dont change original license =)

[asim]

But it sounds like you are fine doing that with a fork? So I'm wondering what you gain by taking over the project. Also licensing isn't really an issue, it's more a matter of attempting to achieve sustainability. So yes there has been some experimenting with it but as you've done, it's fine to fork and keep going yourself. What I'm looking for is something more mainstream that will build the project and community back up. So I think that requires something a bit different. Your interest is appreciated.

[vtolstov]

I’m not fine with fork, because I need to monitor original repo for changes. I must create a fork because you change license.
So I’m interest to taking over micro and move changes back to original project

[asim]

But why is the original project relevant to your work? If you fork and make the changes you need it effectively becomes a new thing for your own use. Taking ownership of the open source project adds overhead you don't need. Essentially I'm looking for full time ownership and commitment to it's future works. If it's just something you use for your own obligation then you don't have the time commitment not just to write code but to be a steward for the open source aspects such as building community, blog posts, etc.

[vtolstov]

You have docs, for my fork I need to rewrite all, and so I need to duplicate work. Next thing - as you remember I’m put many changes to micro, before you change license.
And as you remember - I have time and experience to support open source communities, answer question and fix bugs.

[asim]

For now what I'm going to do is re-enable GitHub sponsorship for the micro org. I really want this to be a community driven project. In the beginning as the sole maintainer I found it very difficult to sustain the project. VC funding diverged from the goals of the open source. The only clear approach is to make it community driven. So let's see. If people want to sponsor, we'll give them some sort of tiered rights, maintainer access, etc.

https://github.com/sponsors/micro