in-development-ca / welcome

👋💖🍁 In Development! Start Here!

welcome

In Development! Start Here! 👋💖🍁

In Development is a Canadian Open Source Software Incubator.

We give developers the time and tools necessary to build successful open source projects, promote and support the local open source ecosystem, and build connections between our region and the broader open source world.

• The Plan
• Interested?
  • For Participants
  • For Mentors
  • For Sponsors
• License

The Plan

We are planning a first cohort for six developers, each working on a separate OSS project, together in the same physical space, with their costs of living covered during the duration.

The developer space will also host our mentors, facilitators, and teachers, who will guide the developers through the process of building a successful and sustainable OSS project, by filling in any missing pieces in their knowledge.

We plan to launch the application process during Q3 2017, and to begin the first cohort during Q4, with the second cohort beginning in Q1 2018. The alumni of the first cohort will be involved in the application, selection, and mentoring processes for the next cohort, adding to our organizational strength with each passing quarter.

Interested?

For Participants

Have an early-stage OSS project that you'd like to work on full-time?

Get in touch! For now, open an issue with the name of your project.

For Mentors

Interested in being a mentor? Get in touch! For now, we are publicly accepting mentors via GitHub Issues. Make a PR to add yourself to mentors.md. There's a template in there.

For Sponsors

Our immediate ask is for partners who will sponsor a developer for the first cohort. Estimated cost of living is $4,000 per month, which is $12,000 per developer for one three month cohort. We have space for six of these, and the first sponsors will earn a permanent place in our foundation’s history.

Over the longer term we seek renewable sources of funding, including long-term grants and sponsoring relationships with companies that want to continue to support OSS tool development, building a hiring pipeline for companies that want to support our graduates in doing OSS development internally, and offering open source tools as services and products.

Get in touch: email [email protected]

License

All documents here are under the CC-BY-SA-NC Unported International 4.0 License © 2017 In Development CA

welcome's Issues

Plan for meta-projects

@yogthos commented in the now-deleted minutes repo:

consider facilitating projects that help aggregate libraries into high level stacks, and coordinate between different library maintainers to ensure all the pieces of the stack work well together.

@RichardLitt responded:

This is something like what libraries.io is doing. Unless you mean with specific projects relevant to In Development attendees?

Overhaul the "Volunteer as a Mentor" section

I think I know what I was doing with this, but it hasn't been used by anyone else. This is most likely because 1) we haven't mentioned it 2) the process isn't clear. I think a combination of both.

Integrating this with the website is probably the best way forward. This ticket exists to mention that we need to add a mentor userflow to the website.

Get a second iteration of the logo

I've asked my designer friend Pablo to help with this. He said he'd have the second iterations done by next week. I'll update you all in this issue when we get those, and we can take it from there.

Infosheet feedback

@kvirani wrote:

Things we want to add to the infosheet (discussed by Richard, Dann and KV)

• Add reasons for signing up (why status quo is bad). Research here would be nice
• Rejig so admissions and curriculum are at the end, bringing benefits up a bit as a result
• Add reader persona at beginning (who is this doc for)
• Add a section on the experience that students go through (education delivery). Length, style, format, interaction, philosophy. The main goal of the program and how it helps the participants get there. Half to 3/4 of a page of the document, at most. [=> KV]
• Where will InDev be in 3-5 (or 10) years? Quantify in terms of # of alumni, impact on OSS, impact on communities, etc. Since this is an exercise in marketing (pitching)
  ]
• Add the Ask (need $x of sponsorship) and CTA again to the infosheet (it's in the one-pager) and what they get (tangibles like logo representation).

Note: Richard brought up a good point about adding metrics once we have a cohort or two

Collapse repositories

At the moment, we have five or so documentation repositories with no actual code in them. I wonder; could we just put all of the information in one repository? I don't see a need for lots of repositories right now.

When we have a need beyond document storage, we could split them out again, but for now, collapsing will provide an easy way to work on documents.