#35/README.md

README.md

@@ -13,6 +13,110 @@ A quick reference guide for the **Pythonista** in process of becoming a **Rustac
 
 > [Click to READ https://rochacbruno.github.io/py2rs](https://rochacbruno.github.io/py2rs/)
 
+## Table of Contents
+
+- [:gear: Developer Installation](#gear-developer-installation)
+- [:star: Contribution](#star-contribution)
+
+
+
+## :gear: Developer Installation
+
+**You must have  Git installed in your PC**
+
+1. Clone repo and change into directory
+   ```bash
+   git clone https://github.com/<username>/py2rs.git
+   cd py2rsS
+   ```
+
+   ```# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Sending a Pull Request
+
+Your Pull Requests are always welcome, but, before working on a large change, it is best to open an issue first to discuss it with the maintainers.
+
+When in doubt, keep your Pull Requests small. To give a Pull Request the best chance of getting accepted, don't bundle more than one feature or bug fix per Pull Request. It's often best to create two smaller Pull Requests than one big one.
+
+1. Fork the repository.
+
+2. Clone the fork to your local machine :
+
+
+git clone https://github.com/<your username>You-Dont-Need-JavaScript/.git
+cd You-Dont-Need-JavaScript
+
+
+<!-- #default-branch-switch -->
+
+
+3. Create a new topic branch:
+
+
+git checkout -b my-topic-branch
+
+
+4. Make changes, commit and push to your fork:
+
+
+git push 
+
+## :star: Contribution
+Contributions are welcome 😃. 
+
+
 
 ## Credits