Skip to content

Team Meeting Notes

Jump to bottom
Evan Scales edited this page Sep 24, 2023 · 34 revisions

Format for Notes

Make sure to include the following when adding new notes:

  • Date (put this in the section header)
  • Attendees
  • Agenda (what we want to discuss/figure out)
  • Outcomes

08/28/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda: We wanted to discuss what technologies we wanted to use or investigate, talk about previous experience with different technologies, assign roles to members, discuss possible application features, and other miscellaneous information.

Outcomes:
Team Name: Palmetto Programmers
Technology we want to use:

  • JavaScript and React for front end
  • ASP.NET backend
  • PostgreSQL and Azure

Application features etc.:

  • Find other gamers to play with.
  • Groups of players looking to play specific games.
  • Carmax/dating site interface/ea games
  • Look for clans/groups/users/friends/looking for group to play a game.
  • Offline/online feature
  • Searching features
  • Need messaging/forum
  • Learn web sockets for the live chat?
  • Favorite games for players
  • Location of servers (US East)
  • Accounts and account creation (looks)
  • Find a group and what it looks like in a group. (looks)
  • What’s it going to look like for people to match?
  • First person to invite to the group is the leader and have a request to join.
  • 50% of group to kick a member
  • What does the group look like?
  • It will have to have a messaging list/system of some sort.
  • C# dictionary for key being the name of the friend on their list and an arraylist for the messages.
  • Start on the backend ASP.NET API first and work on the graphic design after

Roles:

  • Ethan: Master of Front end/Submits
  • Aaron: Master of Back end/scribe
  • Evan: Scrum Master/edit the schedule and deadlines
  • James: Research stuff/review git stuff and “untangle mess”
  • Jackson: Tester

This week: submit teams and form (Ethan is going to submit)

09/05/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss recently opened and closed issues
  • Share findings from any intial light research
  • Discuss next milestone (User personas and stories)
  • Start creating weekly reports
  • Braintstorm any other issues we can create and start work on

Outcomes:

  • How are we going to do the code with Mac, Linux, and Windows OS?
  • Weekly report bundle last weeks work, which is due this week.
  • NPM for react? (package manager for JavaScript)
  • Issues we created and closed.
    • Project description
  • Any other high-level features we want.
  • Merge account management/profile
  • Every competitor app are all mobile apps, because they’re console players that may not have a pc. If you want to support console players, make a mobile app.
  • What’s our market? Focus on indie games?
  • You don’t have to do steam support. Allow users to put what store or game platform they use to be linked under the profile, including your riot/steam id.
  • Are we looking for communities? Is it specific game centered or more general?
  • Research game ticket on github.
    • Add specific roles to games and associate them.
    • Roles in games. We’ll have to support specific games.
  • Target specific platforms.
  • Don’t launch the game from the website.
  • Sign in with steam uses php.
  • Focus on PC
  • Finding teammates to play immediately or a general interest who want to play on the weekend.
    • Should make it general/long term
  • Add a commending system. (reputable)
  • Write personas to think about this more.
  • Do we want to make a friend app or a game app.
  • More casual vs more competitive.
    • Rank on the game could be posted/skill level
  • Parsec low latency screen share.
  • Think of niche markets and more open ended.
  • Let the user choose how to use it.
  • Focus on personas before we design the app!
  • Create an alternative friend finder.
  • Look at the users library and take their meta data.
  • If they like specific genres of game.
  • Do a search with a bunch of users with their name, interests, etc. There would be tiles of the users.
  • Get rid of the 50% kick.
  • This week:
    • Personas
      • One who plays a lot. Tyler Tryhard
      • Plays moderate amount. Gary Gamer
      • Plays casually. Casual Casey. Just Dance game.
    • Learn React
    • Research ASP.Net
    • 9 user stories. 3 different stories or three features/goals they want out of the website.
  • Meet next Monday at 10:00 remotely on discord.
  • Users can search for groups and users
  • Is this group centered around a person you’re looking for.
  • The group is looking for this type of player based on the game.
  • They can make posts for looking for team member
  • Would the group have a page.
  • Public and Private groups.
  • Private won’t be able to view the private.
  • Are we doing it right now or get together for later?
  • Time zones?
  • Image, name, and backstory for each persona
  • 3 people to make the users
  • All of us make 3 stories each.
  • Ethan, Jackson, and Evan, doing personas.
  • Project description. If the teacher is looking at it.
  • After Sept. 10th don’t change the project description until he gives us the grade.
  • Header, navigation, user profile on the right.
  • Next week we’ll do the low-fi

