in-development-ca / welcome Goto Github PK

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.

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.

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.

@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?

@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