Create CODE_OF_CONDUCT.md and CONTRIBUTING.md

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [Email Address]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,109 @@
+# 🎇Contributing Guidelines
+
+This documentation contains a set of guidelines to help you during the contribution process. 
+
+I'm happy to welcome all the contributions from anyone willing to add new scripts to this repository. Thank you for helping out and remember,
+**no contribution is too small.**
+
+
+## 💻Before Contributing
+
+Welcome to [sandeep-07/file-manager](https://github.com/sandeep-07/file-manager). Before sending your pull requests, make sure that you **read the whole
+guidelines**. If you have any doubt on the contributing guide, please feel free to reach out.
+
+
+## 🙌Contribution
+
+Any contribution is accepted, from fixing grammatical mistakes to implementing complex scripts. Please read this section if you are contributing your work.
+
+
+### 🔖Steps to Contribute
+
+Following are the steps to guide you:
+
+* Step 1: Fork the repo and Go to your Git terminal and  clone it on your machine.
+* Step 2: Add a upstream link to master branch in your cloned repo
+    ```
+    git remote add upstream https://github.com/sandeep-07/file-manager.git
+    ```
+* Step 3: Keep your cloned repo upto date by pulling from upstream (this will also avoid any merge conflicts while committing new changes)
+    ```
+    git pull upstream master https://github.com/sandeep-07/file-manager.git
+    ```
+* Step 4: Create your feature branch (This is a necessary step, so don't skip it)
+    ```
+    git checkout -b <feature-name>
+    ```
+* Step 5: Commit all the changes (Write commit message as "Small Message")
+    ```
+    git commit -m "Write a meaningfull but small commit message"
+    ```
+* Step 6: Push the changes for review
+    ```
+    git push origin <branch-name>
+    ```
+* Step 7: Create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)
+
+
+### 🔨Note:
+
+> - Do not edit/delete someone else's script in this repository. You can only insert new scripts in this repository.
+
+  > - Give a meaningful name to whatever file or folder you are adding.
+  > - To state an example, folder name should be as "Images" and file name should be "front_image.jpg"
+
+
+## 🔑Guidelines
+
+1. Welcome to this repository, if you are here as open source program participant/contributor.
+2. Participants / contributors have to **comment** on issues they would like to work on, and mentors or the PA will assign you.
+3. Issues will be assigned on a **first-come, first-serve basis.**
+4. Participants / Contributors can also **open their issues**,but it needs to be verified and labelled by a mentor or PA. Please discuss with the team once before opening your issues. We respect all your contributions, whether it is an Issue or a Pull Request.
+6. When you raise a issue, make sure you get it assigned to you, before you start working on that project.
+7. Participants are expected to follow **project guidelines** and [**coding style**](https://google.github.io/styleguide/tsguide.html). **Structured code** is one of our top priority.
+8. Try to **explain your approach** to solve any issue in the comments. This will increase the chances of you being assigned.
+9. Don't create issues that are **already listed**.
+10. Please don't pick up an issue already assigned to someone else. Work on the issues after it gets **assigned to you**.
+11. Make sure you **discuss issues** before working on the issue.
+12. Pull requests will be merged after being **reviewed** by a mentor or PA.
+13. It might take **a day or two** to review your pull request. Please have patience and be nice.
+14. Always create a pull request from a **branch** other than `master`.
+15. Participants / contributors have to complete issues before the decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to 
+another person in the queue.
+16. While making PRs, don't forget to **add a description** of your work.
+17. Include issue number (Fixes:issuenumber) in your commit message while creating a pull request.
+18. Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
+19. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.
+
+
+### 🧲Pull Requests Review Criteria
+
+1. Create New PR.
+2. You must add your script into the respective **places**.
+3. Your work must be original, written by you not copied from other resources.
+5. Follow the proper [style guides](https://google.github.io/styleguide/) for your work.
+
+
+## 📖Resources
+
+1. Markdown : Markdown is a lightweight markup language like HTML, with plain text formatting syntax. 
+  * [Markdown Cheat-Sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)
+
+2. Git : Git is a distributed version-control system for tracking changes in source code during software development. It is designed for coordinating work among programmers, but it can be used to track changes in any set of files.
+  * [Videos to get started](https://www.youtube.com/watch?v=xAAmje1H9YM&list=PLeo1K3hjS3usJuxZZUBdjAcilgfQHkRzW)
+  * [Cheat Sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet)
+
+
+## 🤔Need more help?
+
+You can refer to the following articles on basics of Git and Github and also contact me, in case you are stuck:
+- [Forking a Repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo)
+- [Cloning a Repo](https://help.github.com/en/desktop/contributing-to-projects/creating-an-issue-or-pull-request)
+- [How to create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github)
+- [Getting started with Git and GitHub](https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d4ac6)
+- [Learn GitHub from Scratch](https://lab.github.com/githubtraining/introduction-to-github)
+
+
+## 😇Tip from me
+
+It always takes time to understand and learn. So, do not worry at all. I know you can do this!💪