Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 26 Apr 2017 20:04:04 +0000 (UTC)
From: "Shazron Abdullah (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.13066813.1493152604000.59363.1493237044621@Atlassian.JIRA>
In-Reply-To: <JIRA.13066813.1493152604000@Atlassian.JIRA>
References: <JIRA.13066813.1493152604000@Atlassian.JIRA> <JIRA.13066813.1493152604051@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CB-12708) Core Plugins Roadmap 2017
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Apr 2017 20:04:09 -0000


     [ https://issues.apache.org/jira/browse/CB-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shazron Abdullah updated CB-12708:
----------------------------------
    Description: 
h1. DEADLINE of June 1st 2017

All decisions should be wrapped up by then.

h2. This is an umbrella issue where we list all the core plugins we have, and what we are to do with them:
1. Sunset 
2. Continue Maintenance
3. Integrate into their respective platforms 

The first two of these options will require migration steps (docs), if any, to W3C API equivalents in the browser, when available. If not, the goal would be for them (if we are still maintaining them) to be upgraded to a W3C API standard.

h2. Actions:
1. Migration docs (if applicable)
2. Upgrade to W3C API standard (if applicable)
3. Update README with non-maintenance status (if applicable)


  was:
h2. This is an umbrella issue where we list all the core plugins we have, and what we are to do with them:
1. Sunset 
2. Continue Maintenance
3. Integrate into their respective platforms 

The first two of these options will require migration steps (docs), if any, to W3C API equivalents in the browser, when available. If not, the goal would be for them (if we are still maintaining them) to be upgraded to a W3C API standard.

h2. Actions:
1. Migration docs (if applicable)
2. Upgrade to W3C API standard (if applicable)
3. Update README with non-maintenance status (if applicable)


> Core Plugins Roadmap 2017
> -------------------------
>
>                 Key: CB-12708
>                 URL: https://issues.apache.org/jira/browse/CB-12708
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: AllPlugins
>            Reporter: Shazron Abdullah
>
> h1. DEADLINE of June 1st 2017
> All decisions should be wrapped up by then.
> h2. This is an umbrella issue where we list all the core plugins we have, and what we are to do with them:
> 1. Sunset 
> 2. Continue Maintenance
> 3. Integrate into their respective platforms 
> The first two of these options will require migration steps (docs), if any, to W3C API equivalents in the browser, when available. If not, the goal would be for them (if we are still maintaining them) to be upgraded to a W3C API standard.
> h2. Actions:
> 1. Migration docs (if applicable)
> 2. Upgrade to W3C API standard (if applicable)
> 3. Update README with non-maintenance status (if applicable)


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org