-
Notifications
You must be signed in to change notification settings - Fork 829
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
Rename contrib
and sdk_contrib
#1100
Comments
@tylerbenson What IS the intention of those submodules? |
This was explained on a call by @bogdandrutu but I forgot what he said. |
I would love to start transferring some tribal knowledge from peoples head into more readable documentation. I totally feel the pain of new contributor and want to help future generations. So if somebody can explain their meaning to me, I will augment |
For the moment these were the only rules we applied, but based on the specification open-telemetry/opentelemetry-specification#539 we should split the contrib into |
@iNikem you got it :) |
@bogdandrutu but I still don't quite understand what does |
What name do you expect for some utility artifacts? We choose to call them |
E.g. what are criteria for the decision to put some functionality into contrib/util and not into API/SDK proper? If we just say "this is a bunch of utility/helper artefacts", then I am afraid it will become what every |
Talked to Bogdan during SIG meeting and we agreed on the name |
I don't like the names of |
They contain additional, utility functionality that some users may want, while others don't. They are not "contributed" by some external third party, but are maintained by the same "team" (in loos OSS sense of word) as |
I also find the name Maybe |
contrib
is causing a bit of confusion around the intention. Perhaps something likeutil
orext
instead?The text was updated successfully, but these errors were encountered: