Project Proposal: Feature Flag Semantic Conventions

[dyladan]

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:

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

[beeme1mr]

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

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

[lukas-reining]

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

[dyladan]

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

[svrnm]

LGTM overall, some wording suggestions (transaction to trace, monitoring to observability)

[julealgon]

@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"?

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dyladan / name: Daniel Dyla (8a3fde5, 4992147, b5cc7f9, 3ba6f3e, a25a5a4, 848a7ca, 3384555, b9f24fd, 899b949, 6878459, 524f464, a32c028, 84b5278, 2b03d11, 349c23b, 0b2d0f5, 1de0ba3, 3a27694, 4c6f66d, 61a62bb, 4d2190d, bebde4f, d946f50, ae1abe5, c888b1e, 344fb4b)

[dyladan]

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

[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

[askpt]

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.

[svrnm]

see communitybridge/easycla#4329

[jarias-lfx]

/easycla