Open rkwright opened 6 years ago
@JCCR wrote: I'm looking at adopting new names for the "evolved" readium-js repos I've been working on.
If we are going by what's in your EOL doc.. I see a problem (https://github.com/readium/readium-js-viewer/wiki/EOL-for-ReadiumJS-and-BOL-for-Readium-Web#new-repos)
The shared code for the JS R2 streamer/navigator is called r2-shared-js already.
I propose we either rename the previous projects with some sort of -archived suffix readium-js-archived readium-js-viewer-archived
Rename it to something else: readium-js-old readium-js-legacy
Or use a different naming convention for the new packages: I'm currently in favour of a mono repo called r2-js-classic
Clearly, these new repos need to be named as a function of the outcome of the discussion in this thread.
r2-testapp-web
r2-*
projects published and pulled from npm
.r2-navigator-web
r2-workspace-web
r2-testapp-web
with local versions of r2-*
projects:
r2-navigator-web
r2-shared-js
r2-utils-js
r2-glue-js
@rkwright wrote document about the EOL of the Chrome app here. As part of that it was proposed that the naming of the new repos be as follows:
New Repos
We will need four new repos corresponding to readium-js, readium-js-viewer, shared-js and cfi-js. One approach would be to pattern them of the existing names and the "r2" prefix used elsewhere. Thus:
Each of these repos will be a clone of the existing repo, then modified by