Problem:
Once a mentor and mentee start a mentorship relationship, they will ideally continue it to perpetuity.
The only thing that might differ is the skills for which this mentorship is occurring.

Solution:
Make the mentor-mentee relationship unique

Problem:
It is best for the local dev setup and the production setup to be as similar as possible.
This means switching from SQLite to PostgreSQL, which we will use in production.

Solution:
Use PostgreSQL in all environments: Dev, Testing and Production

Problem:
A member can take the role of mentor or mentee, but not both

Solution
Enable a member to take on both mentor and mentee roles.
For example, a member might be a mentor on JavaScript but be receiving mentorship on Python

Problem:

• We do not have Continuous Testing for this project, so we cannot know if new code will break the project.

Solution:
Add Continuous Testing with Travis CI

Problem:
There is no way to immediately know the build status of the project

Solution:
Add a build status badge in the README

Problem:
All the environments are sharing a single settings.py file.

Solution
Every environment should have its own settings file, and there should be a base settings file that each environment should extend.
Convert the settings from a module (single file) to a package with the following folder structure:

settings
├── __init__.py
├── base.py
├── local.py
├── prod.py
└── test.py

Problem:
We don't have a document that explains every step of the contribution process
e.g. forking the project, creating a new branch to work on, which branch to submit the pull request against, etc.

This is a good starting point: https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/CONTRIBUTING.md