Keploy is increasingly looking for new developers to join us and help improve our processes. We are also looking to collaborate on the development of new projects that serve our plan and mission. Please have a look at the following steps to start a new project:
-
Avoid Duplication:
- Before starting a new project, review whether a project based on your idea already exists:
- All projects are listed in the Project tab of the keploy root directory.
- Please also review the existing repositories, as not all may be listed under the "Project" tab.
- If your project idea already exists, please join forces with those already active. Else (if your project does not exist) proceed with the next step.
- Before starting a new project, review whether a project based on your idea already exists:
-
Build on what already exists:
- If you can build on code that is already available, coordinate your project with the maintainers of the relevant repository by requesting a new feature.
- If there is no existing code base to start from, create a repository even if you are not part of the keploy organisation (yet).
-
Create a project board to track and update your work:
- If you are a part of the keploy organisation use the project list under
.github. - If you are not (yet) part of the keploy organisation, use the projects list in your repository. You can notify the wider keploy community by opening an issue under
.githubinforming that you have started a new project.
- If you are a part of the keploy organisation use the project list under
-
Invite your team:
- Invite your team to join the project even if they are not part of the keploy organisation
- Nest your team into the right parent team, which means the repository team for new projects or the keploy team for new repositories
- Assign roles for Developers, Engineers, Editors, Maintainers (for code). Try to have at least 2 persons for each role to avoid overloading your team.
-
Follow the regular project implementation cycle