Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Review last week’s progress

  • Review survey results

    • Discuss potential features

  • Assign tasks for next week

\uD83D\uDDE3 Discussion topics

Item

Notes

Last week’s progress

  • Product

    • Survey breakdown

  • Engineering

    • Methods of collaboration with Planner and requirements of features need to be laid out in order for Platform to develop and provide useful services

Survey results

Survey Summer - Spring 2023

  • Analysis

    • How are choices made?

    • Resources used

    • Biggest challenges

  • Features to be built from this

    • New things for both Trends and skedge

    • Tying Trends and skedge together

Engineering work

  • Meeting with Planner to determine collaborative features

    • This week availability

  • NLP sentiment analysis

    • What sources of data would we use? Course evaluations?

    • Likely a backend task, but will require a lot of conversations with them about it

  • Documentation

    • Styleguidist https://react-styleguidist.js.org/docs/documenting

      • The design elements are going to be overhauled by the new features and design stuff, so there’s not much point to working on the documentation if it’s going to change

      • Styleguidist equivalent within skedge?

    • Confluence Onboarding documentation

      • What technologies do we use, what do they do, why do we use them, where to learn about them

✅ Action items

  • William Skaggs set up meeting with Ragini Tiwari (Unlicensed) , should include an engineer, product, and design person from each team
  • William Skaggs work through backlog of Github pull requests
  • @Engineers Create basic onboarding documentation
  • @Engineers NLP feasibility research
  • No labels