-
Notifications
You must be signed in to change notification settings - Fork 9
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
create outline of expectation for May 17 meeting #18
Comments
Created the following issues for people to begin working on:
Nice to haves: |
Instead of dictating CSS stuff, inquired to the UI/UX people how they normally prefer to complete this as per this Discord message |
How do we want to split up components? Rock, paper, scissors; vote; draw straws? |
The same way you would normally - from the backlog.
|
Will consolidate code at end of meeting.
Different components should have their own repo issues. This will allow for people to go between break rooms:
The text was updated successfully, but these errors were encountered: