You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With two repositories, we often ask where something (e.g. active wiki) is located.
Solution 1 - merge repositories:
Close this repository after moving content into the ghdata wiki.
I don't know yet what do do about issues here since they are not related to the software development.
Maybe use wiki pages instead and comment/edit the wiki pages for discussion?
Solution 2 - specify purpose:
Specify purpose of ghdata repository for software development only. HealthIndicators repository becomes our project coordination space outside of software development, e.g. papers, milestones, etc.
Thoughts? Opinions? Votes?
The text was updated successfully, but these errors were encountered:
GeorgLink
changed the title
Discussion: Merge Respositories or specify purpose
Discussion: merge respositories or specify purpose
Feb 10, 2017
We should not merge repositories. The other repository will be published to the Python Package Index and our other work should not be downloaded to those who pip install it.
The wiki on ghdata should contain information about the usage and development of the tool only.
With two repositories, we often ask where something (e.g. active wiki) is located.
Solution 1 - merge repositories:
Close this repository after moving content into the ghdata wiki.
I don't know yet what do do about issues here since they are not related to the software development.
Maybe use wiki pages instead and comment/edit the wiki pages for discussion?
Solution 2 - specify purpose:
Specify purpose of ghdata repository for software development only. HealthIndicators repository becomes our project coordination space outside of software development, e.g. papers, milestones, etc.
Thoughts? Opinions? Votes?
The text was updated successfully, but these errors were encountered: