Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontend Team Meeting Agenda #461

Open
ryanfchase opened this issue Oct 11, 2024 · 5 comments
Open

Frontend Team Meeting Agenda #461

ryanfchase opened this issue Oct 11, 2024 · 5 comments

Comments

@ryanfchase
Copy link
Collaborator

ryanfchase commented Oct 11, 2024

Overview

Meeting agendas, useful links, and action items for the weekly Spacelab Frontend member meetings

Agenda template

Template for weekly meeting's comment

## YYYY-MM-DD - Spacelab Frontend Weekly Meeting

### Topic Requests
Topics that members want to address in this meeting.

### Action Items
Tasks that need to get done for upcoming meetings.

### Resources
Links and references to useful URLs, documents, resources, etc.

### Attendees

- [ ] FJ
- [ ] Alexei
- [ ] Ryan
- [ ] Kausar
- [ ] Brianne

@ryanfchase
Copy link
Collaborator Author

ryanfchase commented Oct 11, 2024

2024-10-11 Spacelab Frontend Weekly Meeting

Topic Requests

  • 1st time intros

Notes

Action Items

Questions for Matt

  • Upcoming task: changing the about page for the spacelab-react page
    • do we need to ask the design team for input?
    • New team members?
    • New history?
    • Is something broken on the About Page's history component? Is something supposed to be sliding? Or is there a carousel
    • We noticed the team listing (Roles) is not mobile-friendly
  • Where our ticketing system lives?
    • potentially?: https://trello.com/b/56OkqE6f
    • What should our priorities be? Is there another list we of tickets that we need to work through?
    • Do we have a team board that we can use? Or should we come up with our own?
  • Does the frontend team responsible for renewing our SSL cert to get https on the website
  • Do contributors need special team permissions? E.g. perhaps our team lead can be given permissions to edit the Github issues, labels, etc

Questions for anyone familiar w/ Exoplanetarium3D

  • noticing we aren't pulling data from any source, just hardcoding the planets
    • What is the plan for data pipeline? How should we begin facilitating this?
  • How do we visualize planets that are in different solar system? On the demo site, we only see a single solar system, and planets that live within that solar system
  • Adding light (thus shadows) to make things more realistic
    • ambient light
    • center-point of light
    • we currently have hemisphere light
    • what is the strategy for coming up with our textures? What aspects are we looking to improve?
      • each planets are not easily distinguishable from each other
  • Where is React website deployed
    • Github Pages

Next Meeting Goals

  • Familiarize with frontend website (About Page)
  • Find out how our data pipeline will look so we can get ready to receive actual data(?)

@fjtria
Copy link
Collaborator

fjtria commented Oct 11, 2024

2024-10-11 - Spacelab All-Team Weekly Meeting

Topic Requests

  • Matt: Project introduction PPT
  • All-team: Informal stand-up

Frontend Notes

  • Overall project goals:
    • Improve Exoplanetarium
      • Data Science team working on database
    • Update the About page
      • Wait on new design from UX/UI
  • New tasks will come from PM and UX/UI
    • Frontend PM incoming
  • Sprint 1 Assignment: work through legacy tickets (GitHub issues)

Action Items

  • Schedule a recurring Frontend meeting
  • Divide legacy tickets to work on
  • Discuss API needs with Backend team

@ryanfchase
Copy link
Collaborator Author

ryanfchase commented Oct 18, 2024

2024-10-18 - Spacelab Frontend Weekly Meeting

Topic Requests

  • review issues
  • collaborate with backend on data pipeline
  • Important: we need some way of viewing the live source code. The spacelab-react repo does not have a CI pipeline, therefore we'll need to go to AWS to view the source code.
    • maybe ask Benny since we know he has access to AWS
    • we know our instance IP is 35.82.90.21, do we need to SSH into this to view source code?
  • Important: Regarding project board + issues
    • we ALL need to be added to the spacelab-react project. nobody can add themselves as assignees
  • Important: schedule time with Matt and at least 1 rep from Frontend to resolve important issues

Action Items

Tasks that need to get done for upcoming meetings.

Resources

No Blog Posts

image

Attendees

  • FJ: fjstria
  • Alexei: Alex-dev7
  • Ryan: ryanfchase
  • Kausar: kakther (might be already set)
  • Brianne: freckledspider

@fjtria
Copy link
Collaborator

fjtria commented Oct 18, 2024

2024-10-18 - Spacelab All-Team Weekly Meeting

Topic Requests

  • Stand-up
  • Sprint 1 conclusion, Sprint 2 introduction

Frontend Notes

  • Roadblock on SSL
  • UI/UX recruitment ongoing
  • AWS region is Oregon
  • April (UX/UI) has made new mockup for About page (they're still polishing)

Action Items

  • Schedule Frontend sync-up meeting with Matt
  • Continue assignment and work on legacy tickets
  • Connect with Backend on API needs (no rush, they need more time)
  • Update About Page (Create tickets, feature branch)
  • Begin looking into Exoplanetarium – UX/UI is beginning work on designs

Resources

  • Check in on UX/UI Slack channel for the latest Figma designs

@fjtria
Copy link
Collaborator

fjtria commented Oct 25, 2024

2024-10-25 - Spacelab Frontend Weekly Meeting

Topic Requests

  • Recap of About Page tasks
  • Recap of Exoplanetarium tasks

Notes

  • Develop starting off of main! There are changes not yet pushed to release branch

Action Items

  • Permissions to GitHub Projects – our perms disappeared and we can't create tasks
  • Once permissions fixed, clean up tickets

Attendees

  • FJ
  • Alexei
  • Gavin
  • Benny (Backend team)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants