community icon indicating copy to clipboard operation
community copied to clipboard

Project Proposal: Feature Flag Semantic Conventions

Open dyladan opened this issue 10 months ago • 7 comments

This proposes a new project to stabilize feature flag semantic conventions. Created as a draft for now while we fill out the rest of the project template.

TODOs:

  • [x] list engineers committed to working on the project
  • [x] list prototype engineers and maintainers committed to review

dyladan avatar Apr 05 '24 21:04 dyladan

@askpt has volunteered to support us from a .NET perspective.

https://cloud-native.slack.com/archives/C06RT64NP37/p1715113701675879?thread_ts=1714057336.076709&cid=C06RT64NP37

beeme1mr avatar May 07 '24 20:05 beeme1mr

As said @dyladan, I would love to be in for that. (OpenFeature TC)

lukas-reining avatar May 09 '24 14:05 lukas-reining

As said @dyladan, I would love to be in for that. (OpenFeature TC)

Awesome thanks. Added you

dyladan avatar May 09 '24 16:05 dyladan

Project leads/sponsors have approved. I can't approve because I opened the PR but to be clear, I do approve.

dyladan avatar May 09 '24 19:05 dyladan

@svrnm

...monitoring to observability

Is this a known preferred naming convention? What about calling it "telemetry" instead, wouldn't that be even more consistent with "OpenTelemetry"?

julealgon avatar May 13 '24 12:05 julealgon

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: dyladan / name: Daniel Dyla (8a3fde585c347a783397bd6525f83b4133819799, 4992147ce2a465e2df9740d62c4a7a7779b396fd, b5cc7f9e25d3d0f3f93e1ddb605a6f7a70e73acc, 3ba6f3e5c6a4e0adfa0a99f256f698e55848c53c, a25a5a43aa47667bcc644e85bbba6168e5a0fb6e, 848a7ca2d4328d4adccab3dccdf4d8cf24a5cc83, 3384555c342105162990bfcbfaee62514b87c4f1, b9f24fd8831d4c954a110cb7ef69ac0cb3ee4ce6, 899b949982061beb0116505e92c8d8656d5fa07d, 68784590afa1b6491521da7ff72bfde7e2d1f11e, 524f4641657b8d181412568828687bfa5b8e3c17, a32c028c5057748572e9f945ce4529fd88d0a3e3, 84b5278a522a3eb4883ad4e54dec08679d1856cf, 2b03d1112d7747b8b621339dc961459c6c91f08b, 349c23bda1b94ac587a279ff5f627498fd7ffe60, 0b2d0f544a3a91ee98c2bfe634256097f4a3531f, 1de0ba365eab1dc4131cc0b1d5b16b26dd80413a, 3a27694358aaa0ab0acc49f59735f1d967b8bd5c, 4c6f66d05cc7c6658cef53ae35ee94755464b536, 61a62bbe957b060c3659e300e79e5949cde28594, 4d2190d524e2295226887aa9b9c990a88660b895, bebde4f3523283a558cf464d323f3debf3ecb7a1, d946f50f1cfb9d49383c793b4e8ee71b4c85c61a, ae1abe50dff48df57248bb5899a32e69fdf09b22, c888b1eb1bdc74c624a55457489079f265eda58d, 344fb4b1060058c2dad9e682e16941489be031b9)

not sure what's causing easycla to fail on some of the commits

dyladan avatar May 21 '24 18:05 dyladan

not sure what's causing easycla to fail on some of the commits

I think the issue are the emails in Co-Authored-by, since this is a new feature in easyCLA to be verified as well, see

https://github.com/communitybridge/easycla/releases

Everyone might need to check if their @users.noreply.github.com address is also covered by the easyCLA

svrnm avatar May 22 '24 10:05 svrnm

not sure what's causing easycla to fail on some of the commits

I think the issue are the emails in Co-Authored-by, since this is a new feature in easyCLA to be verified as well, see

https://github.com/communitybridge/easycla/releases

Everyone might need to check if their @users.noreply.github.com address is also covered by the easyCLA

I just signed in using my @users.noreply.github.com address and primary address. It seems it didn't update automatically.

askpt avatar May 22 '24 11:05 askpt

see https://github.com/communitybridge/easycla/issues/4329

svrnm avatar May 22 '24 11:05 svrnm

/easycla

jarias-lfx avatar May 22 '24 14:05 jarias-lfx