← Back to team overview

ubuntu-manual team mailing list archive

Re: Dash search data and Chapter 2


Ok...got a informative reply from Didier last night.  He was very detailed
in his explanation and very empathetic at the frustration this last minute
change had caused the documentation community.

The external search results will be OPT-OUT, meaning search results will be
ON by default. The reason for it being ON by default makes sense as this
impacts other lenses that rely on external data sources (he mentions a
google lens and a wikipedia lens as examples). Users can disable external
results by going to the privacy section of the gnome control center.

Here is a screenshot of the final output that will appear in the final
12.10 release:

I think at this point, we have enough information to move forward with a
mention in Chapter 2 of this feature and a quick blurb in the appropriate
security section or chapter on how to disable, along with a good screenshot.

The earliest I'll be able to update this information is Wednesday night
(Pacific Standard Time). So if it needs to be inserted before then, someone
else will have to do it. Else, I'll take care of it at that time (the
write-up in Chapter 2 and in other sections as needed...and the insertion
of the screenshot).

On Mon, Oct 1, 2012 at 10:10 AM, Kevin Godby <godbyk@xxxxxxxxx> wrote:

> Hey, Jim.
> On Mon, Oct 1, 2012 at 9:09 AM, Jim Connett <jimandmarcy@xxxxxxxxx> wrote:
> > That said, there has to be some credible/substantive information
> available
> > somewhere telling us what user options will be available to control the
> > Dash's scope (including screenshots?). Maybe someone has a source for
> this
> > information and we can squeeze it into the doc this week.
> The best pointer I have at the moment is the feature-freeze exception
> bug report: <
> https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1054746
> >
> You could try contacting Didier Roche (didrocks) from the bug report
> for more up-to-date info, as well.
> Hopefully there will be a lot fewer feature-freeze and
> user-interface-freeze exceptions next cycle. It's been pretty crazy
> this time 'round.
> --Kevin