Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Commit

Permalink
Merge pull request #176 from amzn/develop
Browse files Browse the repository at this point in the history
Deploy 0.3.1
  • Loading branch information
zhenwendai authored May 30, 2019
2 parents ef2b128 + 34309c0 commit af6223e
Show file tree
Hide file tree
Showing 73 changed files with 155,713 additions and 715 deletions.
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,13 +26,13 @@ If you're wishing for a feature that doesn't exist yet in MXFusion, there are pr

If you're thinking about adding code to MXFusion, here are some guidelines to get you started.

* If the change is a major feature, create a [design proposal](design_proposal/design_proposal_guidelines) in the design_proposals folder and post it as a PR, optionally with a prototype implementation of your proposed changes. This is to get community feedback on the changes and document the design reasoning of MXFusion for future reference.
* If the change is a major feature, create a [design proposal](docs/design_proposals/design_proposal_guidelines.md) in the design_proposals folder and post it as a PR, optionally with a prototype implementation of your proposed changes. This is to get community feedback on the changes and document the design reasoning of MXFusion for future reference.

* Keep pull requests small, preferably one feature per pull request. This lowers the bar to entry for a reviewer, and keeps feedback focused for each feature.

Some major areas where we appreciate contributions:
* [Adding new Distributions/Functions/Modules](examples/notebooks/writing_a_new_distribution.ipynb)
* [Adding new Inference Algorithms](design_documents/inference)
* [Adding new Inference Algorithms](docs/design_documents/inference.md)
* Example notebooks showing how to build/train a particular model.

If you're still not sure where to begin, have a look at our [issues](issues TODO) page for open work.
Expand Down Expand Up @@ -73,7 +73,7 @@ Before submitting the pull request, please go through this checklist to make the
* Do all public functions have docstrings including examples? If you added a new module, did you add it to the Sphinx docstring in the ```__init__.py``` file of the module's folder?
* Is the code style correct (PEP8)?
* Is the commit message formatted correctly?
* If this is a large addition, is there a tutorial or more extensive module-level description? Did you discuss the addition in a [design proposal](design_proposals/design_proposal_guidelines)? Is there an issue related to the change? If so, please link the issue or design doc.
* If this is a large addition, is there a tutorial or more extensive module-level description? Did you discuss the addition in a [design proposal](docs/design_proposals/design_proposal_guidelines.md)? Is there an issue related to the change? If so, please link the issue or design doc.


## Setting up a development environment
Expand Down
195 changes: 178 additions & 17 deletions examples/notebooks/gp_regression.ipynb

Large diffs are not rendered by default.

Loading

0 comments on commit af6223e

Please sign in to comment.