Dear cross-projects, several committers asked whether we could give *contributors* access to error reports and let them review, triage and fix problems spotted in Eclipse in order to distribute the workload better.
Contributors cannot get full access to all reports but providing an *anonymized view* (that does not contain potentially sensitive information like reporter names, email addresses, ids, comments, error messages etc.) seems to acceptable and a viable alternative. I created an example for such a public view for your review here: Reviewer’s view: https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/552bd8f4e4b026254ee03b58 <https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/552bd8f4e4b026254ee03b58> Reporter’s view: https://dev.eclipse.org/recommenders/community/aeri/v2/#!/problems/552bd8f4e4b026254ee03b58 <https://dev.eclipse.org/recommenders/community/aeri/v2/#!/problems/552bd8f4e4b026254ee03b58> Please let me know if you have any concerns with that proposal. The Foundation's Legal and the Architecture Council approved the general idea but we’d like to bring this to your attention early in the process and before announcing this to the public. If no issues are raised, I’ll modify the digest emails to contain links to the public problem views which adds the option to create bug reports from them. Thank you. Marcel P.S.: Side Note: Mars.2 contained 30% less errors than Mars.0. Let’s take these numbers further down in Neon... Source <http://de.slideshare.net/Microbiotic/eclipse-neon-webinar-automated-error-reporting-preview>
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
