Ric Wright

From @llemeurfr 👍 I confess I would have a more basic approach, where people who are not "committers" (PR reviewers) don't even create branches in the Readium space, but create...

Note that there are more test files of various provenance here: [https://github.com/readium/readium-test-files](https://github.com/readium/readium-test-files) but they need curation as well.

After the discussion on the Readium engineering meeting on 31 October, re-opening this as it would appear we still have some open questions here - maybe a number of questions.

@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...

Clearly, these new repos need to be named as a function of the outcome of the discussion in [this thread](https://github.com/readium/architecture/issues/74).

A couple of other potentially relevant sources of info from the widget work in EPUB 3.x: - [Security and Privacy](https://docs.google.com/document/d/18Kt9AmTiBOFNKexsm-iSIAUXS6JPN-tnTV7CO0dmUTE/edit) - [Widget Security Use Cases](https://docs.google.com/document/d/1cR-TgQSHxrE9oW4P8pY9vDZOU0TTHebstJKvkg5phpM/edit)

whmccoy wrote: Just as an FYI, the EPUB-in-Edge team whom I talked with earlier this week here in Seattle area, mentioned how many tricky issues they had to deal with....

@whmccoy Well, I think it is a little more complex than that. I think there are (at least) 4 buckets: 1. issues that are entirely something intrinsic to Readium-1 and...

Thanks for creating and testing this @olivierkorner @danielweck I am OK with it, If you are OK with this, please go ahead and merge it.

This is part of the work on Windows. As our support for Windows is up in the air, not sure what we will do here.