Rename github repository from worthwhile to hydra-curation_concerns

[flyingzumwalt]

After #41 is complete,

• make a new git repository at projecthydra-labs/hydra-curation_concerns (don't use github to fork projecthydra-labs/worthwhile. That will cause wierdness with the github issues)
• push the curation_concerns branch of pulibrary/worthwhile to the master branch of projecthydra-labs/hydra-curation_concerns

[jpstroop]

I don't have a philosophical problem with this, but there are instances of Worthwhile in production somewhere, correct? Should those users be warned, should we make a fork instead, or is this OK? Following SemVer, we're certainly within our rights, but reality may be different. Just checking.

[flyingzumwalt]

You can create a new repository, but should not fork. When you fork,
issues can only be created on the original repository.

On Tue, May 12, 2015 at 5:22 PM, Jon Stroop [email protected]
wrote:

I don't have a philosophical problem with this, but there are instances of
Worthwhile in production somewhere, correct?

Should those users be warned, should we make a fork instead, or is this OK?
Following SemVer, we're certainly within our rights, but reality may be
different.

Just checking.

Reply to this email directly or view it on GitHub
#40 (comment)
.

[flyingzumwalt]

On second thought, let's just leave worthwhile there and create a new repo. I updated the instructions.

[jpstroop]

👍