You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the canonical un-versioned (i.e. non-alpha, non-beta) version of the protos recently added uses a package of dev.cel instead of starting with google. I also see that cel.dev is a domain owned by Google (though no addresses are present in DNS yet).
Does this mean that CEL might be moving to its own organization, a la protocolbuffers and grpc?
I ask because I'd like to sync these protos into Buf's BSR. But I'm not sure if I should put them in an organization named google, to match the current GitHub organization that owns this repo, or if I should create something else, like cel, in the event that this repo expects to soon "graduate" to a separate organization.
Can you provide any guidance?
The text was updated successfully, but these errors were encountered:
We have considered the possibility of moving CEL to its own organization, though there is no urgency to move this year. Ideally, we would ensure that CEL can be easily used with alternative type systems (besides proto) before graduating to a more neutral organization.
I noticed that the canonical un-versioned (i.e. non-alpha, non-beta) version of the protos recently added uses a package of
dev.cel
instead of starting withgoogle
. I also see thatcel.dev
is a domain owned by Google (though no addresses are present in DNS yet).Does this mean that CEL might be moving to its own organization, a la protocolbuffers and grpc?
I ask because I'd like to sync these protos into Buf's BSR. But I'm not sure if I should put them in an organization named
google
, to match the current GitHub organization that owns this repo, or if I should create something else, likecel
, in the event that this repo expects to soon "graduate" to a separate organization.Can you provide any guidance?
The text was updated successfully, but these errors were encountered: