Skip to content

Team Meeting Notes

Jump to bottom
Aaron Keys edited this page Nov 28, 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/27/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss our Hi-Fi design Figma pages and the needed changes
  • Everyone has the same understanding of our design

Outcomes:

  • Gave everyone an idea of what we'll need to do next

  • Users create posts (craigs list or job post)

  • User is asking other players to play with them.

  • User is like I want this type of player to play with me.

  • The other users look through posts, where they’d go to a game they have in mind and select what game/several games and display them.

  • Select your filters

  • It shows all the post from other users.

  • A group or user can look for people. It doesn’t matter which it is.

  • The looking for post the user is going to be able to post I want to be able to play fortnight at this time.

  • I’m at the us east server. For communication put mic or something.

  • A group of fortnight players are looking to join a squad or a singular fortnight player who’s looking to find the other player.

  • It could be a group of two fortnight players looking for two more.

  • #needOne #need1

  • I just want one other teammate which would be the way to search for players.

  • It may not have to be a game. It could be a genre. We can look at this.

  • Every post should have a time. (not wanting to play with players in 2 days if you’re wanting to play tonight).

  • Tags can be open ended. #maleGamerGroup. #Dusk2 for CSGO. #Deathmatch for CSGO

  • The player’s tab is going to be basically worthless; you’re going to be looking for players for who you know, and the discovery players will be in the post tab.

  • As an aside, we need to replace CSGO to CS2

  • We’re not going to have supported games anymore. The looking for post title is going to be the name of the game they’re playing.

  • When you make an LFG post, it’ll be the tag of the games. It’ll start some of the games beforehand.

  • If someone hasn’t done the game before, they can easily create the game.

  • Create posts, groups, tags, games.

  • Create page you should be able to put your looking for post, groups…

  • User Ebay or a job post site for inspiration.

  • Work From Home Jobs | Monster.com possibly?

  • Create page is going to be all the filters and will have all the customization. Everything you see on the card will be modified and put on the create page. Time, description, whether you want a mic, way to add tags. Title is going to be the name of the game. Search box and start typing.

  • We want it kind of like search games in discovery.

  • Creating games and tags will be simple; one or two textboxes.

  • Input more would be groups and posts.

  • Aaron will need to create a looking for posts.

  • Home tab

  • Free SVG images, no attributes, for the three dots in the social page.

  • Create a wiki for our hi-fi pages. Everyone will put their own pages.

  • Drag and drop to the wiki images.

  • https://capstone.cse.sc.edu/milestone/website/#i-built-a-webapp for home. Go to a website and change it to describe what it’s about. Do a few sentences and do lorem ipsum. After a few sentences this is the forces unite game site where gamers find gamers lorem ipsum.

10/02/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Start discussing requirements
  • Discuss more design
  • Discuss what each person is doing for research

Outcomes: For Requirements:

  • Working on the features on the google spreadsheet found here: https://docs.google.com/spreadsheets/d/14hr0qxg-QrL8ejQyT2BujwWb3aWIbuwfBf6w-od-_Fc/edit?usp=sharing
  • We don’t need an author.
  • Post and group discovery goes under sub sections.
  • Comments on profiles are aspirational. It will be like a review on amazon for a purchase. (Good or bad experience).
  • Do the sub items as individuals and come back later. We’ll focus on the priority of the features later.
  • If we have a reset password feature, we might have to use email/phone number.
  • Evan did an ai thing for the logo.
  • Work on your research milestone.
  • We want to be able to have the sub features done by this weekend.
  • If we need help with react and connecting it to asp.net contact evan.

10/09/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss Requirements and Personal Research Milestone

Outcomes:

10/16/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss Outcomes for Personal Research and Future assignments

Outcomes:

  • Discussed issues that group members had completing Personal Research and how we can overcome them.
  • Discussed Roles for upcoming assignments and possible options for completing the assignments.
  • Two front-end. two backend. 1 person floats between them.
  • Ethan is on backend.
  • James is on backend.
  • Evan floats
  • Aaron backend
  • Jackson on views
  • James, Evan, Aaron Schema & ERD diagrams
  • Ethan and Jackson URL
  • For post service, we’d probably have savePost()
  • Architecture document on a wiki page.
  • Docker? James might make a docker, so we have the same database setup for testing. Have everything running locally, so we have a consistent environment. The database would be one of the bigger things.
  • Run one command and everything starts up because it runs in its own container environment, and you don’t have to update it.
  • Azure has a docker. It might be easier to deploy that way.
  • Contact for coding during the break. Preferred nighttime for coding.
  • Evan might design the models and push it to the repo.

10/23/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss sprints and source control milestone.

Outcomes:

  • Start the project coding this week.
  • @vidal for the poc milestone. Get his approval for removing some of the issues.
  • Split it up and do sprints.
  • Sprint 1 starts today.
  • Set up header.
  • Create a signup and signin page.
  • Add email to signup page.
  • SPA-Single Page application. (Front end stuff)
  • We’ll use local databases for now and set up azure at the end.
  • One person could put it into azure at the end.
  • Do we want to use vite?
  • Npm run build
  • Use vite.
  • Switch from react script to vite.
  • Call api to make an account.
  • Sign in call api and save the token to local storage.
  • Talk to Prof. Vidal for the branch protection stuff.
  • We’ll use jwt tokens if we’re going to do the signin/up in the front end.
  • One person sign in and sign up.
  • Ethan’s doing the switching to vite.
  • James is doing the backend.
  • Jackson is doing the navigation.
  • Aaron Signin
  • Ethan Signup
  • Evan is doing the model/dbcontext and anything else to do with database stuff.
  • One-week sprints at first and then see how it goes.
  • Make a branch for what you’re working on and then make a merge request once you’ve finished.

11/1/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss sprints and Ethical, Legal, Security milestone.

Outcomes:

  • Splitting into three sections.
  • Ethical
  • Legal
  • Security
  • We need to break down what we need to do each week, especially after this milestone.
  • Jackson has Ethical
  • Aaron has legal
  • Security has Evan
  • How members treat each other treat each other for ethical
  • Aaron will look into the material ui licensing.
  • We have a remove function for taking people off our site.
  • Think of privacy in terms of both ethical and legal.
  • For security would be age and location. Hash password into a database, so it’s not plaintext. Authenticated users can access their stuff. All user input shouldn’t be able to do SQL. https://owasp.org/www-project-top-ten/
  • Ethan and James can focus on coding this week.
  • Ethan is waiting on authentication.
  • James is working on authentication now he has to connect to the DB.
  • James will use JWT web tokens.
  • Careful on how we store the information in local storage for security issues.
  • We’ll meet Monday at 6:00 pm from now on.
  • Have the sprints down by Monday every week.
  • Removing issues for PoC that we won’t be doing for the actual PoC milestone, so we’re not dinged on our grades.
  • Main things are chat, authentication, and searching.
  • Filtering and searching are going to be the hardest part.
  • Joining the chat for the post is just joining the chat that’s happening.
  • For learning the coding stuff, https://github.com/SCCapstone/PalmettoProgrammers/wiki/Learning-Resources
  • https://capstone.cse.sc.edu/490syllabus/#you-must-write-code
  • Aaron will create a new issue and @instructors about the coding of JavaScript and C#.

11/27/2023

Attendees:

  • Aaron
  • Ethan
  • Evan
  • Jackson
  • James

Agenda:

  • Discuss sprints and PoC milestone.

Outcomes:

  • Ethan- Sending, list, receiving chat. Make a different navigation bar for when you have an account and when you don’t.
  • Jackson- Searching on the front end and profile when you create an account should be displayed but not change anything yet. Jackson did post displaying.
  • Still need to display profile and posts
  • James-post discovery and list associated posts to the user.
  • Evan is going to be deploying the site to azure. Publish profile.
  • Evan will give us the password after he creates the database.
  • Aaron – connect the posts creation to backend and User Profile.
  • James may do the post discovery or may need help on his depending on how things go.
  • Try to finish it by next Wednesday Dec 6th.
  • Meet up Monday Dec. 4th at 6:15 pm to see where we’re at.
  • https://github.com/SCCapstone/PalmettoProgrammers/issues/71#issuecomment-1775618236
  • https://github.com/SCCapstone/PalmettoProgrammers/milestone/9
Clone this wiki locally