koopjs/koop vs koopjs/koop-core is confusing

[gavinr]

Sharing my experience as a new developer user:

• saw on the blog that v4.0.0 is out.

• clicked on the "GitHub" icon in the nav, brought me to https://github.com/koopjs

• saw that koopjs/koop was pinned, assumed that's the main place to look for the releases.

• latest release is 3.2 in 2017 - huh?

• Readme says "New @ version 3" - huh??

I then manually looked up koop on npmjs.com, eventually saw that it does have v4.0.0 as the latest version (as the blog post says) and links to github.com/koopjs/koop-core

I'm not sure how to resolve this - do we still want koopjs/koop to be the main repo for the project, or is koopjs/koop-core filling that role now? If we're just using koopjs/koop for issues, maybe we should clear out the readme and releases on this repo and just link to koopjs/koop-core or the documentation site? Or if koopjs/koop-core is the main repo, maybe pinning that instead on the org page? Or maybe both repos are still used and they are under different release schedules?

[rgwozdz]

Hey @gavinr - I really appreciate this. You're totally right - this is confusing. This structure was put in place before I came on to the project and the folks that thought it up are no longer part of the maintainer team. I think the idea was that Koop, due to it's plugin architecture is a collection of repos, and not just koop-core. koopjs/koop really just serves as a stand-in for a centralized place for issues - so for example, you're new to Koop, you have a bug, but it's really not clear if it's koop-core, FeatureServer, winnow, or one of the providers.

I like your idea of clearing the readme and releases from koopjs/koop. I also think we should clear all the repo pointers - it's not necessary anymore, now that we have a better doc site. We ca use this repo for issues that user's don't know where else to put.

[gavinr]

Sounds good - thanks for the response!

[rgwozdz]

Changes made.

[gavinr]

Thanks!