> Am 25.07.2015 um 06:32 schrieb Konstantin Komissarchik > <konstantin.komissarc...@oracle.com>: > > > is opening and extending automated error reporting to non-eclipse.org > > 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.
Marcel, 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. -Gunnar _______________________________________________ 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
