Skip to content
This repository has been archived by the owner on Jul 4, 2019. It is now read-only.

Which repo for issues / Transfer Ownership #11

Open
qwo opened this issue Nov 25, 2015 · 1 comment
Open

Which repo for issues / Transfer Ownership #11

qwo opened this issue Nov 25, 2015 · 1 comment

Comments

@qwo
Copy link
Member

qwo commented Nov 25, 2015

the @CodeforNRV fork is the more active fork, should we migrate the issues and project over to that one and maintain @Code4HR as the fork.

just want to consolidate issue tracking and make sure everyones hacking on the right repo to merge 'upstream' to

@qwo qwo changed the title Which repo for issues Which repo for issues / Transfer Ownership Nov 25, 2015
@bschoenfeld
Copy link
Member

Make a new repo. I have a new scraper I'm working on and both of these will
be deprecated. No reason to keep API and scraper in the same repo anyway.

On Wednesday, November 25, 2015, Stanley Zheng [email protected]
wrote:

the @CodeforNRV https://github.com/codefornrv fork is the more active
fork, should we migrate the issues and project over to that one and
maintain @Code4HR https://github.com/code4hr as the fork.

just want to consolidate issue tracking and make sure everyones hacking on
the right repo to merge 'upstream' to


Reply to this email directly or view it on GitHub
#11.

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

No branches or pull requests

2 participants