Re: [Tracker] about the website

[Michael Lissner <mlissner michaeljaylissner com>]

There is a middle road as well. The current website instructions are very minimal. Some detail and examples could be given there with a reference to the README for more detail.

Either way though, my conclusion would be more info on the site, but keeping it up to date seems to be pretty challenging with a project that changes so rapidly.

My 2 cents.

Mike

Michele Mattioni wrote on 05/19/2009 03:11 AM:

On Tue, May 19, 2009 at 9:27 AM, Tshepang Lekhonkhobe
<tshepang gmail com> wrote:
  

On Mon, May 18, 2009 at 19:07, Michael Lissner
<mlissner michaeljaylissner com> wrote:
    

I believe this is the one:
http://michaeljaylissner.com/blog/installing-tracker-from-source

Something I think people might appreciate is more detail about all the
dependencies. Something like, if you want tracker to be able to read the
tags in jpegs, install X, if you want it to be able to do pdfs, install
Y. Maybe a table would be useful?

The other two things that have given me trouble in the past was (1)
whether to uninstall the tracker version from my distro's repos first,
and (2) where to find the commands to start tracker once it is installed
(and which command actually starts it - is it trackerd, tracker-applet,
tracker?) I think the commands end up somewhere that isn't part of most
people's path too, so I had trouble getting it to GO.

It would be great to see these instructions get some polish. Default
tracker installations by Ubuntu (and I believe other distros) seriously
leave out a lot of tracker's power (no jpegs, pdfs, tiffs, etc). Better
instructions might lead to people using more of the program's code.
      

Info in README is little more detailed and I was torn on what's more
suitable for README and what's more suitable for the web. What's your
advise?

    

I see two possible solutions:

1. We are really verbose and detailed on the Web. Basically we write
everything we replicate the README, Add info about which dep you need
and which filter enable and in which package you can find it. (at
least ubuntu [deb] and fedora [rpm])

something like:

# Dep Name: poppler
# Effect:  index pdf content
# package: libpoppler-dev libpoppler-glib-dev [deb], [Fedora Package here]

Would be really handy from an user point of view I think.

2. We are minimal and we suggest to read the README on the source
directory (thing that you should do by default if you install a
package from the source.)

Until now I went for the second option because I had the feeling to
miss the man power to keep track with the current status of tracker
and update the docs properly on the web. So I prefer to relay on the
README in the source.

If you guys are happy to keep an eye on the website and makes sure we
are not outdated (docs outdated is really really bad) we can try to
give it a go. As I said patches welcome :)

My two cents.

Cheers,
Michele