Konstantin, I presented AERI to the board of directors at EclipseCon Europe last week. I also discussed with EMO whether there is a way that Eclipse would extend its current scope and start collecting error reports on behalf of others (member companies or other third parties). We came to the conclusion that the Eclipse Foundation will not collect error reports on behalf of other plug-in providers in foreseeable future. The risk that sensitive data might get shared is too high in such an uncontrolled environment and setting up a secured system that can handle this, the legal work this requires etc. is currently out of scope.
But the Foundation is open to extensions to the error reporting client which allow users to share errors with arbitrary (e.g., your own or other centralized) data end-points. Marcel > Am 03.08.2015 um 17:49 schrieb Konstantin Komissarchik > <konstantin.komissarc...@oracle.com>: > > I have filled out the survey, but I do want to stress one point that I think > got missed in all the discussion… > > Doing something about auto-censored stack frames is not entirely for > third-party benefit. It is statistically improbably that all of the errors > with third-party frames are caused by third-party code, yet all that I’ve > seen collected for Sapphire are non-actionable in their current censored > form. As such, we are losing on an opportunity to improve eclipse.org > <http://eclipse.org/> code as well as third-party code. > > Thanks, > > - Konstantin > > > From: cross-project-issues-dev-boun...@eclipse.org > [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Marcel > Bruch > Sent: Monday, August 03, 2015 2:49 AM > To: Cross project issues > Subject: Re: [cross-project-issues-dev] Error reporter and third-party code > > >> Am 31.07.2015 um 22:01 schrieb Konstantin Komissarchik >> <konstantin.komissarc...@oracle.com >> <mailto:konstantin.komissarc...@oracle.com>>: >> >> While we ponder broader process and infrastructure improvements > > > To follow up on this part: So far only a few actively discussed this request. > To me, and likely to others, it’s hard to say who really is interested in > extending the scope of the error reporting and whether it’s worth taking this > to the board of directors now. > > If you (and others on this list) have a couple of minutes, please cast your > voice at this short form [1]. > > > Thank you > Marcel > > > [1] > https://docs.google.com/forms/d/1LtQ8QyMnQ1cD5XTXBdVgynGRaiKEMaUi9a0nxeRoumM/viewform > > <https://docs.google.com/forms/d/1LtQ8QyMnQ1cD5XTXBdVgynGRaiKEMaUi9a0nxeRoumM/viewform> > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> -- Codetrails GmbH The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Phone: +49-6151-276-7092 Mobile: +49-179-131-7721 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
