New Project Step-By-Step

[amaliebarras]

Draft

Intake:

• Create a project-idea issue, link repo in readme
• Create a repo and add tags for
  ** Stack
  ** Status
  ** Needs

Evaluation:

• Someone will evaluate to make sure you’re not doing anything sketchy
• They may point you to another similar project in OA to join
• They may suggest an existing project in the CFA network

Production:

• Leave a comment every time you work on it at an event
• @amaliebarras if you have specific needs

Marketing:

• When your app is ready to use, let the comms team know and they’ll walk you through
  ** Documenting
  *** Github README
  *** Open-Austin.org
  ** Blogging
  ** Sharing on social media
  ** Engaging Open Source community

Figure out where to publish this, new project champ UX.

[amaliebarras]

reference @VictoriaODell 's 6 steps to successful project

reference civic hacking roadmap

[amaliebarras]

Drafting out what this might look like

Feedback needed and appreciated!

[amaliebarras]

assigning this to you @hlupico but I'll myself on to lurk / assist you as called upon

[amaliebarras]

From 3/22

notes from our team conversation

Relevant action items

• Research project drop off, create google doc with status of current repos
• Ideate of names of project phases
• Make edits to our ideas template based on CfD's

[werdnanoslen]

The problem and project definition bits from Mozilla's open leadership training is pretty useful for part 1: https://docs.google.com/presentation/d/1bCOAoLrNtRVuTt0dtOwsnzbclbGTvWUkcdzk-o8iJeM/.

For example, here's the project vision step that is between figuring out what i'm doing and filling out a canvas:

Brainstorm answers to these questions:

• 1. Who you’re working with, or hope to work with
• 2. What you’re doing
• 3. Who you’re doing it for, your audience (may be same as b)
• 4. Why you’re doing this, the impact or change you hope to make

Put your answers together in a short statement:
I’m working with [community, allies, contributors] to [make, build, teach, or do something] so that [audience, end users, consumers, community members] can [do something different, achieve a goal]

Following that, here's the long form description of using their Open Canvas: https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/develop-an-open-project-strategy-with-open-canvas/

Overall, though, I think Mozilla's site for this is fairly comprehensive: https://mozilla.github.io/open-leadership-training-series/

Wanna test it?

[werdnanoslen]

When creating new issues, I suggest we immediately add a "Help Wanted" tag so it can show up here: http://civicissues.codeforamerica.org/geeks/civicissues

And our latest projects with an Open Austin repo should soon show up here: http://brigade.codeforamerica.org/brigade/projects

We can immediately direct people to check these two sites as well as our repos specifically for finding similar efforts. Unfortunately, the issues one is not searchable, but I submitted a PR to fix that. In the meantime, we can fork it to embed on our site, along with an embedded project finder. That would probably be a weekend hack day's worth of work, but it'd translate to more cross-brigade or at least cross-project exploration and (hopefully) collaboration. By the way, this is one practical example of "knowledge matching" I was talking about @amaliebarras

[hlupico]

Thanks Andy - this is awesome!

…

On Thu, Mar 23, 2017 at 10:35 PM Andrew Nelson ***@***.***> wrote: When creating new issues, I suggest we immediately add a "Help Wanted" tag so it can show up here: http://civicissues.codeforamerica.org/geeks/civicissues And our projects with an Open Austin repo should soon <codeforamerica/brigade-information@c3dac48> show up here: http://brigade.codeforamerica.org/brigade/projects With that as a policy, we can immediately direct people to check these two sites as well as our repos specifically for finding similar efforts. Unfortunately, the issues one is not searchable <codeforamerica/civic-issue-finder#30>, and I don't have the dev environment ready to make that change right now. In the meantime, we can fork it to embed on our site, along with an embedded project finder. That would probably be a weekend hack day's worth of work, but it'd translate to more cross-brigade or at least cross-project exploration and (hopefully) collaboration. By the way, this is one practical example of "knowledge matching" I was talking about @amaliebarras <https://github.com/amaliebarras> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#224 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHQpM5eINGsPy4oO6rA9dqvA2-AETGwKks5roznkgaJpZM4MG41G> .

[amaliebarras]

1. @werdnanoslen but what if the project doesn't have an active leader? I worry about asking for help and then not having anyone to guide the team / volunteers. We should only be asking for help on projects that are moving forward / actively being managed IMO... and if not there's that "needs leadership" tag.

I like the idea but that's one issue we've always had, is people coming to hack nights excited to work on project that the champions either don't exist or aren't present to help.

2. Cool! So to clarify, is that what the help wanted tag does? Or did you set up some other configuration to make that happen?

3. Awesome idea, sounds like a great resource for finding forkable projects. Thanks for implementing :)

[werdnanoslen]

just to document here what we discussed yesterday:

scratch the help wanted tag, that project is abandoned by CfA and we can make our own fork for the website. We can choose the labels

[mapineda]

@werdnanoslen there was a need expressed at the previous CHS about projects being tagged with their "tech stack" ie: reactjs, angularjs, angular2, php, mongodb, sql, c#, python etc

Your thoughts?

[werdnanoslen]

Re:@Vickie I should make this into a blog post, and maybe a lightning talk

…

---- Andrew Nelson andyhub.com 832-677-7180 (sent from mobile)

On Jul 6, 2017 20:41, "Marco Pineda" ***@***.***> wrote: @werdnanoslen <https://github.com/werdnanoslen> there was a need expressed at the previous CHS about projects being tagged with their "tech stack" ie: reactjs, angularjs, angular2, php, mongodb, sql, c#, python etc — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#224 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAuouvXn0-vTdpICr13vTS1kWL9DrgH5ks5sLYzQgaJpZM4MG41G> .

[werdnanoslen]

I'm just going to make this the canonical issue for this work and close the others. Here's some related issues:

#237
#235
#233
#224
#218
#215
#69

[werdnanoslen]

I think this has been captured in the new project idea template. We can make new issues targeting more specific outcomes we want, but I think the original intent of this issue has been completed.