Bugzilla – Full Text Bug Listing
| Summary: | [usage] include the list of installed features with the uploaded monitor data | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Michal Dobisek <michal.dobisek> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | Keywords: | helpwanted |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Michal Dobisek
Hmm. You would see features that are actually used, i.e. CDT-specific actions and views. I am not sure how that would matter if some features are never used even if they are installed... Well, having the things insalled, but not using them is a usage pattern as well... But does such usage patter mean anything? Except that things can be uninstalled without any harm... Of course, from the used views and actions you might infer what features are actually used (~installed), which could workaround this enhancemend to some extend. I am now not able right now to came with a killer argument to support this enhancement. However I have a feeling, that especially for higher level analysis having just the list of features might be usefull. Especially if the feature versions are included. E.g. what percentage of people uses which Eclipse version, or a paricular version of some tool, or what are the most used UML editors. (In reply to comment #4) > ...or what are the most used UML editors. I can tell you right now that it is either RAD/WASD or Magic Draw (which is not Eclipse based). Uploaded stats won't be representative for drawing any conclusions, because you'll only see info from users who did uploaded stats. Most of the users won't really bother to upload... The idea behind the monitor framework is that it provides extensibility to support this kind of monitoring so that interested parties can add such monitors. We have no driver in the project for adding this monitoring, so I'm marking this as helpwanted in case anyone is interested in contributing it. If there is any additional extensibility required to support this please post. Fyi, I tried this way back and think that you can get most of what you need by querying the plug-in registry. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |