Editing Desktop Search Hackfest

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
[[Image:DesktopSearchHackfest.jpg]]
+
= Other Pages of Interest =
-
 
+
-
Hackfest around the Desktop Search and Metadata handling topic. Currently there are many partial solutions to the problem, so a hackfest could help to share some code, define lines to the projects and steal the good points of other projects :P
+
* [[Talk:Desktop_Search_Hackfest|Discussion page]]
* [[Talk:Desktop_Search_Hackfest|Discussion page]]
* [[Desktop_Search_Hackfest/Schedule|Schedule draft]]
* [[Desktop_Search_Hackfest/Schedule|Schedule draft]]
 +
 +
= Event description =
 +
 +
[COMPLETE]
 +
 +
Hackfest around the Desktop Search and Metadata handling topic. Currently there are many partial solutions to the problem, so a hackfest could help to share some code, define lines to the projects and steal the good points of other projects :P
== Proposed dates ==
== Proposed dates ==
Line 12: Line 16:
* In Berlin
* In Berlin
-
== Notes ==
+
= Participants =
-
* [[/Day one notes | Notes from the 1st day]]
+
-
* [[/Design discussion | Notes on designing desktop search]]
+
-
 
+
-
== Participants ==
+
* Name (Project / Location)
* Name (Project / Location)
* Ben van Klinken (CLucene/NL)  mailinglist
* Ben van Klinken (CLucene/NL)  mailinglist
Line 42: Line 42:
* Marius Vollmer (Nokia)
* Marius Vollmer (Nokia)
* Otto Kopra (Nokia)
* Otto Kopra (Nokia)
 +
fabrice.colin (Pinot) was invited, is on mailinglist, but won't make it.
fabrice.colin (Pinot) was invited, is on mailinglist, but won't make it.
Line 67: Line 68:
* Ben Martin (libferris/Australia - Quim group, booking requested to travel agent)  (date to be confirmed)
* Ben Martin (libferris/Australia - Quim group, booking requested to travel agent)  (date to be confirmed)
* Anders Rune Jensen (unknown time and location)
* Anders Rune Jensen (unknown time and location)
-
* Shivakumar Manishankar (Helsinki 18:00+ - Urho group booking)
+
* Rob Taylor (gnome)
-
* Rob Taylor (Manchester 18:00+ - Urho group booking )
+
* Jürg Billeter (gnome)
-
* Jürg Billeter (Zürich 18:00+ - Urho group booking )
+
* Marius Vollmer (Nokia)
-
* Marius Vollmer (Helsinki 17:00+ - Own booking - own hotel)
+
* Otto Kopra (Nokia)
-
* Otto Kopra (Helsinki 17:00+ - Own booking - own hotel)
+
=== Friday 19 ===
=== Friday 19 ===
Line 113: Line 113:
* Ben Martin (libferris/Australia)  (date to be confirmed)
* Ben Martin (libferris/Australia)  (date to be confirmed)
-
== Proposed items to work ==
+
= Proposed items to work =
The sessions are being ordered/organized in the [[Desktop_Search_Hackfest/Schedule | Schedule]] page.
The sessions are being ordered/organized in the [[Desktop_Search_Hackfest/Schedule | Schedule]] page.
-
=== Concrete Coding Tasks ===
+
== Concrete Coding Tasks ==
* Xesam integration in file chooser and Nautilus. Possibly use xesam-glib
* Xesam integration in file chooser and Nautilus. Possibly use xesam-glib
 +
* Specify a DBus specification for thumbnailers
* Specify a DBus specification for thumbnailers
 +
