Editing Desktop Search Hackfest/Schedule

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 30: Line 30:
* Mikkel Kamstrup (host)
* Mikkel Kamstrup (host)
* Jos van den Oever
* Jos van den Oever
-
* Ben Martin
 
-
* Sebastian Trueg
 
=== Xesam MetadataStorage API ===
=== Xesam MetadataStorage API ===
Line 43: Line 41:
* Mikkel Kamstrup (host)
* Mikkel Kamstrup (host)
* Anders Rune Jensen
* Anders Rune Jensen
-
* Sebastian Trueg
 
=== Xesam Index API ===
=== Xesam Index API ===
Line 54: Line 51:
'''Attending:'''
'''Attending:'''
* Mikkel Kamstrup (host)
* Mikkel Kamstrup (host)
-
* Sebastian Trueg
 
=== Desktop Search Status report ===
=== Desktop Search Status report ===
Line 70: Line 66:
* Anders Rune Jensen
* Anders Rune Jensen
* Jos van den Oever
* Jos van den Oever
-
* Ben Martin
 
=== Xesam-Gtk a Widget Set on Top of Xesam-GLib ===
=== Xesam-Gtk a Widget Set on Top of Xesam-GLib ===
Line 127: Line 122:
* Jos van den Oever (host)
* Jos van den Oever (host)
* Mikkel Kamstrup
* Mikkel Kamstrup
-
 
-
=== Implementing Indexes on Flash ===
 
-
'''Type:''' BOF
 
-
 
-
'''Duration:''' 1h
 
-
 
-
'''Description:''' The old disk head seek time enemy is slain! But flash still is block oriented so primary memory structures mmap()ed to flash are still as unwise as ever. The BOF is a general discussion of how storing indexes (inverted files, triple stores) on flash might allow techniques that would be prohibitively slow on spinning storage.
 
-
 
-
'''Attending:'''
 
-
* Ben Martin (host)
 
-
* Mikkel Kamstrup
 
-
 
-
=== Maybe replacing inotify as the base of Desktop Search Crawling ===
 
-
'''Type:''' BOF
 
-
 
-
'''Duration:''' 1h
 
-
 
-
'''Description:''' Using inotify to monitor a collection of directories, maybe even a few hundred is fine. But if you want to monitor the entire filesystem, using something that allows all create,change,delete operations that the same UID performs to be seen would be great. Even more so on a device that is CPU/RAM contrained like the maemo ones, when the user might shove 32gb of storage and a few hundred thousand files on their mobile system.
 
-
 
-
'''Attending:'''
 
-
* Ben Martin (host)
 
-
* Mikkel Kamstrup
 
-
* Sebastian Trueg
 
-
 
-
=== Xesam support for more interfaces ===
 
-
'''Type:''' Hack session
 
-
 
-
'''Duration:''' 1h
 
-
 
-
'''Description:''' Implement basic Xesam support for a selected search interface. (ie. Avant, beagle-search, tracker-search etc.0
 
-
 
-
'''Attending:'''
 
-
* Still needs host
 
-
 
-
=== Search interface design ===
 
-
'''Type:''' BOF
 
-
 
-
'''Duration:''' 1h
 
-
 
-
'''Description:''' Whats the deal with all the different approaches to search interfaces? Lessons learned? Likes/Dislikes? What should we see in the next-gen search interface.
 
-
 
-
''Note: This BOF has a bit of overlap with the Desktop 3000 BOF. Maybe we should combine them?'' -- kamstrup
 
-
 
-
'''Attending:'''
 
-
* Still needs host
 
-
 
-
=== Make Xesam Semantic Data Ready ===
 
-
'''Type:''' BOF
 
-
 
-
'''Duration:''' 1h
 
-
 
-
'''Description:''' Xesam is a key/value system and as such is not able to provide a search on a data graph as used in Nepomuk. In this session I would like to discuss how the API can be extended to provide these features.
 
-
 
-
'''Attending:'''
 
-
Ben Martin
 
-
 
-
'''Host'''
 
-
Sebastian Trueg
 
= Schedule =
= Schedule =
Line 239: Line 176:
|-
|-
|  '''11:00-12:00'''  
|  '''11:00-12:00'''  
-
|  width="33%" | '''BOF (*) BOF Xesam Design and Critique '''
+
|  width="33%" | '''BOF Xesam Index API '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
Line 250: Line 187:
|-
|-
|  '''13:00-14:00'''  
|  '''13:00-14:00'''  
-
|  width="33%" | '''BOF Xesam Index API '''
+
|  width="33%" | '''BOF Xesam MetadataStorage API '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
Line 259: Line 196:
|-
|-
|  '''14:00-15:00'''  
|  '''14:00-15:00'''  
-
|  width="33%" | '''BOF Xesam MetadataStorage API '''
+
|  width="33%" | '''BOF (*) BOF Xesam Design and Critique '''
|  width="33%" | '''BOF  Xesam compliance testing  API '''
|  width="33%" | '''BOF  Xesam compliance testing  API '''
|  width="33%" | '''BOF (*) Sharing tags and metadata between engines when not embedded in file '''
|  width="33%" | '''BOF (*) Sharing tags and metadata between engines when not embedded in file '''
Line 301: Line 238:
|-
|-
|  '''10:00-11:00'''  
|  '''10:00-11:00'''  
-
|  width="33%" | '''Implementing Indexes on Flash'''
+
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
Line 320: Line 257:
|-
|-
|  '''13:00-14:00'''  
|  '''13:00-14:00'''  
-
|  width="33%" | '''BOF Desktop 3000  '''
+
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
Line 329: Line 266:
|-
|-
|  '''14:00-15:00'''  
|  '''14:00-15:00'''  
-
|  width="33%" | '''Maybe replacing inotify as the base of Desktop Search Crawling'''
+
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
|  width="33%" | ''' '''
Line 348: Line 285:
== Day(s) After the Official Program ==
== Day(s) After the Official Program ==
-
 
-
 
-
[[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)