Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: tracker-review
Now that we are shipping tracker by default, we must review it's effectiveness and problems in Gutsy. Moving forward, performance should be evaluated, and new uses should be examined.
Trackers object tracking exposes ways to greatly increase desktop usability through intuitively providing access to files around content and attributes as opposed to their location on the filesystem, and we should look at ways to exploit this. Some examples include Trackers ability to build a music database (avoiding Rhythmbox having to maintain it's own database), and the ability to create a userspace filesystem organized around tracker tags/search.
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
You can have subsections that better describe specific parts of the issue.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
- use CPU limit to make trackerd not use more then 50% CPU, even when on idle.
- warn UPGRADE users (those that usualy have a lot more to index, then new users) that trackerd will take a long time. many upgrade users to ""gutsy"" have disable tracked, 'cause to froze there CPU and disk I/O to 100%