-
Notifications
You must be signed in to change notification settings - Fork 617
Updated CONTRIBUTION Guide #233
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
|
Check out this pull request on ReviewNB: https://app.reviewnb.com/tensorflow/addons/pull/233 Visit www.reviewnb.com to know how we simplify your Jupyter Notebook workflows. |
|
Hey @amanp592 thanks for starting this. I think we may have had a mis-communication. What we want to do is update CONTRIBUTING.md to explain to users how to create new examples using colab. That mostly my fault as I started that issue discussing notebook templates etc. |
|
@seanpmorgan Sorry for this! i thought it was about notebook template and all, well no worries mistakes happens! Now coming to the main point what i am getting is the Do you want the examples notebook to be colab notebooks and remove all jupyter notebooks and to be converted into colab notebooks?? Please correct me if i am wrong anywhere!! |
|
@amanp592 No worries at all, we can always iterate. So if you create a colab notebook there is a Save to Github option. That is how you can build and test your example on colab and then save the notebook to a branch you have created. The information should be in the example template on tensorflow docs. |
|
@seanpmorgan Thankyou, Now i understood so final words, Update the
Anything else then please specify!! |
|
@seanpmorgan I did as you explained. Please review this and tell me if anything is wrong. |
|
@seanpmorgan all looks good? or we need to change something??? |
seanpmorgan
left a comment
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 @amanp592 ! I've added some comments but I think we're close.
| process can take longer than typical commit reviews so please bare with | ||
| us** | ||
|
|
||
| ## Colab Support |
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.
I would name this section "Contributing Examples" And then add a small blurb about how all examples are built using colab and then saved as .ipynb files in the repo
|
|
||
| 3) Open File->Save a copy in Github. | ||
| 4) Authorize your Colab with Github. | ||
| 5) Save it in the desired branch. |
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.
Close! I think the following steps are needed:
-
Create a branch on your fork
-
Goto colab.google.com and start a new notebook using this template:
https://github.com/tensorflow/docs/blob/master/tools/templates/notebook.ipynb -
Remove the "View on TensorFlow.org Link"
-
Edit the "View source on Github" and "Run in Google Colab" links so that they point to where the link will reside after it's merged into master (e.g. "https://colab.research.google.com/github/tensorflow/addons/blob/master/examples/layers_weightnormalization.ipynb")
-
Install TF2 and tensorflow-addons
!pip install tensorflow==2.0.0.a0
!pip install tensorflow-addons -
Follow the guidelines of the template
-
Save a copy in github on your branch
| All submissions, including submissions by project members, require review. We | ||
| use Github pull requests for this purpose. | ||
|
|
||
| For Visual Diffs we prefer to using [reviewNB](www.reviewnb.com). It Simplifies your Notebook Workflows. |
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.
We can probably just remove this line. It's true but it is generally useful for reviewers and not specific to the Dev Environment.
|
This issue has gotten a bit stale... see #255 . Thank you very much for the contribution though and it was a great start for the updated PR. Please continue to contribute to the repository! |
Fixes #168
@seanpmorgan sir, Please review this!!
If any more changes can be done please point it out!!