09/11/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Go over our new personas
  • Go over weekly report (09/10/23)
  • Narrow down our top 9 user stories
  • Discuss recent discussions (Gamer Discover, User Stats)
  • Discuss next milestone (Design)

Outcomes:

  • These 9 stories should be the ones we know for sure we’re going to do.
  • What are the users features we want in the app?
  • We’re going through persona and stories.
  • Selected the top 3 stories for each persona.
  • Fix “specific section” and typo in stories.
  • We’ll have to dig in a bit about how we decide to find friends or whether we synchronize with other applications or if we want to do an email invitation or through a recommendation.
  • We agree about stop adding players.
  • We’re good on low-fi, but it would be good to get it started this week.
  • What does the team feature do?
    • Quickly chat with my group mates.
    • Consistent group of people to play with
    • Schedule meetings
  • We’ll make an issue to revamp the top 9 stories on wiki.
  • Design next week.
  • Draw the app out on paper. Diagram it out at some point.
  • Evan will make some issues.
  • All roughly sketch it out. Then we can work out the official design from there.
  • Discuss Gamer Discovery
    • Search for users and groups.
    • Users-filter off age, interests, fav games, tagging system, time-zone, playtimes, skill level (low/beginner, intermediate, pro).
    • Tags like RPG tag? Or tags like on Instagram/twitter (#roblox tag) #2v2 #speicalmode
    • The post feature will have the users and groups as the same function. It’s customizable. You’re searching for a group of 1.
    • Check out GamerLink app screenshots.
    • Group drop listing.
    • Member types: Leader, moderator, group member. Moderator and above can post.

09/18/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Go over our Low-Fi UIs
  • Go over weekly report (09/17/23)
  • Narrow down our UI
  • Discuss recent discussions
  • Discuss next milestones (Research & Requirements)

Outcomes:

  • Use google draw to do UI.
  • Figma free for students on UI.
  • Big companies use Figma.
  • Ethan’s going to put react code in his own branch.
  • Found signal r for live chat with asp.net. Evan’s going to make a test project. He designed a database project for that. Set up a login input too.
  • Ethan will help with the front-end stuff.
  • If anyone wants to clone to repo and tries to run it, you can sign up but to connect to the database look up the old issue for PostgreSQL. You have to use the old commands to set up the PostgreSQL stuff.
  • Wednesday 5:30 Thomas Cooper Library in one of the Technology Room. (4th floor)
  • Going over feedback for Personas Milestone.
  • Next Milestone is Research and Requirements
  • Discussed package manager on requirements.
  • Do we want to do the same project or something similar that relates to our site?
    • Look up a full stack application
    • Milestone: authentication, databases, react, CSS, etc.
  • We will all create a TODO application.
  • Todo app will interact with the database.
  • Don’t worry about C# etc.
  • Folders on GitHub will have our react and API
  • For react redux, it adds another level of complexity. It changes how you store stuff. It’s a way of managing data that James found super helpful. Found it hard to build a huge front end without it.
  • Should we learn typescript?
  • The difference is defining objects.
  • Stick with JavaScript
  • Fullstackopen.com for learning all things react and JavaScript and frontend. It’s separated into modules.
  • We want to focus on the web part of ASP.NET.
  • Web chat demo of Evan’s to get an understanding of ASP.NET.
  • When Evan and Ethan finish, they plan to post it in discord.

09/20/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss our design
  • Everyone have the same understanding of our design

Outcomes:

  • Drew on a whiteboard designing our main pages

09/25/2023

Attendees:

Agenda:

  • Go over any started Figma pages

Outcomes:

Clone this wiki locally