[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Direction of KDE default?
From:       wvl <yatsu () wanadoo ! nl>
Date:       2002-07-27 22:46:26
[Download RAW message or body]

On Saturday 27 July 2002 23:50, Uno Engborg wrote:
> Aaron J. Seigo wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >On Saturday 27 July 2002 08:34, Irwin K wrote:
> >>How would we evaluate the files?  We would likely need another program
> >> for that.
> >
> >yes, but it wouldn't be hard to write.
> >
> >iterrate through all the files in $KDEHOME/share/config/, opening each one
> >with KConfig. for each group read in each config entry and  create a text
> >file with a bunch of sql statements that can be fed into a database. email
> >that text file off to the project.
>
> Why open with KConfig, wouldn't it be simpler with a simple perl script
> that directly
> fed the info into the database.
>
> >the program would have a blacklist of files/entries to ignore (e.g. all
> >"username" or "password" entries, or kmail's filters, or ...). the
> > blacklist would be fiarly easy to come up with as we could run the
> > program w/out the blacklist on our own configs and determine what we
> > wouldn't want made public =)
> >
> >the database would have one record for each config entry in each file.
> > each record would record the file name (e.g. konquerorrc), the config
> > group, the config option and the value it was set to.
> >
> >with this all in a database one could then run interactive queries.
> > popping it behind a set of php web pages one could even open it up to
> > developers to query the results they are interested in (e.g. the settings
> > for the apps they maintain)
>
> If we collect data from users, why not let other users make use of that
> information?
>
> If, when using kde for the first time, the user  was prompted for
> information on
> how long he had used a computer,  and what systems he previously used,
> his nationality etc we could use the database to get him the avarage
> settings
> for his kind of user.
>
> We could ask the user if he wanted to use the central database as backup
> for his config files, and if he allows other people to make use of  the
> information.
>
> If he agrees, then his settings could be polled every time he closes the
> "Control
> Center". The user could then use the central database as backup for his
> config
> files.
>
> That  way there would be an incentive for the user  to fill in and share
> the information.
>
> Usernames and hostnames could be used as keys in the database, or we
> could use the md5 hash of that information to anonymize the data.

This would be a usability nightmare.

- wvl
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]