Skip to content

Commit

Permalink
fix: guidelines text introduction fix
Browse files Browse the repository at this point in the history
  • Loading branch information
tiagostutz authored Jun 2, 2020
1 parent c61268c commit 14b06b4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion MANIFESTO.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Part of the OSS mentoring journey is based on courses, readings and tutorials on

## Guidelines to make a Poppins project

The guidelines above are just suggestions on how to make your project beginner-friendly, but it is not a golden rule. So, if you already have your own set of practices working, keep doing it.! The important thing here is that the project is focused on mentoring beginners and first-contributors.
The following guidelines are just suggestions on how to make your project beginner-friendly, but it is not a golden rule. So, if you already have your own set of practices working, keep doing it.! The important thing here is that the project is focused on mentoring beginners and first-contributors.

1. Identify your project as a "Poppins project" by placing this badge [![This is a Poppins project](https://raw.githubusercontent.com/bancodobrasil/poppins/master/badge-poppins.svg)](https://github.com/bancodobrasil/poppins) on top of the README. Badge code: `[![This is a Poppins project](https://raw.githubusercontent.com/bancodobrasil/poppins/master/badge-poppins.svg)](https://github.com/bancodobrasil/poppins)`
1. Don't choose critical or "rush scheduled" projects to be a Poppins project. Remember: the focus of the project is the beginners' journey not the release of the software itself.
Expand Down

0 comments on commit 14b06b4

Please sign in to comment.