W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: [IndexedDB] Status

From: Andrei Popescu <andreip@google.com>
Date: Mon, 7 Jun 2010 21:32:38 +0100
Message-ID: <AANLkTin0xm7tl3juDP87o6LmJKCBBhqQU59iKPFuFb8B@mail.gmail.com>
To: Nikunj Mehta <nikunj@o-micron.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, public-webapps WG <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>
On Mon, Jun 7, 2010 at 9:13 PM, Nikunj Mehta <nikunj@o-micron.com> wrote:
>
> On Jun 7, 2010, at 12:22 PM, Jeremy Orlow wrote:
>>
>> 3. Editors: Nikunj Mehta (Invited Expert), Eliot Graf (Microsoft)
>> 4. Spec document management: Currently W3C CVS, also using W3C's
>> Distributed CVS (Mercurial) system
>
> The current spec is really far out of date at this point.  There are 15
> issues logged, but I could easily log another 15 (if I thought that'd help
> get things resolved more quickly).
> I know Eliot is helping out with copy editing, but it's going to take a lot
> of time to get the spec to where it needs to be.  Andrei P (of GeoLocation
> spec fame) has been working on implementing IndexedDB in Chrome for a couple
> weeks now and has volunteered to start updating the spec right away.  He
> already has CVS access.  Is there any reason for him not to start working
> through the bug list?
>
> As Eliot is working on non-design issues, it is easier to coordinate with
> him. Moreover, I am not totally sure how the DCVS system we have started to
> use just now is going to work out. Give us another week or so to sort out
> initial hiccups and at that point we could use more editorial help.
> Multiple people changing the spec's technical basis makes it necessary to
> create a more sophisticated process. I am happy to add Andrei as an editor
> provided I can understand the editing process and how we get new editor's
> drafts out without necessarily being out of sync with each other.
> Andrei -- would you be able to describe how you would co-ordinate the
> editing with me?

I only plan to make changes once we have consensus on the mailing
list. It's probably easiest to use the issue tracker to distribute the
existing bugs among the three editors. If we find that over time the
distribution becomes unbalanced, we can discuss offline about how to
improve the collaboration, but I don't think that is a big worry at
this point.

Thanks,
Andrei
Received on Monday, 7 June 2010 20:33:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:38 GMT