Add an explanation of how our nonprofit projects work #7158
+73
−0
8 participants
QuincyLarson
commented
BerkeleyTrue
and 1 other
commented on an outdated diff
server/views/resources/how-nonprofit-projects-work.jade
| @@ -0,0 +1,47 @@ | ||
| +extends ../layout | ||
| +block content | ||
| + .col-xs-12.col-sm-8.col-sm-offset-2.col-md-6.col-md-offset-3 | ||
| + html. | ||
| + <h2 class='text-center'>How our Nonprofit Projects Work</h2> | ||
| + <hr> |
|
Because we're getting ready to move to React and there's no point in using Jade if we'll just have to move it back to HTML. I've been using HTML in a lot of the text heavy static views for this reason. That's not necessary. We should stick with jade unless there is some other reason.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
|
CodeNonprofit
commented
@BerkeleyTrue It's important that we get this up sooner than later, as this document is the one source of truth for all nonprofit related Q&A.
SaintPeter
and 1 other
commented on an outdated diff
server/views/resources/how-nonprofit-projects-work.jade
| + <p>You’ll continue to work on nonprofit projects until you’ve built a sufficiently impressive portfolio and references to start your job search. Your portfolio will ultimately have four nonprofit projects. We estimate that the 800 hours of nonprofit projects and 80 hours of interview prep you’re going to complete, in addition to the 1200 hours of challenges you’ve already completed by this point, will be more than enough to qualify you for your first coding job.</p> | ||
| + <h3>Your first Nonprofit Project</h3> | ||
| + <p>We generally scope Nonprofit Projects to 200 hours, or about 10 weeks at 20 hours per week of development per camper. These are only rough estimates. You’ll only work on one project at a time.</p> | ||
| + <p>You will choose another camper to partner with on this projects. You should choose your pair based on:</p> | ||
| + <p>Your estimated time commitments (10, 20 or 40 hours per week) Your time zones (Will you be able to pair program together?) Prior coding experience (we’d like both campers to be able to contribute equally) Do not take age or gender into account. This will provide you with valuable experience in meshing with diverse teams, which is a reality of the contemporary workplace.</p> | ||
| + <p>Then, you’ll email <a href="mailto:team@freecodecamp.com">team@freecodecamp.com</a> with:</p> | ||
| + <ol> | ||
| + <li>Names</li> | ||
| + <li>Contact information</li> | ||
| + <li>Links to each of your Code Portfolios</li> | ||
| + <li>Timezones</li> | ||
| + <li>Hours pledged per week</li> | ||
| + </ol> | ||
| + <p>We’ll send you a list of 3 nonprofit projects that need your help, and together you will choose one to begin work on. While you do this, our team will code review each of your Code Portfolios to ensure all user stories have been completed, and that there are no signs of academic dishonesty.</p> | ||
| + <h3>Beginning the Project</h3> | ||
| + <p>We’ll set an initial meeting with representatives from Free Code Camp, the two campers, and the stakeholder. If the stakeholder and both campers shows up promptly, and seem enthusiastic and professional, we’ll start the project. This lengthy process serves an important purpose: it reduces the likelihood that any of our campers or stakeholders will waste their precious time.</p> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
|
SaintPeter
commented on an outdated diff
server/views/resources/how-nonprofit-projects-work.jade
| + <p>Then, you’ll email <a href="mailto:team@freecodecamp.com">team@freecodecamp.com</a> with:</p> | ||
| + <ol> | ||
| + <li>Names</li> | ||
| + <li>Contact information</li> | ||
| + <li>Links to each of your Code Portfolios</li> | ||
| + <li>Timezones</li> | ||
| + <li>Hours pledged per week</li> | ||
| + </ol> | ||
| + <p>We’ll send you a list of 3 nonprofit projects that need your help, and together you will choose one to begin work on. While you do this, our team will code review each of your Code Portfolios to ensure all user stories have been completed, and that there are no signs of academic dishonesty.</p> | ||
| + <h3>Beginning the Project</h3> | ||
| + <p>We’ll set an initial meeting with representatives from Free Code Camp, the two campers, and the stakeholder. If the stakeholder and both campers shows up promptly, and seem enthusiastic and professional, we’ll start the project. This lengthy process serves an important purpose: it reduces the likelihood that any of our campers or stakeholders will waste their precious time.</p> | ||
| + <h3>Nonprofit Stakeholders</h3> | ||
| + <p>Each nonprofit project was submitted by a nonprofit. A representative from this nonprofit has agreed to serve as a “stakeholder” - an authorative person who understands the organization and its needs for this particular project.</p> | ||
| + <p>Stakeholders have a deep understanding of their organizations’ needs. Campers will work with them to figure out the best solutions to these needs.</p> | ||
| + <p>When you and your pair partner first speak with your nonprofit stakeholder, you’ll:</p> | ||
| + <p>talk at length to better understand their needs. create a new Trello board and use it to prioritize what needs to be built. and establish deadlines based on your weekly time commitment, and how long you think each task will take. Ideally, we’ll scope each project to be completed in 10 sprints. It’s notoriously difficult to estimate how long building software projects will take, so feel free to ask our volunteer team for help.</p> |
|
This paragraph is missing proper capitalization and has several grammar errors. Periods should be commas?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
|
SaintPeter
and 1 other
commented on an outdated diff
server/views/resources/how-nonprofit-projects-work.jade
| + <li>Links to each of your Code Portfolios</li> | ||
| + <li>Timezones</li> | ||
| + <li>Hours pledged per week</li> | ||
| + </ol> | ||
| + <p>We’ll send you a list of 3 nonprofit projects that need your help, and together you will choose one to begin work on. While you do this, our team will code review each of your Code Portfolios to ensure all user stories have been completed, and that there are no signs of academic dishonesty.</p> | ||
| + <h3>Beginning the Project</h3> | ||
| + <p>We’ll set an initial meeting with representatives from Free Code Camp, the two campers, and the stakeholder. If the stakeholder and both campers shows up promptly, and seem enthusiastic and professional, we’ll start the project. This lengthy process serves an important purpose: it reduces the likelihood that any of our campers or stakeholders will waste their precious time.</p> | ||
| + <h3>Nonprofit Stakeholders</h3> | ||
| + <p>Each nonprofit project was submitted by a nonprofit. A representative from this nonprofit has agreed to serve as a “stakeholder” - an authorative person who understands the organization and its needs for this particular project.</p> | ||
| + <p>Stakeholders have a deep understanding of their organizations’ needs. Campers will work with them to figure out the best solutions to these needs.</p> | ||
| + <p>When you and your pair partner first speak with your nonprofit stakeholder, you’ll:</p> | ||
| + <p>talk at length to better understand their needs. create a new Trello board and use it to prioritize what needs to be built. and establish deadlines based on your weekly time commitment, and how long you think each task will take. Ideally, we’ll scope each project to be completed in 10 sprints. It’s notoriously difficult to estimate how long building software projects will take, so feel free to ask our volunteer team for help.</p> | ||
| + <p>You’ll continue to meet with your stakeholder weekly using the conference software GoToMeeting. You will also correspond with the team on the project’s Trello board.</p> | ||
| + <p>Getting “blocked” on a task can take away your sense of forward momentum, so be sure to proactively seek answers to any ambiguities you encounter.</p> | ||
| + <p>Ultimately, the project will be considered complete once both the stakeholder’s needs have been met, and you and your pair are happy with the project. Then you can add it to your portfolio!</p> | ||
| + <h3>Working with your Pair</h3> |
|
Is it really common to say "Pair" as opposed to "Partner"? This usage makes the following paragraphs awkward. "pair with your pair", etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
|
SaintPeter
commented on an outdated diff
server/views/resources/how-nonprofit-projects-work.jade
| + <h3>Beginning the Project</h3> | ||
| + <p>We’ll set an initial meeting with representatives from Free Code Camp, the two campers, and the stakeholder. If the stakeholder and both campers shows up promptly, and seem enthusiastic and professional, we’ll start the project. This lengthy process serves an important purpose: it reduces the likelihood that any of our campers or stakeholders will waste their precious time.</p> | ||
| + <h3>Nonprofit Stakeholders</h3> | ||
| + <p>Each nonprofit project was submitted by a nonprofit. A representative from this nonprofit has agreed to serve as a “stakeholder” - an authorative person who understands the organization and its needs for this particular project.</p> | ||
| + <p>Stakeholders have a deep understanding of their organizations’ needs. Campers will work with them to figure out the best solutions to these needs.</p> | ||
| + <p>When you and your pair partner first speak with your nonprofit stakeholder, you’ll:</p> | ||
| + <p>talk at length to better understand their needs. create a new Trello board and use it to prioritize what needs to be built. and establish deadlines based on your weekly time commitment, and how long you think each task will take. Ideally, we’ll scope each project to be completed in 10 sprints. It’s notoriously difficult to estimate how long building software projects will take, so feel free to ask our volunteer team for help.</p> | ||
| + <p>You’ll continue to meet with your stakeholder weekly using the conference software GoToMeeting. You will also correspond with the team on the project’s Trello board.</p> | ||
| + <p>Getting “blocked” on a task can take away your sense of forward momentum, so be sure to proactively seek answers to any ambiguities you encounter.</p> | ||
| + <p>Ultimately, the project will be considered complete once both the stakeholder’s needs have been met, and you and your pair are happy with the project. Then you can add it to your portfolio!</p> | ||
| + <h3>Working with your Pair</h3> | ||
| + <p>You and your pair will pair program (code together on the same computer virtually) about half of the time, and work independently the other half of the time.</p> | ||
| + <p>Here are our recommended ways of collaborating:</p> | ||
| + <p>Gitter has robust private messaging functionality. It’s the main way our team communicates, and we recommend it over email. Trello is great for managing projects. Work with your stakeholder to create Trello cards, and update these cards regularly as you make progress on them. Screen Hero or Team Viewer - These are the ideal way to pair program. Tools like TMUX are good, but difficult to use. We discourage you from using screen sharing tools where only one person has control of the keyboard and mouse - that isn’t real pair programming. Write clear and readable code, commit messages, branch names, and pull request messages.</p> | ||
| + <h3>Hosting Apps</h3> | ||
| + <p>Unless your stakeholder has an existing modern host (AWS, Digital Ocean), you’ll need to transition them over to a new platform. We believe Heroku is the best choice for a vast majority of web projects. It’s free, easy to use, and has both browser and command line interfaces. It’s owned by Salesforce and used by a ton of companies, so it’s accountable and unlikely to go away.</p> |
|
I take it you mean free to develop on. It shouldn't be free to host on and there are limitations to how long the app can be active per day on the free plan.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
|
There is at least one paragraph with grammar errors I just can't overlook.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.