Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: merge respositories or specify purpose #13

Open
GeorgLink opened this issue Feb 10, 2017 · 3 comments
Open

Discussion: merge respositories or specify purpose #13

GeorgLink opened this issue Feb 10, 2017 · 3 comments

Comments

@GeorgLink
Copy link
Contributor

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?

@GeorgLink GeorgLink changed the title Discussion: Merge Respositories or specify purpose Discussion: merge respositories or specify purpose Feb 10, 2017
@germonprez
Copy link
Contributor

I'm inclined for option 2.

@howderek
Copy link
Contributor

howderek commented Feb 14, 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.

@sgoggins Will you move Papers.md from ghdata to this repo?

@germonprez
Copy link
Contributor

@howderek I think that papers.md could move here. You'll see in the dev branch of ghdata, I moved queries (off the wiki) and added a roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants