Feature/melchor

Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+gem 'rspec'
+gem 'simplecov'

Gemfile.lock

@@ -0,0 +1,35 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.5.1)
+    docile (1.4.1)
+    rspec (3.13.0)
+      rspec-core (~> 3.13.0)
+      rspec-expectations (~> 3.13.0)
+      rspec-mocks (~> 3.13.0)
+    rspec-core (3.13.0)
+      rspec-support (~> 3.13.0)
+    rspec-expectations (3.13.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-mocks (3.13.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-support (3.13.1)
+    simplecov (0.22.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+      simplecov_json_formatter (~> 0.1)
+    simplecov-html (0.12.3)
+    simplecov_json_formatter (0.1.4)
+
+PLATFORMS
+  arm64-darwin-23
+  ruby
+
+DEPENDENCIES
+  rspec
+  simplecov
+
+BUNDLED WITH
+   2.5.13

README.md

@@ -1,3 +1,51 @@
 # Futbol
 
 Starter repository for the [Turing School](https://turing.io/) Futbol project.
+
+### A 1-2 summary or bullet points outlining your plan for check-ins throughout the duration of the project.
+
+* Meeting in the mornings to discuss our schedules
+* Meeting after class to establish a game plan and decide how we want to work for the day
+
+### A 2-4 sentence summary of your plan for project organization and workflow. This can include bullet points. If you plan to use a project management tool, please include a link to your project board.
+
+* [Jira on Trello for project management](https://tnoblecmd.atlassian.net/jira/core/projects/FGP/board)
+* Morning meetings
+    * Getting together in the morning to update the project board with our next tasks.
+    * Discuss our availability for the day and when we will be online
+* Pull requests
+    * Communicating when a pull request has been submitted
+    * Never merging our own pull requests
+    * At least 2 people review the code before merging
+    * Communicating by leaving comments on the pull requests
+
+### A 2-3 sentence summary describing the different approaches your group discussed for project organization and how you collectively made a decision on which to use.
+
+* Some of the group members have used Trello in the past.
+* Joel used an extention of Trello called Jira and recomended it for its organization tools.
+* Thus the group decided to utilizing the Jira board and update it daily as we progress though the project.
+
+
+### A 2-3 sentence summary describing your approach to the code design.
+
+* Grouping methods together by similar function.
+* Potentially breaking things up into smaller classes.
+    * We will evaluate this more as be begin working on Iteration 2.
+* Deciding to progress when our tests are passing and they are within a good percentage rate, with the ability to revisit and refactor later.
+
+#### Include a link to your initial DTR document and the date it was completed. If you do additional DTRs later in the project, you should link the revised versions here as well with the date. New versions should be listed alongside older versions. Do not delete old DTRs.<br/>
+[DTR Link](https://docs.google.com/document/d/1eRyCmQuAlY8jA7yiepLuJlpfgi4hn2COcAz-tQuNMlQ/edit)
+
+#### Create a section in your README called “Contributors”. List each group member’s name and link to their LinkedIn and Github profiles.<br/>
+
+## Contributors
+
+[Joel's GitHub](https://github.com/jdavalos98)
+
+[Melchor's GitHub](https://github.com/MDelarosa1993)
+
+[Renee's GitHub](https://github.com/Renee-m02)
+
+[Brody's GitHub](https://github.com/BrodyNics77)
+
+[Terra's GitHub](https://github.com/TDManning)

runner.rb

@@ -0,0 +1,15 @@
+require './lib/stat_tracker'
+
+game_path = './data/games.csv'
+team_path = './data/teams.csv'
+game_teams_path = './data/game_teams.csv'
+
+locations = {
+  games: game_path,
+  teams: team_path,
+  game_teams: game_teams_path
+}
+
+stat_tracker = StatTracker.from_csv(locations)
+
+require 'pry'; binding.pry