-
Notifications
You must be signed in to change notification settings - Fork 144
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
nginx module #4
Comments
Thanks @seemk for initiating first contribution for this repo :) My suggestion would be to have single mono-repo with below set of sub-directories to start with:
And the under Instrumentation, we can have further:
I do understand it would be difficult to manage them down the line as the contributions increases, and that time we can decide on having CODEOWNERS for each of the contrib directories. This is how it is done in The releases would be source distribution for entire repo. CI would build and test required set of contrib modules, and not everything. @maxgolov There is a PR for initial directory structure raised by you. Would you like to address the comments so that we can merge the changes to get started. |
Meanwhile, I would suggest you to raise a PR as discussed above, and let others comment over there. |
Hi,
I would like to contribute an nginx module which is based on opentelemetry-cpp. Would this repository be the right place?
What would the the directory structure be - each contribution in a subdirectory or would each contrib be a submodule?
With each contrib's code in a separate directory (i.e. a huge monorepo) my hunch is that handling issues might be a bit more complicated down the line. Any suggestions appreciated 🙂
The text was updated successfully, but these errors were encountered: