|
| 1 | +# Projects |
| 2 | + |
| 3 | +Projects are at the core of Code for Boston. Our projects vary widely, but all of them have a few things in common: |
| 4 | + |
| 5 | +- They serve a real, documented civic need (we're not in the business of creating solutions in search of problems). |
| 6 | +- We work with an external partner that has the ability to take over ownership of the project when we're done building. |
| 7 | +- We don't build mission-critical infrastructure. Our projects are designed to be proofs of concept, nice-to-haves, experiments, or v1.0 of a longer-term priority our project partner will own. |
| 8 | +- Our projects are open source and mission aligned. |
| 9 | + |
| 10 | +## Typical project structure: |
| 11 | + |
| 12 | +All projects start with a project lead (a Code for Boston volunteer) and an external project sponsor. In some rare cases this can be the same person, but only if the external partner has the capacity to act as a consistent project lead. |
| 13 | + |
| 14 | +Most projects evolve to include multiple sub-teams, often with their own leads. These might include: |
| 15 | +- Front end developers |
| 16 | +- Back end developers |
| 17 | +- Design and user research |
| 18 | +- Data + research |
| 19 | +- And more! |
| 20 | + |
| 21 | +The "average" Code for Boston project takes about 18 months from project kickoff to v1.0 launch, though this can vary quite a lot! Some of our projects continue to be built, improved, and maintained by Code for Boston, but only if there is interest and voluteer capacity to keep working. If there isn't, the project is handed over to the project partner after launch for them to own and operate. |
| 22 | + |
| 23 | +## How to Choose a Project |
| 24 | + |
| 25 | +After Orientation, feel free to sit in on one or more project team meetings to see if the topic is interesting to you, you like the people on the team, and if you can contribute in a way that will fulfil whatever goals you have coming into Code for Boston. |
| 26 | + |
| 27 | +Ask yourself: |
| 28 | + |
| 29 | +- Does the mission interest me? |
| 30 | +- Can I contribute with my current skills? |
| 31 | +- Will I learn something new? (You're not at work! You can use this time to learn something new, not just do the same thing you do in your day job.) |
| 32 | +- Do I enjoy spending time with the other people on the project? |
| 33 | + |
| 34 | +## Where do new projects come from? |
| 35 | + |
| 36 | +Most project ideas are submitted using the [New Project Idea submission form linked at the bottom of this page](https://codeforboston.org/projects/). Occasionally, the Code for Boston core team will solicit projects from our contacts in Local and State government, or from local community-based organizations. If you have an idea but you're not sure where to start, the Code for Boston core team is always happy to help refine ideas and point you in the right direction! |
| 37 | + |
| 38 | + |
| 39 | + |
0 commit comments