Re: [RFC][PATCH] report-error.bbclass: Add support for autosending

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2016-09-09 at 08:42 +1200, Paul Eggleton wrote:
> Hey Beth,
> 
> On Thu, 08 Sep 2016 11:26:01 Elizabeth 'pidge' Flanagan wrote:
> > 
> > This commit pulls and extends the functionality of .oe-error-report 
> > into
> > local.conf. It maintains the functionality of .oe-error-report.
> > 
> > It also enables report-error to automatically send error reports to
> > a
> > specified error report server. This patch enables infrastructure
> > ppl to
> > set development teams up so that we can gather error metrics
> > automatically.
> > 
> > This relies on a new set of variables:
> > 
> > REPORTERROR[autosend]="yes|no|ask"
> > REPORTERROR[user]=username
> > REPORTERROR[email]=email
> > REPORTERROR[server]=error-report-web instance
> > 
> > For autosend yes and no are pretty self explainatory. ask does not
> > pass
> > the -y flag to send-error-report, thus enabling the end user to
> > review
> > the report prior to submission.
> I'm not sure if sentiment has changed on this issue (FWIW, it hasn't
> really
> on my part), but this topic did come up before - start of thread
> here:
> 
> http://lists.openembedded.org/pipermail/openembedded-core/2014-March/
> 090621.html

Thanks for digging that up. I am conscious that this was deliberately
designed so the user has to sign up for auto submission. To do
otherwise lets layers "spy" on users far too easily.

That said there are 101 ways you could do that anyway, this just makes
it very very easy.

So I'm torn on this issue. How easy should auto-error submission be,
given the information that could accidentally expose?

Cheers,

Richard