[jbosstools-issues] [JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
[
https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin....
]
Michelle Murray updated JBDS-2848:
----------------------------------
Description:
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.
was:
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
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.
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: Andre Dietisheim
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