Community
Participate
Working Groups
To better understand m2e user base and have objective data about m2e execution environment we need to collect the following m2e usage statistics * org.eclipse.m2e.core bundle fully qualified version * org.eclipse.osgi bundle fully qualifier version as a proxy for eclipse version * java version * workspace id, tentatively generated as UUID.randomUUID * number of workspace maven projects * md5 hash of client ip address (as observed by the server) m2e will report this information to a remote server TBD weekly. The report will take place only if m2e is activated for some other reason, for example, explicit user UI interaction or presence of maven project in workspace, and if there are opened maven project in the workspace. In other words, installed but dormant m2e instances will not contribute to usage statistics.
Proposed m2e usage reporter implementation feature branch http://git.eclipse.org/c/m2e/m2e-core.git/log/?h=416371_m2e-usage-stats Proposed statistics collection server implementation https://github.com/ifedorenko/m2e-stats-server
Will there be an option for users to disable this? I am aware of companies with very strict policies for these kind of "calling home" features. And is there anything planned with regards to terms of use? Or is the plan to refer to the old Eclipse data usage collector terms of use?
Yeah, this can't really be collected automatically - must be an opt-in...but then if all plugins does this and shows a dialog it becomes a nightmare. Which is why we've been promoting allowing for preferences for this at eclipse platform level that plugins like m2e could register it intent to call home.
Just adding the link to https://bugs.eclipse.org/bugs/show_bug.cgi?id=413169 here. Maybe this bug should depend on bug 413169 as the EF has to agree to general policy first?
(In reply to Martin Lippert from comment #2) > Will there be an option for users to disable this? I am aware of companies > with very strict policies for these kind of "calling home" features. And is > there anything planned with regards to terms of use? Or is the plan to refer > to the old Eclipse data usage collector terms of use? The reporter plugin is completely separate from the rest of m2e, but it is installed by default. Companies that include m2e in their distributions (redhat, vmware, internal distros, etc) will have to decide if they include or not. Users who install m2e themselves will be able to delete the reporter plugin or disable it in OSGi console.
(In reply to Max Rydahl Andersen from comment #3) > Yeah, this can't really be collected automatically - must be an opt-in...but > then if all plugins does this and shows a dialog it becomes a nightmare. > What particular data is a concern here? If you looked at the code, there is nothing that will allow us or anyone else identify instances, at least this is my indent.
(In reply to Igor Fedorenko from comment #5) > The reporter plugin is completely separate from the rest of m2e, but it is > installed by default. Companies that include m2e in their distributions > (redhat, vmware, internal distros, etc) will have to decide if they include > or not. Users who install m2e themselves will be able to delete the reporter > plugin or disable it in OSGi console. I thought I have seen this plugin being included in the m2e feature, which makes it harder to use m2e in different distros if you can't include the stats bundle. What about putting it into a separate feature? That would make it easy to install or not install and would be very transparent for users what they get. And are there any plans for a terms of use? What are the terms of use?
> What particular data is a concern here? Some countries have very strict laws about calling home at all, almost regardless of what the content of the 'call' includes.
(In reply to Martin Lippert from comment #7) > (In reply to Igor Fedorenko from comment #5) > > The reporter plugin is completely separate from the rest of m2e, but it is > > installed by default. Companies that include m2e in their distributions > > (redhat, vmware, internal distros, etc) will have to decide if they include > > or not. Users who install m2e themselves will be able to delete the reporter > > plugin or disable it in OSGi console. > > I thought I have seen this plugin being included in the m2e feature, which > makes it harder to use m2e in different distros if you can't include the > stats bundle. What about putting it into a separate feature? That would make > it easy to install or not install and would be very transparent for users > what they get. > Yes, you are correct, usage reporter bundle is included in m2e main feature. I used p2 download stats as an example, there is no opt-in, no way to opt-out and no way to remove this functionality from p2 either. Unlike p2 I do provide a way to remove m2e usage reporter, so anyone who wants and cares will be able to do it. I believe anything else will only confuse people. > And are there any plans for a terms of use? What are the terms of use? Given how little info this collects there is not much we can do with the data. I assume only m2e committers and their employers will have access to the data. We can use it as bragging rights, I supposed, but primary goal here is to make better informed project management decision. The reason I decided to implement this was a discussed on m2e-dev mailing list about java6 support. I really want to have direct and objective data all m2e developers can look at and decide rationally, instead of looking at some secondary indicators but mostly relying on their gut feeling.
(In reply to Rob Stryker from comment #8) > > What particular data is a concern here? > > Some countries have very strict laws about calling home at all, almost > regardless of what the content of the 'call' includes. How my proposed usage reporter is different from p2 download stats? p2 calls home every time someone installs a feature with download stats enabled, and this call home happens even if the feature is being installed from a local mirror if I am not mistaken.
(In reply to Igor Fedorenko from comment #9) > > I thought I have seen this plugin being included in the m2e feature, which > > makes it harder to use m2e in different distros if you can't include the > > stats bundle. What about putting it into a separate feature? That would make > > it easy to install or not install and would be very transparent for users > > what they get. > > Yes, you are correct, usage reporter bundle is included in m2e main feature. > I used p2 download stats as an example, there is no opt-in, no way to > opt-out and no way to remove this functionality from p2 either. Unlike p2 I > do provide a way to remove m2e usage reporter, so anyone who wants and cares > will be able to do it. I believe anything else will only confuse people. I would like to ask for a separate feature. This doesn't make things more complicated on the m2e side, but makes things a lot easier on the distribution sides in their decision whether to include this or not. Please put this into a separate feature. > > And are there any plans for a terms of use? What are the terms of use? > > Given how little info this collects there is not much we can do with the > data. I assume only m2e committers and their employers will have access to > the data. We can use it as bragging rights, I supposed, but primary goal > here is to make better informed project management decision. I think we should have a good terms of use policy in place for this (as described in the bug that Marcel mentioned). Having these "calling home" features in place without an explicit policy looks suspicious and makes it hard for companies and their legal departments to decide on whether they allow to use the software or not. > The reason I decided to implement this was a discussed on m2e-dev mailing > list about java6 support. I really want to have direct and objective data > all m2e developers can look at and decide rationally, instead of looking at > some secondary indicators but mostly relying on their gut feeling. I think the discussion on the m2e-dev list provided good and solid data, far away from secondary indicators or far far far away from gut feeling. I don't know why you dismiss and depreciate that information here, people spend a lot of time to provide you with that data.
(In reply to Martin Lippert from comment #11) > (In reply to Igor Fedorenko from comment #9) > > > I thought I have seen this plugin being included in the m2e feature, which > > > makes it harder to use m2e in different distros if you can't include the > > > stats bundle. What about putting it into a separate feature? That would make > > > it easy to install or not install and would be very transparent for users > > > what they get. > > > > Yes, you are correct, usage reporter bundle is included in m2e main feature. > > I used p2 download stats as an example, there is no opt-in, no way to > > opt-out and no way to remove this functionality from p2 either. Unlike p2 I > > do provide a way to remove m2e usage reporter, so anyone who wants and cares > > will be able to do it. I believe anything else will only confuse people. > > I would like to ask for a separate feature. This doesn't make things more > complicated on the m2e side, but makes things a lot easier on the > distribution sides in their decision whether to include this or not. Please > put this into a separate feature. The number of people that package m2e in distros is far far smaller than the number of people who install m2e. I think it is fair to simplify m2e installation for the vast majority of users but I need to think some more about this before I decide. > > > > And are there any plans for a terms of use? What are the terms of use? > > > > Given how little info this collects there is not much we can do with the > > data. I assume only m2e committers and their employers will have access to > > the data. We can use it as bragging rights, I supposed, but primary goal > > here is to make better informed project management decision. > > I think we should have a good terms of use policy in place for this (as > described in the bug that Marcel mentioned). Having these "calling home" > features in place without an explicit policy looks suspicious and makes it > hard for companies and their legal departments to decide on whether they > allow to use the software or not. > Can you point me at p2 download stats terms of use, I'll probably just copy&paste it as-is. And I'll be more than happy to switch to the service provided and managed by Foundation, when such service becomes available that is. > > The reason I decided to implement this was a discussed on m2e-dev mailing > > list about java6 support. I really want to have direct and objective data > > all m2e developers can look at and decide rationally, instead of looking at > > some secondary indicators but mostly relying on their gut feeling. > > I think the discussion on the m2e-dev list provided good and solid data, far > away from secondary indicators or far far far away from gut feeling. I don't > know why you dismiss and depreciate that information here, people spend a > lot of time to provide you with that data. Not sure what you mean. The only data that was provided came from JBossTools, which did not have fidelity needed to make conclusive decision and did not represent broader m2e user base (and I have to assume was collected from JBossTools call-home feature). Few more people expressed their preferences and opinions, which is of course appreciated but I don't believe sufficient to understand 200K+ m2e install base.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
