Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Error reporter and third-party code

There are two separate aspects...

1. Allowing the vendors to actually subscribe to the error reports. This is aimed at letting vendors help themselves.

2. Revising the system for censoring stack frames. This is aimed at facilitating project committers in investigating the error reports that land in their inbox by allowing them to know who they should be talking to. A more flexible system allowing parties to be added to the list of namespaces that aren't censored would be valuable, especially if coupled with improved defaulting/prompting on the client. One thing to consider is how would we handle vendors who are not aware of the error reporting system operated by Eclipse Foundation or at least are not aware that they can take advantage of it. We could collect a list of namespaces that are being censored and have someone in an elevated trust position (Eclipse Foundation staff?) attempt to contact these vendors to inform them of the error collection system and how they can advantage of it.

Ideally, we address both of these aspects. #2 may be more achievable in the short term (SR1).


- Konstantin

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: Saturday, July 25, 2015 7:33 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Error reporter and third-party code

> Am 25.07.2015 um 06:32 schrieb Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx>:
> > is opening and extending automated error reporting to 
> > plugins, e.g. to member companies, worth these efforts?
> In my opinion, it’s the only way to achieve the goals you set out to achieve at the beginning of this project. Users view Eclipse as a whole that encompasses third-party plugins and we need to act accordingly to remain competitive.


What about a program that allows any vendor to "opt-out" of the filtering? It could be as simple as requesting a vendor to open a Bugzilla and/or submit an agreement form to the Eclipse Foundation listening the package namespaces which should not be filtered anymore.


cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top