On the user metrics page (/profiles/<org name>/<member username>) we want to show a simple graph with the member at the centre and then directly connected nodes for each organisation member they're connected to by collaboration.
The data structure underneath this graph is super simple. eg.
Where the value represents the 'level' of collaboration between the current user and the keyed user. Just how this 'level' is calculated is undecided but a simple way would be a point system like:
1 point if current user follows target user
1 point if current user is followed by target user
1 point for each repository they've both contributed to recently
Dependency
The data to construct this graph should be pulled from the database and not from API calls. API calls are only made to put data in the database if it isn't there already.
The data model is in place but as of 21st July 2017 we haven't yet written code to make the API code if data is not available in database.
Description
On the user metrics page (
/profiles/<org name>/<member username>
) we want to show a simple graph with the member at the centre and then directly connected nodes for each organisation member they're connected to by collaboration.The data structure underneath this graph is super simple. eg.
Where the value represents the 'level' of collaboration between the current user and the keyed user. Just how this 'level' is calculated is undecided but a simple way would be a point system like:
1 point if current user follows target user 1 point if current user is followed by target user 1 point for each repository they've both contributed to recently
Dependency
The data to construct this graph should be pulled from the database and not from API calls. API calls are only made to put data in the database if it isn't there already.
The data model is in place but as of 21st July 2017 we haven't yet written code to make the API code if data is not available in database.