-
Notifications
You must be signed in to change notification settings - Fork 425
New directory for community contributions #2167
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D52747159 |
@saitcakmak has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: Establishes the directory structure for BoTorch community contributions, associated notebooks & unit tests. Updates `CONTRIBUTING.md` with instructions on where each type of contribution should be made. Differential Revision: D52747159 Pulled By: saitcakmak
f18661e
to
f89ae71
Compare
This pull request was exported from Phabricator. Differential Revision: D52747159 |
Summary: Establishes the directory structure for BoTorch community contributions, associated notebooks & unit tests. Updates `CONTRIBUTING.md` with instructions on where each type of contribution should be made. Differential Revision: D52747159 Pulled By: saitcakmak
f89ae71
to
43cc481
Compare
This pull request was exported from Phabricator. Differential Revision: D52747159 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this up. Curious why you chose this module structure over a top-level community
folder (where the import path would be botorch.community.acquisition...
rather than botorch_community.acquisition...
). Would this cause any import headaches?
If we keep the current setup, should we rename community_notebooks
to notebooks_community
for consistency?
I've considered both and went with the top-level folder for clearer separation between the two. I am also not a fan of many level deep directory structures, particularly when there's repetition (e.g., we would have
I didn't run into any issues in my testing. The example test & notebooks run fine after
We can, though I like the sound of |
@saitcakmak merged this pull request in ac19e24. |
Summary: Establishes the directory structure for BoTorch community contributions, associated notebooks & unit tests. Updates `CONTRIBUTING.md` with instructions on where each type of contribution should be made. Pull Request resolved: pytorch#2167 Reviewed By: SebastianAment Differential Revision: D52747159 Pulled By: saitcakmak fbshipit-source-id: e65d79d04c66a5a12f5d3c71aaaf001d36c4806b
Summary: Establishes the directory structure for BoTorch community contributions, associated notebooks & unit tests. Updates
CONTRIBUTING.md
with instructions on where each type of contribution should be made.Differential Revision: D52747159