* Create language bindings for xesam-glib (specifically Vala, C#, and Python) for xesam-glib and use these achieve
* Create language bindings for xesam-glib (specifically Vala, C#, and Python) for xesam-glib and use these achieve
 +
** a deskbar module
** a deskbar module
** a Gnome Do add-in
** a Gnome Do add-in
** Gnome launch box extension
** Gnome launch box extension
*** Sebastian has mentioned that he would like to work on Python and C# bindings for xesam-glib as well as a Deskbar module
*** Sebastian has mentioned that he would like to work on Python and C# bindings for xesam-glib as well as a Deskbar module
 +
* Create/draft a xesam-gtk library with widgets empowered by xesam-glib
* Create/draft a xesam-gtk library with widgets empowered by xesam-glib
 +
* Create a small server that exposes the Xesam search engine over Avahi (probably over http). This is correlated with the "Xesam over alternative protocols BOF".
* Create a small server that exposes the Xesam search engine over Avahi (probably over http). This is correlated with the "Xesam over alternative protocols BOF".
 +
* Create a common metadata test corpus
* Create a common metadata test corpus
 +
* Create a common metadata unit test suite for the most common file types
* Create a common metadata unit test suite for the most common file types
-
** Improve current extractors (all engines). Prepare a huge database of creative commons contents with a lot of metadata, including corrupted files before the hack meeting. Prepare an automated script to check if we are extracting the interesting information from the files (showing information like "extraced the expected information in 90% of the mp3, incomplete information in 9%, crashed in 1% of them"). We can even organize a small competition with a modest prize.
+
 
 +
** Improve current extractors (all engines). Prepare a huge database of creative commons contents with a lot of metadata, including corrupted files before the hack meeting. Prepare an automated script to check if we are extracting the interesting information from the files (showing information like "extraced the expected information in 90% of the mp3, incomplete information in 9%, crashed in 1% of them"). We can even organize a small competition with a modest prize.  
 +
 
* Time ordering / searching optimized model for tracker
* Time ordering / searching optimized model for tracker
 +
* Category optimized database model for tracker
* Category optimized database model for tracker
 +
* Document Xesam ontology
* Document Xesam ontology
** See [[Desktop_Search_Hackfest/XesamOntology|Xesam Ontology BOF and Hackfest page]]
** See [[Desktop_Search_Hackfest/XesamOntology|Xesam Ontology BOF and Hackfest page]]
-
 
+
=== Beagle Coding Task Ideas ===
-
==== Beagle Coding Task Ideas ====
+
* Beagle-Xeasm work, we will have almost everyone involved in this spec available too us, so lets work on getting our compatibility 100%
-
* Beagle-Xesam work, we will have almost everyone involved in this spec available too us, so lets work on getting our compatibility 100%
+
** Gnome-Do plugin. I want a solid beagle plugin for Gnome-Do, should be a super-quick codeup (Preferably over xesam!)
** Gnome-Do plugin. I want a solid beagle plugin for Gnome-Do, should be a super-quick codeup (Preferably over xesam!)
* Dashboard. I have a million and one ideas working for this, but the core of it would hopefully be getting some unified means of generating clue packets/context. I am thinking that utilizing screenreader api's to get working windows/text could be very helpful here.  
* Dashboard. I have a million and one ideas working for this, but the core of it would hopefully be getting some unified means of generating clue packets/context. I am thinking that utilizing screenreader api's to get working windows/text could be very helpful here.  
Line 144: Line 154:
** This could increase the beagle-xesam performance considerably, and has the potential to fix Dashboard bottlenecks as well.
** This could increase the beagle-xesam performance considerably, and has the potential to fix Dashboard bottlenecks as well.
-
=== BOF Sessions ===
+
== BOF Sessions ==
* There are several metadata-heavy technologies emerging. Soylent, People, Online Desktop/Desktop Data Model, Xesam, and others. Can we somehow work more together? They all appear to take slightly different approaches.
* There are several metadata-heavy technologies emerging. Soylent, People, Online Desktop/Desktop Data Model, Xesam, and others. Can we somehow work more together? They all appear to take slightly different approaches.
 +
* How to share metadata between engines when it's not stored in the file itself (say... tags)
* How to share metadata between engines when it's not stored in the file itself (say... tags)
 +
* How to share extractors between the engines. (How many code to read id3 is out there?)
* How to share extractors between the engines. (How many code to read id3 is out there?)
 +
* A shared way to harvest metadata and register metadata extractors or sources. This is also relevant for Xesam.
* A shared way to harvest metadata and register metadata extractors or sources. This is also relevant for Xesam.
 +
* Dashboard? Why has the idea that everybody loved never landed on consumer desktops? How can we make it real. What technical solutions do we need in place?
* Dashboard? Why has the idea that everybody loved never landed on consumer desktops? How can we make it real. What technical solutions do we need in place?
 +
* While it is pretty hype to talk about desktop search and even write lots of code for it, why is it not more integrated in the desktop than it is? A big reason is of course the quality of the search engine. I can think of a lot of other reasons though (feel the teaser!).
* While it is pretty hype to talk about desktop search and even write lots of code for it, why is it not more integrated in the desktop than it is? A big reason is of course the quality of the search engine. I can think of a lot of other reasons though (feel the teaser!).
 +
* Xesam over alternative protocols. Keywords: http/REST, Avahi, Bluetooth, XMLRPC, Soap, Plain ol' socket.
* Xesam over alternative protocols. Keywords: http/REST, Avahi, Bluetooth, XMLRPC, Soap, Plain ol' socket.
 +
* How can we integrate pervasive searching capabilities in the current Gnome desktop (ie. without changing the desktop interaction model)
* How can we integrate pervasive searching capabilities in the current Gnome desktop (ie. without changing the desktop interaction model)
 +
* How can we create a whole new user interface based on metadata and instant searches. Ie possibly breaking totally with the standard interaction model of the desktop. One possible starting point:
* How can we create a whole new user interface based on metadata and instant searches. Ie possibly breaking totally with the standard interaction model of the desktop. One possible starting point:
 +
** "do-what-I-think-desktop" The basic premise is "the user should not need to even touch the computer. It should just do the expected/desired in all circumstances without user interaction". Then see how far we can go with statistical analysis of historic user actions and rich metadata - and then accept that we can not achieve the end goal, but still get as close as possible.
** "do-what-I-think-desktop" The basic premise is "the user should not need to even touch the computer. It should just do the expected/desired in all circumstances without user interaction". Then see how far we can go with statistical analysis of historic user actions and rich metadata - and then accept that we can not achieve the end goal, but still get as close as possible.
 +
* Discuss the Xesam Metadata Storage spec. It is slated to be included in the post 1.0 release of Xesam, but there is very little concrete written down or agreed upon. This can seriously use a lot of discussion. It has ramifications into Soylent and desktop-data-model as well, probably others too.
* Discuss the Xesam Metadata Storage spec. It is slated to be included in the post 1.0 release of Xesam, but there is very little concrete written down or agreed upon. This can seriously use a lot of discussion. It has ramifications into Soylent and desktop-data-model as well, probably others too.
 +
* Gnome and Nepomuk? Hitherto Gnome and Nepomuk has not really been related at all. Even though Xesam and Nepomuk has its disagreements we are also trying to collaborate. Should Gnome do more, what steps would be necessary to utilize Nepomuk technologies in Gnome?
* Gnome and Nepomuk? Hitherto Gnome and Nepomuk has not really been related at all. Even though Xesam and Nepomuk has its disagreements we are also trying to collaborate. Should Gnome do more, what steps would be necessary to utilize Nepomuk technologies in Gnome?
 +
* Semantic Gnome?
* Semantic Gnome?
 +
* Smarter Searching in Gnome: Keyword matching is cool, but user data is becoming more and more massive, Terabyte desktops are not unheard of. Thousands of e-mails and documents need a better ranking system.
* Smarter Searching in Gnome: Keyword matching is cool, but user data is becoming more and more massive, Terabyte desktops are not unheard of. Thousands of e-mails and documents need a better ranking system.
 +
* Xesam Ontology review and discussion. This should be very, very, high priority if you ask me. Preferably lead by Evgeny. A very good follow-up to this would be to make it continue into an ontology-documentation hackparty --[[User:kamstrup|kamstrup]] 09:53, 3 August 2008 (UTC).  
* Xesam Ontology review and discussion. This should be very, very, high priority if you ask me. Preferably lead by Evgeny. A very good follow-up to this would be to make it continue into an ontology-documentation hackparty --[[User:kamstrup|kamstrup]] 09:53, 3 August 2008 (UTC).  
** See [[Desktop_Search_Hackfest/XesamOntology|Xesam Ontology BOF and Hackfest page]]
** See [[Desktop_Search_Hackfest/XesamOntology|Xesam Ontology BOF and Hackfest page]]
 +
* Xesam Roadmap to 1.0. Set deadline for 1.0. Outline items needing to be addressed. Who does what. Etc.
* Xesam Roadmap to 1.0. Set deadline for 1.0. Outline items needing to be addressed. Who does what. Etc.
 +
* Xesam post 1.0, a BOF about Xesam's future. Xesam 1.1 features - fx. index metadata (term count), metadata storage api, see [[http://xesam.org/main/XesamIteration2]]. Xesam 2.0?
* Xesam post 1.0, a BOF about Xesam's future. Xesam 1.1 features - fx. index metadata (term count), metadata storage api, see [[http://xesam.org/main/XesamIteration2]]. Xesam 2.0?
 +
* PagedSearch for xesam (Philip is interested in leading this BOF)
* PagedSearch for xesam (Philip is interested in leading this BOF)
== Meta ==
== Meta ==
* It would be great to have RC3 of the Xesam Search spec ready at least a week or two ahead of this. It is likely to contain some (minor) API-breaks. Probably an updated xesam-glib to go with it too.
* It would be great to have RC3 of the Xesam Search spec ready at least a week or two ahead of this. It is likely to contain some (minor) API-breaks. Probably an updated xesam-glib to go with it too.
 +
* Given an updated Xesam spec it would be great to have all servers updated to the latest spec and have easy-to-set-up trunks or branches. The point is that a hack fest should not be spent with everybody trying to set up a privately circulated branch of MyGreatSearchEngine.
* Given an updated Xesam spec it would be great to have all servers updated to the latest spec and have easy-to-set-up trunks or branches. The point is that a hack fest should not be spent with everybody trying to set up a privately circulated branch of MyGreatSearchEngine.
-
== Organization ToDo ==
+
= Organization ToDo =
Steps we need to make in order to bring this forward.
Steps we need to make in order to bring this forward.
Line 191: Line 219:
*** At least blogging of the people there. Publicity in planet.gnome/planet.kde --[[User:ifrade|ifrade]] 13:49, 30 July 2008 (UTC)
*** At least blogging of the people there. Publicity in planet.gnome/planet.kde --[[User:ifrade|ifrade]] 13:49, 30 July 2008 (UTC)
Anything else? Add it to the list.
Anything else? Add it to the list.
-
 
-
[[Category:Community]]
 
-
[[Category:Development]]
 

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)