Skip to content

Latest commit

 

History

History
51 lines (40 loc) · 2.37 KB

CONTRIBUTING.md

File metadata and controls

51 lines (40 loc) · 2.37 KB

Contributing

Here are the contribution guidelines for the TomorrowDevs projects.

Creating new projects

New projects must observe the following rules:

  1. Every problem must have a README.md file explaining:
  2. The problem itself
  3. A reference for the student to some documentation that could help them solve the problem
  4. Every problem must have one category.
  5. Every problem README.md file must implement the template file.

Solving a problem

  1. Solutions must be submitted by opening a pull request. The pull request must observe the following rules:
  2. The branch name should be formatted as solution/<problem-name> for example: solution/binary-search
  3. The solution must be placed inside of a folder using your name or username. Example: micheleriva/solution.js or mitch/solution.js
  4. The solution file must be placed inside the "challenges" folder in the problem subdirectory. For example: /programming-basics/binary-search/solutions/micheleriva/solution.js
  5. Every commit must adopt the conventional commits rules. Learn more here

Before starting any of the tasks in this Learning Path, please READ the following rules

What do you need to start this Learning Path:

  1. A GitHub account
  2. A Local IDE or Editor
  3. Git Environment
  4. A http://toggl.com/ account and Chrome Extension
  5. A Netlify account

Rules that you MUST follow:

  • Create a Github Project connected to the repository
  • Read carefully the task description
  • Analyze the task, and create relative subtasks to track any requirement and knowledge needed
  • Assign an estimate to each created subtask
  • Define a deadline for the main task
  • Provide a Flowchart within the project
  • Where required, involve other members of the community to support you on the development
  • When working on a task, move it to the In progress column and start tracking it
  • After each task completion, move it to the "Done" column and stop tracking it
  • After the main task completion, share the solution (e.g. your GitHub repo) over the community

Following some useful materials for your work:

Git and GitHub configuration and usage

Pseudo Code Methodology