ctaggart / froto

Froto: F# Protocol Buffers
MIT License
146 stars 27 forks source link

new maintainer please #114

Open ctaggart opened 5 years ago

ctaggart commented 5 years ago

With 0.7 shipped, I think it is a good time to look for new project ownership. I am not using this project at work where there is very little chance of switching away from openapi defined json web services to gRPC. For personal projects, I've switched to Rust because of its web assembly support, async support, and a variety of other reasons.

@jhugard, you've contributed most of the current parser and serializer. Would you like me to transfer this repository to you?

@takemyoxygen, what would you like? There is fsprojects as well or other orgs.

takemyoxygen commented 5 years ago

I'm not using F# nor protocol buffers on a daily basis, so I don't want to be an owner of this repo. I guess, transferring it to fsprojects is a good idea.

jhugard commented 5 years ago

TBH, I'm not using Froto, either. Built the parser and serializer for a proof-of-concept a few years ago, but nothing moved forward with the project. I've just been hopping in to fix big issues as they occur...

cboudereau commented 4 years ago

Hi, I think having only a TP for protobuf messages as DTO is ok but adding a real grpc client is a very hot topic for now : https://docs.microsoft.com/en-us/aspnet/core/grpc/aspnetcore?view=aspnetcore-3.0&tabs=visual-studio

I am also interested in having a grpc client (ie : https://grpc.io/docs/tutorials/basic/csharp/ a generated code as opposed to a TP) for fsharp or maybe for csharp (if we produce a generated TP) because:

I am not using grpc on prod not in a daily basis but I wonder if it possible to make a new start of this project by injecting new options like grpc client.

What do you think about this ?

I prefer working with a pair to not be alone on this.

64J0 commented 2 years ago

Any update on this?