Date

May 12, 2023

 Participants

• @Caleb Lim

• @Jake Spann

• David (add later)

Updates

Updates

Jake: meet Planner, Trends, and Jupiter teams

• Big issues: recruiting people, especially product & design

  • Figure out how to utilize recruits the best

• Integrations

  • Integrate the tech between projects?

  • Nebula Platform

  • People interested in interacting with other teams, but no formal way to do that

  • Add more structure & learning to the projects

• Want to address above over the summer

• Long term

  • Projects are on track to make big progress

  • Trends has big improvements in store

  • Lot of projects want marketing push

• Hope to meet with the rest of the projects soon

• Optimistic with projects

• Biggest problems

  • Recruiting people

  • Educate people to use Nebula tools and processes

• David

  • Make shared meeting notes

  • But also have biweekly meetings to share high level updates

David

• Division stuff aligns with what Jake said

• Want to standardize JIRA usage among teams

• Maybe Jake helps them set up their JIRA workflows

  • Also good to get feedback from past leads

• Last summer, we tried to do too much and not much got done

• Don’t want to over commit to things in the summer

• Component library stuff too big in scope last summer

• Maybe work on component library this summer

  • Integrate towards new design standard

  • If we have component library, then components can be used to incrementally add to projects

• Summer initiative

  • Hilary: design kit

• Above are summer initiatives at a division level

• All agree on Jira setup this summer

• But we need to decide if we can take on the scope we want over the summer

• Goal is to get a few high impact stuff during the summer

• Jake: sgtm!

  • Want to know how much resources we will have over the summer

• David: lots of interest at beginning of summer, but then fizzled out kekw

  • “I have plans Thursday night “

• Jake: feasible to put out an org wide survey over the summer?

  • Ask “do you want to do work over the summer?”

• David: do we want forward movement on projects over the summer?

  • Previous talk was no during the summer

  • Leadership should if we want to work on projects or not during the summer

  • Makes it more clear on what people will do during the summer

• Consensus is prioritize org stuff over the summer

  • Avoid having teams meet on an organized fashion

• Division initiative:

  • Component library: take components from Planner & Platform and throw it into a component library

  • “We won’t be able to convince people to do hours of frontend design in the summer”

• David

  • Also working with Jason on standardizing Github and JIRA

  • Goal of summer initiatives is to set teams up for success for each project

• Caleb

  • Make big list of tasks for projects & divisions

  • Then come as a group and design

• David

  • Prioritize Jira setup - Jake

• Caleb & David: docker discussion that’s not that important xD

• Jake

  • People don’t know what to do when onboarding

  • Should we improve onboarding documentation as solution?

  • David

    • Onboarding is tricky because we’re not sure what we’re aiming to achieve with onboarding

    • Maybe onboarding by division?

• David: talk about onboarding later in the summer

  • But difficult to define everything

    • 1 month long onboarding is like a mini-bootcamp

• David: busy May 19th - June 4th

• Caleb: we have tasks & discussions

  • Should we ask leadership if they have discussion points?

  • David: we decide but ask people / open to discussion

  • Jake: we should say what we think is important

    • BUT important we hear the project leads as well

• Caleb: status onprojects

  • Jake: wrap up conversations w/ project leads

• Caleb: for first leadership meeting, lets have a list of important topics/initiatives for the summer

• Try to define Product & Marketing heads by end of summer

 Goals

 Discussion topics

 Action items

 Decisions

1. Consensus is prioritize org stuff over the summer
   - Avoid having teams meet on an organized fashion
2. Finish talking to project leads / division heads
   - Officers sync up on summer priorities
   - Then hold leadership meeting to get everyone on the same page