[coremob-ucr] created document

Hi everyone,

I created the use case and requirement doc on github[1]. An up to date
editor's draft is automagically available[2].

Instructions on how to edit this document are available in the README
file[3]. It's a lot easier than it might appear to be and you should be
able to get started within seconds. Ping me if there are any issues.

Please consider the current content as a placeholder more than anything

Over the course of the next two weeks I'd like for the editors to come to
agreement over the following questions:

    1. How do we document the requirements for features that don't really
fall under specific scenarios, use cases or app descriptions (e.g.: ES5,
HTML markup, CSS 2.1, etc.) if at all?

    2. Do we go for an approach where we document apps[4] or do we go for
an approach where we document use cases / scenarios[5]?

    3. How deeply do we define requirements? The goal being to avoid
overlap with spec-level requirements. For example, are the current recs
for taking pictures too deep, or not deep enough[6]?

    4. How can we split up work to move this along faster?

    5. Other issues you might want to raise.

Note that we'll be prefixing all messages on the mailing list pertaining
to the edition of this document with [coremob-ucr] so that those
interested can follow along and others tune out.

Finally, thanks to Lars, Jen and Giri to jump in to help with. This is
much appreciated.


[1]: https://github.com/coremob/coremob-ucr
[2]: http://coremob.github.com/coremob-ucr/index.html
[3]: https://github.com/coremob/coremob-ucr#editing-this-document
[4]: http://coremob.github.com/coremob-ucr/index.html#a-2d-game
[6]: http://coremob.github.com/coremob-ucr/index.html#taking-pictures

Received on Friday, 12 October 2012 17:39:50 UTC