Define project structure / define data that we need

[bastelfreak]

We need to interact a lot with the forge and github api.It might make sense to split the application in two parts. one datapoller and the actual web aplication. that allows us to use agressive caching.

[Flipez]

This is a good one to start with.

Currently Repositories are cached and kept locally to work with.

This includes name, full_name, description, homepage, stars, watchers, open_issues_count and the github_id.

Depending on the features this sure has to be enhanced.

[bastelfreak]

https://developer.github.com/v3/rate_limit/ and https://developer.github.com/v3/#rate-limiting describe rate limits for github. https://forgeapi.puppet.com/#section/Introduction is the API for forge.puppet.com

[dhollinger]

You could also separate the datapoller into a Rails engine