Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed Typos #55

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

Removed Typos #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ With all that in mind, we're now accepting project proposals,via pull request to

Your first step should be to look over the /proposals/ folder. Not all of those ideas will make the cut; it could be that they are not properly defined, the wrong size, or don't have a mentor, and that makes them less likely to get accepted. We may simply be awarded fewer GSoC slots than we have projects.

We see a lot of questions about what tasks or bugs students can be assigned in the leadup to GSoC, and while we're grateful for the enthuiasm we would like to discourage pepole from taking that approach. While it would be helpful for us to be able to assess applicants' skills ahead of time and we always want to be open to new contributors' help, we don't want to treat our GSOC projects as a prizes you might win if you volunteer hard enough. Asking people to labor performatively is unfair and exploitative, and that is not how we intend to operate or who we want to be.
We see a lot of questions about what tasks or bugs students can be assigned in the leadup to GSoC, and while we're grateful for the enthuiasm we would like to discourage people from taking that approach. While it would be helpful for us to be able to assess applicants' skills ahead of time and we always want to be open to new contributors' help, we don't want to treat our GSOC projects as a prizes you might win if you volunteer hard enough. Asking people to labor performatively is unfair and exploitative, and that is not how we intend to operate or who we want to be.

With that in mind, while we encourage anyone who is interested to take a look at our code, download and build it - please do, that's why it's there! - we believe that your best approach as a GSoC applicant is to use what you learn there to help you *craft an excellent GSOC proposal*, rather than trying to rack up "points" in order to be considered.

Expand Down