[jbosstools-issues] [JBoss JIRA] (JBDS-2848) Usage Stats for actual used features

[Len DiMaggio (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949097#comment-12949097 ] 

Len DiMaggio commented on JBDS-2848:
------------------------------------

It's not optimal to be adding support for more and more usage all the way up to GA.

However, if most of these are completed in Beta1, and the remainder in Beta2, then QE can 'ack' this requirement.

<ldimaggi_wfh> jpallich, maxandersen when can we stop adding usage? in beta2?
<jpallich> ldimaggi_wfh: no new features after B2 - correct
                
> Usage Stats for actual used features
> ------------------------------------
>
>                 Key: JBDS-2848
>                 URL: https://issues.jboss.org/browse/JBDS-2848
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: requirements, usage
>            Reporter: Burr Sutter
>            Assignee: Alexey Kazakov
>            Priority: Critical
>              Labels: QE_JBDS80_needinfo
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using.  Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira