W3C home > Mailing lists > Public > public-web-mobile@w3.org > February 2014

Cordova/W3C

From: Lisa Seacat DeLuca <ldeluca@us.ibm.com>
Date: Thu, 27 Feb 2014 14:34:56 -0500
To: Dominique Hazael-Massieux <dom@w3.org>, DAP <public-device-apis@w3.org>, public-web-mobile@w3.org
Message-ID: <OFEFBC9D06.FC3E4E54-ON87257C8C.006A6426-85257C8C.006B953E@us.ibm.com>
During today's DAP Working Group call, we chatted about pushing the 
alignment between the Apache Cordova APIs and the w3c specs.  I'm sending 
out this email to get the ball rolling and start discussing some ideas to 
make this happen.

Suggested Steps
Create a set of JIRA issues within the Cordova tracking system for each of 
the issues.  Dom has already graciously started this process.  There are 
currently 10 issues opened.  Anyone can come in and open issues so if you 
see something that has been left off this list please open a new issue.
https://issues.apache.org/jira/browse/CB-6065  battery
https://issues.apache.org/jira/browse/CB-6066  html media capture
https://issues.apache.org/jira/browse/CB-6068  contacts
https://issues.apache.org/jira/browse/CB-6069  motion
https://issues.apache.org/jira/browse/CB-6070  orientation
https://issues.apache.org/jira/browse/CB-6071  notifications
https://issues.apache.org/jira/browse/CB-6072  File transfer
https://issues.apache.org/jira/browse/CB-6073  I18N
https://issues.apache.org/jira/browse/CB-6074  Media
https://issues.apache.org/jira/browse/CB-6075  Vibration which was marked
as a dup of https://issues.apache.org/jira/browse/CB-5459 

Prioritize the issues.  Which of these issues would be the most beneficial 
to have?  Which of the w3c specs are the most stabile?  It makes sense to 
start with older specs first and work from there.
Drill down and understand the disconnect.  What does Cordova have that the 
w3c spec's don't have?  What does the w3c specs have that Cordova is 
missing?  What is the proposed alignment?  ...add these types of comments 
to the JIRA issues.
Once step 3 is determined, break the JIRA issues out into platform 
relevant issues.  ex. battery for iOS, battery for Android, etc.  This 
allows the Cordova team to take ownership for a platform that the team has 
expertise on.  A general issue is also harder to track progress.

We should also create a form letter that we can send out when new users 
come into Cordova volunteering to help out that shows them the status of 
the current JIRA issues related to the w3c alignment and a breakdown of 
each platform so they can get in and help out quickly.  Another suggestion 
Dom made was to either create a task force within the web/mob IG and 
report status and document suggestions there or otherwise report regular 
status so that this alignment stays visible. 


Lisa

Lisa Seacat DeLuca
Mobile Engineer | t: +415.787.4589 | ldeluca@apache.org | | 
ldeluca@us.ibm.com | lisaseacat.com | | 




picture
(image/png attachment: 01-part)

picture
(image/png attachment: 02-part)

Received on Thursday, 27 February 2014 21:29:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:59:29 UTC