Because there is currently a limit of 60 calls per hour per IP address I want to add authentication to allow the use of authentication.

I want a user to be able to create an event, this event would list out prizes, a description, time frame for points, eligible users.
This specifically is what I want to use when going back to Newtown to help encourage git contributions among those students.

Test Driven Development

I know I should care more about following the practices I'm taught. So I would like for this to have working tests with both Travis and Circle.

Test only PHP 5.6+ as I do not care about systems running 5.4 and 5.5

Since my original intent was for this program to be used as a sort of education tool. I want to build out a bit of documentation about how to use git/GitHub to allow this to be easily deployed for educational purposes.

I am new to Travis. But I now have it set up for this project. Now it's just a matter of getting the builds to pass. I'm new to this en-devour and will be looking for help to get this working.

Allow the user of the application to set their own point scaling:

• Added
• Removed
• Challenges
• Commits
• Etc.

Currently if you change the weight of a score value, the breakdown gets broken. I should calculate the total score on display instead of storing it in the DB

SQL Data isn't being stored as it goes down the looping structure.
Tables are created properly and connecting to the database works, however I can't seem to INSERT data.
Look into debugging why this isn't working.

Display in the profile a breakdown of:

• Added Lines
• Removed Lines
• Challenges

In the JSON per commit there is a field for:

"author": {
    "login": "clockfort",
    "id": 57031,
    "avatar_url": "https://avatars1.githubusercontent.com/u/57031?v=3",
    "gravatar_id": "",
    "url": "https://api.github.com/users/clockfort",
    "html_url": "https://github.com/clockfort",
    "followers_url": "https://api.github.com/users/clockfort/followers",
    "following_url": "https://api.github.com/users/clockfort/following{/other_user}",
    "gists_url": "https://api.github.com/users/clockfort/gists{/gist_id}",
    "starred_url": "https://api.github.com/users/clockfort/starred{/owner}{/repo}",
    "subscriptions_url": "https://api.github.com/users/clockfort/subscriptions",
    "organizations_url": "https://api.github.com/users/clockfort/orgs",
    "repos_url": "https://api.github.com/users/clockfort/repos",
    "events_url": "https://api.github.com/users/clockfort/events{/privacy}",
    "received_events_url": "https://api.github.com/users/clockfort/received_events",
    "type": "User",
    "site_admin": false
  }

Use this data instead of Email as the unique identifier

Show the point weights to help explain the score breakdown somewhere on the page

Store the Sha of the commits counted so that there are less API calls per update

Keep Statistics on:

• How many contributors there are
• How many repositories have been scanned
• How many commits have been counted in total
• Total line count (added/removed)

Create a system that allows there to be challenges in the database and for challenges to be assigned a point value.
Unlikely to be counted through the API, likely manual point assignment

Some of the Users committing have multiple emails attached to their commits. So it causes them to have multiple entries in the database and splitting their score. I'm curious as to how I could deal with these conflicts non-manually.

If a Repository is a Fork, don't add new users, just count existing ones from DB

I want to get this app to a stage where it's even easier to deploy. With that in mind I want to look into how to containerize this application for deployment on something like Open-Shift.

Allow the setup to determine whether it's a sign up system, or whether it wants to add new users to the system on first pool.

Use SQL to Store Participating Users

Right now when you load the page it first runs all the queries before loading up the leaderboard. All the data needed to show the leaderboard is in the database already. So all API calls should be made after all the relevant data has been loaded in. Then on refresh again all the new data will be filled.
This could be solved by simply moving the large PHP loop below the "statistics" section and printing debugging code to a "debugging" section that only shows when debugging is set to ON

Include issues just like commits in point add up/breakdown.

• Worth 25pts Default

Create a user profile to show where all the points have come from towards their placement on the leader-board. Since breakdown mostly does this it would likely show all repositories and the breakdown of those towards the final score.

Use GitHub API to grab and Store Data

Grab Commits: https://api.github.com/repos/NHSTechTeam/Calendar-Maker/commits/dcad3fb6cce3e22fa940cd4a13369820e6f789ec

Move assets to Bower in order to "properly" set up the repository

Weight Pull requests separate from issues and give each type a weight:

• Merged: 50
• Closed: 0
• Open: Skip and wait

Currently I'm accounting for maxing out API calls by setting a maximum amount of API calls per load. However that doesn't account for someone refreshing twice in an hour with a max cap. Or for setting the max cap past GitHub's max cap.
I want to:

• Handle "Maxed Out" JSON Returns
• Keep Track of API calls per Hour in Database and set a Global Cap

Count the number of commits per user. Include that in score and point breakdown.

Create methods to "de-blob" the program, using inheritance or importing
Create Methods:

• Leaderboard Printouts
• Statistics

Internal Methods:

• Add New User
• Alerts (Success, Info, Warning, Danger)
• Database Connection and Initialization