Skip to content

Commit

Permalink
Merge pull request #23 from PixelsCamp/joaobeltrao-patch-1
Browse files Browse the repository at this point in the history
Update APPLY.md
  • Loading branch information
carlosefr authored Sep 12, 2019
2 parents 85ba91d + 5b4030f commit 636e923
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions APPLY.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ A few rules you need to know about Pixels Camp first:
* You can't request for a friend to be accepted, but you can ask your friends to read this document and help with their bios and pitches. Effort and detail counts in our evaluation (quality over quantity).
* Our authentication and SSO is based solely on GitHub APIs, which means you need a [GitHub account][2].

When applying, we're going to ask you some contact information, and two critical free text answers. They are your public bio and your private registration pitch.
When applying, we're going to ask you for some contact information, and two critical free text answers. They are your public bio and your private registration pitch.

On your public bio you should reference who you are, what you do, and how can the community reach you (eg. your blog or twitter profile). Everyone can see this. Think of it as your welcome card.
On your public bio you should reference who you are, what you do, and how the community can reach you (eg. your blog or twitter profile). Everyone can see this. Think of it as your welcome card.

On the *private* registration pitch you should spend some time perfecting your answer. This is where we ask for effort and detail. Think of the private pitch as the place where you describe your history in the tech world to us, your best work and accomplishments, what excites you when you look at the future, your motivation to be at Pixels Camp, and why should we accept your application.
On the *private* registration pitch you should spend some time perfecting your answer. This is where we ask for effort and detail. Think of the private pitch as the place where you describe your history in the tech world to us, your best work and accomplishments, what excites you when you look at the future, your motivation to be at Pixels Camp, and why we should accept your application.

Here's a quick checklist of some of the information we expect to see in your private pitch:

Expand All @@ -24,13 +24,13 @@ Here's a quick checklist of some of the information we expect to see in your pri
* Things you’re interested in;
* Why you want to attend Pixels Camp;
* If you’ve been at previous similar events, what you did there;
* Why should we accept your application.
* Why we should accept your application.

If you haven't already done so in your public bio, the private pitch must include your real identity (i.e. your real name).

**Remember**: We don’t have the bandwidth to go sneaking on your personal webpage or blog looking for information. You have to make it available in your bio or private pitch. Not providing enough information may prevent us from being able to accept your application. On the other hand, providing to much information may also difficult the selection process, so be succint yet complete. 😉
**Remember**: We don’t have the bandwidth to go sneaking on your personal webpage or blog looking for information. You have to make it available in your bio or private pitch. Not providing enough information may prevent us from being able to accept your application. On the other hand, providing too much information may also slow down the selection process, so be succinct yet complete. 😉

The private pitch is **private**. Only a small group of Pixels Camp curators has access to it and it isn't shared with any outside entity (eg. sponsors).
The private pitch is **private**. Only a small group of Pixels Camp curators have access to it and it isn't shared with any outside entity (eg. sponsors).

We hope to see you at the next Pixels Camp. Good luck.

Expand Down

0 comments on commit 636e923

Please sign in to comment.