Skip to content

Commit 40c7643

Browse files
committed
Added contributing guide, this closes #67
1 parent 31d325e commit 40c7643

File tree

1 file changed

+43
-0
lines changed

1 file changed

+43
-0
lines changed

CONTRIBUTING.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Contributing Guide
2+
3+
Thank you for your interest in contributing to PyTorch C++ Tutorials! Before you begin writing code, it is important that you share your intention to contribute with the team, based on the type of contribution:
4+
5+
1. You want to propose a new feature and implement it.
6+
Post about your intended feature in an issue, and we shall discuss the design and implementation. Once we agree that the plan looks good, go ahead and implement it.
7+
2. You want to implement a feature or bug-fix for an outstanding issue.
8+
Search for your issue in the PyTorch issue list.
9+
Pick an issue and comment that you'd like to work on the feature or bug-fix.
10+
If you need more context on a particular issue, please ask and we shall provide.
11+
12+
Once you implement and test your feature or bug-fix, please submit a Pull Request to https://github.com/prabhuomkar/pytorch-cpp.
13+
14+
## Developing PyTorch C++ Tutorials
15+
16+
To develop PyTorch C++ Tutorials on your machine, here are some tips:
17+
1. Install latest CMake from [here](https://cmake.org/)
18+
2. Clone the repository
19+
```
20+
git clone https://github.com/prabhuomkar/pytorch-cpp
21+
cd pytorch-cpp
22+
```
23+
3. Follow the instructions given [here](https://github.com/prabhuomkar/pytorch-cpp#generate-build-system).
24+
25+
## Codebase Structure
26+
27+
- [docker](docker/) - Docker entrypoint and other docker related scripts
28+
- [extern](extern/) - External third-party C++ libraries
29+
- [notebooks](notebooks/) - Interactive tutorials are inside this directory
30+
- [tutorials](tutorials/) - All set of tutorials are here
31+
- [utils](utils/) - Utility functions live here
32+
33+
## CI Failure Tips
34+
35+
Once you submit a PR or push a new commit to a branch that is in an active PR, Travis CI jobs will be run automatically. Some of these may fail and you will need to find out why, by looking at the logs.
36+
37+
Some failures might be related to specific hardware or environment configurations. In this case, if the job is run by TravisCI, make sure you check logs and see the line of failure/error to identify the cause.
38+
39+
## Discussion
40+
41+
If you want to discuss something more in detail, contact:
42+
- Omkar Prabhu - [prabhuomkar](https://github.com/prabhuomkar)
43+
- Markus Fleischhacker - [mfl28](https://github.com/mfl28)

0 commit comments

Comments
 (0)