-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Acknowledgements #122
Comments
I suggest we leave this open for some days/weeks, then I'll create a PR based on the outcome. |
I confirm. Thanks! |
Jonathan Mace contributed to the initial baggage concepts that preceded the w3c spec, so you may want to add him as well. |
@JonathanMace Do you consent to being mentioned in the acknowledgement section of the W3C baggage specification, as you came up with the idea originally? (Context: some people that have contributed to W3C working groups in the past do no longer want to be associated with it any longer for various reasons, so we now always ask for consent before crediting someone). |
Sure thing, I appreciate the mention! |
As we are approaching CR for this spec, we should acknowledge people that have contributed significantly to this spec, similar to https://www.w3.org/TR/trace-context/#acknowledgments.
This will be simple list of names in the form of:
Note: No one will be mentioned without having provided explicit consent to being mentioned. If you are fine with being listed in the acknowledgements section, please confirm yourself in the list.
Just from doing a bit of simple statistics via
git shortlog --summary --numbered --email
, I think the following people should be credited (alphabetical order).This is very probably not a complete list. If you can think of someone else that should get credited, please comment. That also includes non-code contributions, which I have completely missed when compiling this list.
cc @SergeyKanzhelev just FYI
The text was updated successfully, but these errors were encountered: