Are you writing your own Graveler code, or interested in doing so? To be very clear: If you are a lakeFS user, or if you program inside lakeFS, then you do not care if we do the following. It is only important if you have a copy of any

.proto

file from github.com/treeverse/lakeFS somewhere in your project. Graveler serializes its actual commit and range values using protocol buffers. One constantly annoying factor with protocol buffers is that there is no way to publish them. Instead, most projects just copy them over from their source project. A project called Buf is trying to create a protocol buffer repository (think "NPM for protobufs"); it is now in beta. Would you be interested in consuming protocol buffers from there? Would you trust this project? Thanks!

It seems to be making

proto

files much more shareable. But for now it only supports

golang

natively. They do intend to support `pypi`/`mvn` eventually.

Personally I wouldn't trust a third-party source to generate code: it's reasonably easy to generate code, while there's always a code generator flag with a different value from that third party's, or you want to depend on a different version, etc. Not sure Buf provides much value there. BUT sharing a proto file is really hard, and does not depend in any way on the third party. Buf gives me a lot of value here, which is basically unattainable. E.g. telling a client "download version 0.61.0 of the

.proto

file in the lakeFS repo" makes life really hard for them.