3/1 Code for Boston agenda

[kevinrobinson]

Trying this out.

Review priorities:

• current: Student profile improvements
• next: Productionize visualizations of academic progress
• after: SPED referral form

Finish what's in progress:

• merge PRs for student profile header with @BWieber (Profile v2 - Improve header styling #93 etc.)
• merge migrations for services with @BWieber (Profile v2 - Allow saving services to the database and rendering them #115 etc.)
• catch up with @erose on newsfeed
• make progress on saving services

Help new folks pitch in:

• Talk about any questions from the project overview
• Help them set up development environment
• Start with Help wanted issues
• Next, help with new pieces of current feature
• After, start with a new feature

cc @alexsoble

[alexsoble]

This looks like a fantastic flow!

[alexsoble]

How did it go at CFB?

[kevinrobinson]

This was a great session!

We made progress on the first two agenda items, but started a few other threads as well.

• @BWieber merged some backend work for saving services and made more progress on styling improvements to the student header
• @eudaimonious started on the SPED referral form feature and made an initial PDF!
• @bw120 made great improvements on improving the styling to the history of behavior incidents
• @sentientmachine made progress on improving the coloring of lines in charts
• @lilybarrett got mostly up and running with her dev environment!
• @johnhrobb and Kemal gave some epic design feedback! capturing that in issues now :)

[kevinrobinson]

@therebelrobot hello over at brigadehub/brigadehub#46, I'm glad this is helpful! Here are some thoughts, would love to hear any input you have. :)

We're trying to keep a flow shipping to users, and that requires full-stack work across product, design and engineering. So far it's been easiest to get contributions on well-defined engineering work, since less context and ramp-up is necessary to contribute there. Good UX and design work often takes a deeper shared understanding, so we've tried to give a first cut at that with a product overview and demo site, and we focus on this rather than the tech stack when introducing the project. Conversations with brand new folks are almost entirely about product and user stories rather than tech, and about communicating the feeling of regularly shipping small features. But this takes time to coordinate, especially for new projects where shaping the user experience is so important. It often takes work to discover clearly-defined engineering tasks.

Anyway, we'd love to learn from you and what works well as you try this out too! :)

[therebelrobot]

👍 For sure! @Judy5000 would definitely be interested in this flow, given her PM background, and as we're building out these initial pieces, demos and product overviews will for sure be handy once we hit beta. I agree that UX and design require a closer understanding, I may pull that from the agenda for now.

Judy, I would love to get your input on this, and see how we can adapt it to brigadehub's needs as we move forward. As this is more of a meta discussion, maybe we can start a new issue on brigadehub for Hack Night meeting structure?

[kevinrobinson]

👍 cool, sounds great!