Maemo Wiki Mirror - User contributions [en]

Desktop Search Hackfest/Day one notes

2008-09-21T12:49:32Z

84.22.107.1:

lightning talks

beagle
* gmail
* compatibility between extractors and similar components should be discussed about
* avahi, web services provided by the daemon itself
* online results shown in firefox
* external devices/sources working
* feature wise beagle feels they have reached a complete state
* more interested in dashboard now
* a masters student working on dashboard at the moment
* million command line tools to proof the concept
* how to tie documents and objects together (asociations) without consumin lots of processing power all the time for the creation of the associations

Strigi

* ported to mac and windows
* Basic requirement of kde4
* modularized into 4 c++ libraries
* libstreams
* efficient access to files as streams
* reading nested streams without overhead: no copying of intermediate data
* tar, bz2, zip, rpm, deb pdf, ole2, mail, .a
* jstream://
* Efficient for actually getting inner contents of objects without the need to create intermediate copy of the objects
* libstreamanalyzer
* api for accessing metadata from streams
* uses libstreams
* uses 5 plugins for analyzers, each optimized for speed of specific data type
* most analyzers can be used in parallel
* all analyzers always run, with little overhead
* index object is getting the data from each content item
* analyzers also run on the embedded filescontent
* plugins for the indexes, so in theory different indexes can be used
* most important clucene and soprano
* clucene very fast
* soprano used for nepomuk for semantic storage
* could use tracker as the index as well
* libseachclient
* socket access to strigidaemon
* libstrigihtmlgui
* libstrigiqtdbusclient
* strigidaemon
* c++
* relativelhy little code in the daemon
* abstract interface for communications
* thread pool
* initial xesam support, partially shared with pinot
* POWER OF STRIGI IN IN LIBRARIES THAT CAN BE SHARED

Xesam
* sd
* Using mirror
* beginnint - dashbar used in beginning
* seemed poor to make compatibility layer for all engines (strigi, beagle, ...)
* unite existing apis
* hide implementation details of backends
* allow simpler indexes such as grepp
* support for web services such as google
* keeping it simple was the leading thought
* does not support everything, but instead mostly desktop and mobile devices
* keep low barrier of entry
* preoactive openess
* community effort
* history
* 2 apis
* simple query and 'live'
* simple api was too simple - so, live was the way to go
* xesam
* dbus search api
* ontology
* xml query language
* user search language
* full draft online - devil in the details
* summarizing critic:
* too complex onto
* feature creeping (it's etting too complex)
* not extensible enough
* vulnerability to extend and embrace tactics

tracker
* last half year
* work has revolved around splitting daemon and indexer into separate entities
* extractor process spwns and pipes data to the indexer
* filters handle the files
* weighting data items as 'hot' based on the headingness or boldness
* daemon has proper introspection
* dbus api has had only a little changes
* planning to change that quite a lot to support xesam
* throttling - pausing indexing with monitoring events, nice, dynamic blacklisting of files, (blacklisting of dirs?)
* q: wrapper of streamanalyzer?
* kde4 metadata extraction using streamanalyzers - all metadata provided with those
* suggestion for traker to consider streamanalyzers
* Suggestion from kubasic, jos, jamie: use a common extraction pipeing model
* jos: suggestion to not to use dbus between the extractor and daemon process
* daemon only there to service the data
* indexer there to handle the writing of the actual data
* suggestion to keep this in tips and tricks session
* last issue before merge - fix jamies tst on his laptop
*

ontologies:
* evgeny giving introduction
* basic design decisions
* why rdf triples
* inheritance needed
* gives example of hierarchy (xesam:contributor in core, client extension this as xesam:majorContributor and xesam:minorContributor)
* this makes applications that do not know of the cleint extensions to be able to interoperate with the data
* How many features we want to implement. 95% (but not more?)
* idea to drop corner cases
* not only what features we implement but also to implement those well, this will lead to change in user habits (example file navigation used to cover 95% of file location needs . after indexers, this can be dimished to 60-70% - but only if indexers work well, are reliable and easy to use)
* thus, we need simple enough fw that is powerful enough, but easy enough to implement and start to use
* content and source split
* source is that the file is and how is it stored
* content deals with documents, messages and such
* for the content tree, it does not matter how it is stored
* source is the place for acl
* document has the created date - it is the actual created date of the document
* source created date is the filesystem level creation date
* also modified on source could be when e.g. acl was changed, on document tree, changed means when someone actually edited the document
* evgeny gives example of a scientific paper
* xesam:author links the item to xesam:contact
* the xesam:contact - country could be e.g. UK
* now, if we want to find list documents of people from uk
* the multiple query solution for this use case can be very slow to implement if the contects contain tens of thousands of people
* so, the dbus traffic is unnecessarily large
* and there are many other use cases of this type of relationships that will be too difficult to implement with the current xesam model efficiently
* photo annotations
* defining region of a photo and who is there
* thus, the annotation is complex
* example - photos of old people
* move toward semantic representation of data. FOF example of the photo annotations
* semantic web activities going on in this area at the moment
* another example: papers referring it to other papers via identifiers without directly pointing to a file
* point being that the client will have to be doing the work that really makes sense to be done on the backend side
* suggestion: use xesam (tm) if it correctly implements the core set of the functionality
* we will need to be future proof and not stagnate and have people making hacks and workarounds
* philip van hoof: standard will be successful only if the client developers take it to use
* martyn: it's an iterative process
* client developers are our users
* using xesam needs to be easy and it needs to be able to provide easily the needed information
* evgeny: how do we solve this conflict of interest: we need to define xesam in flexible enough way
* evgeny: it is not simple enough for the users as it is
* mikkel: two camps: semantic camp and field based camp, my opinion is more on the field based camp - thus, I don't see the needs of this type very relevant for our needs
* kubasic: I agree that mutidimensional graphs not so interesting - maybe we could provide a convenience library to do this kind of depth relationships. So, perhaps xesam could just provide the field based stuff and let the wrappers worry about the more extended multidimensional use cases
* evgeny: my opinion would be to make it possible for the backend to be able to do this and provide the wrapper for the simple backends to do the field too graph use cases.
* maybe we could roadmap that only some parts would be available of the query language and ontology so that
* kubasic: if we do paged browsing the deeper relationships will be completely awful to be implement efficiently - so most often the deeper levels should not be so needed to be done
* evgeny: this need will either be implemented by the cleint or the server. use cases are there
* jos: can you provide a list of items to change
* evgeny: we need to decide whether we want to support these structures or not
* evgeny: can provide list of drawbacks
* current situation undecided what is the type of the e.g. author (reference as url or string of the author) - needs to be decided
* sebastian: <missed>
* jos: my suggestion - if I have author email address - then we go to the next version, where we have contacts - I will store the contact url t database
* urho: suggesting inner queries to the query api
* evgeny: let me give more examples
* sparql - and current query language
*
* we can replace the current query language later on
* jamie: the mapping really doesn't exist on the actual contents, so the documents usually don't map the actual authors, but instead they just contain the freetext of the authors
* so, as long as the applications do not contain the possibilities, the graphs won't happen
* evgeny: we need to make it possible for the applications to do this, otherwise the applications wil lnever support it
* sebastian: shouldn't we make the inner queries optional as well as the graph queries
* intermediate solution - flat view would map queries to text and on the graph capable implementations to the object url instead
* possiblity to create dummy items for each url and containing the string in that object
* qubasic: this will be needing lot of more support from the backend will be needed and it will be much more complicated to do - would be more future compatible to be on the xesam
* sebastian: internal stuff could create the internal representations in hackish way and just expose the data in graph way
* evgeny: proposing a far reaching goal to make it easy for users in mid term future to transition to this - maybe roadmat for applications to be able to produce more complex queries
* Urho: so, do you propose SPARQL?
* evgeny: nope - we should be able to extend current XML
* sebastian: we could create related to inner queries
* mikkel: why not jus tallow the results of one query to be source for the next one
* urho: so inner queries - yeah
* evgeny: makes an example of the paper question in sparql
* evgeny: we are not looking for using sparql, just similar functionality
* evgeny: mapping sparql to sql can be done
* jos: I propose that we won't implement this to 1.0
* just make the ontology as future proof
* make a temporary solution and future path
* evgeny: list of use cases
* we have no way to query - semantic desktop guys will not be able to use xesam in the way they can use nepomuk
* maybe we could at least make a wrapper library?
* JOS: making the proposal
* usually we store the name of author in a field on document
* in graph we would store it on separate object
* so, propose that we do it like this now and if engine supports the denormalized model, it will do the conversion from the object to the name
* and we extend the ontology the denormalized way
* sebastian: we have the proper ontology in nepomuk, we could just translate that to xesam
* qubasik: suggest that we make a small team to discuss this in real detail
* agreed: 1st item: FAIL -

Search API (d-bus api)
* Notes taking by urho
* latest changes for sorting and some session properties
* we simply list all the problems that people have with it
* inner queries agreed to be handled separately
* jamie raising issue of ranged search
* philip: why don't we remove the session completely - it's completely unused
* jos: i'll explain the session - it's for live queries
* you can have multiple searches per session
* search thus should have a separate id so that that can be closed, there is no need for the session at all
* kubasic:
* rob: you need to know what searches are running
* mikkel: if we create the session at the time of the start
* martyn: we need to have a separate id for searches
* rob: we have a separate id for searches
* can't we add the properties to the query itself?
* go for large and infrequent messages
* kubasik: we should decide whether to use the properties on the xml or on the dbus
* mikkel: properties can go on the search object instead (written)
* philip: I agree with sebastian (sebastian) hit fields should be in the query
* philip: we can go instead for the session changes to be for the xesam 2.0 and not yet to the 1.0
* philip: if we change the query language, that'll break everything anyway
* rob: seems like you are using ids for the objects on the server side - perhaps they actually should be d-bus objects
* jos: so, current model is imperfect, but enough for 1.0
* jos: let's keep it like it is for now as it's works
* versioning discussion - should dbus have the version number in the dbus namespace?
* rob checks- yes you can
* kubasik: we need to have a bit of better way to decide which engine to use
* but we don't need to specify the way to do it
* philip: we should have announcement of capabilities to allow applications to choose the right engine with the right capabilities
* kubasik: distributions need to be taken into account here
* mikkel: we need to have the documentation about the capabilities and make the apis to discover
* mikkel: can be considered for 1.0 (at least guidelines)
* let's make a group to specify this
* jos: gethitdata will be capable of handling the ranges quite easily as it's capable
* urho: we have the case where hitsadded hit is on a sorted live query and on place on the visible resultset. without the id and uri of the hitadded, you will have to re-query your entire set
* kubasik: most of the time the issue is really that single item has been modified
* mikkel: so, we would emit: livehitsadded
* jos: live search never sends researchdone
* mikkel: yes it sends once the indexing is done
* mikkel: let's add livesearch added that would contain also the hit metadata
* jos: we need to minimize the changes needed
* everyone can live with even the paging
* jamie: so, no changes for 1.0 for hitsadded, but for 2.0 yes
* jos: idea for ranged search will mean that we supply the ids of the hits
* michael: d-bus api
* sometimes several search engines in parallel is an issue
* one engine refuses to start if d-bus api not available
* we should make search engines to que on d-bus
* no way to decide which engine is started
* mikkel: we have also xesam interface on tracker, so that can be used org.freedesktop.tracker.xesam?
* philip: we don't
* mikkel: perhpas that would be a recommendation
* urho: how about org.freedesktop.xesam.tracker and org.freedesktop.beagle
* mikkel: good idea
* michael raising issues about the specialist engines existing on the same system
* philip: wants to raise something
* this suggestion is unimplementable on sqlite as it is
* ottela: we get hits 1 - 1000 - we change the value of item 1 to be last on the list
* ottela: if one file changes - hitsmodified tells that one changed to 1000 and 2 changed to 1, 3 to 2,...
* jos: why don't we say the gethitsdata needs to be sequential
* philip: the issues with 1, 10000, 500 will mean the complexity of the corner cases will become very difficulta
* and this will make it quite complex to do properly on the server side
* <discussion that has been too hard to type on the report>
* urho: how about adding getrangedhits
* jos: if we don't remove the gethisdata that already exists
* agreed by everyone
* martyn: I'd rather have a new hitsmoved rather than having the hitsremoved and hitsadded
* jos: currently the positionshould not be changing?
* kubasik explains beagle issues
* martyn: sounds nice, but the issue is that the new api would make it more clear for the client applications to use
* kubasik: it's going to be difficult to implement the live queries
* martyn: surely we should add the possibility to handle the things without the need to re-create the live query
* sebastian: how about another working group?
* mikkel agreed:
* so, group to discuss the live sorting and hits added / moved issue
* kubasik: we'll have the group and I can tell how beagle is doing this
* mikkel: one for this and another group for the accessibility
* sebastian proposes to use floating points for the ordering
* ben raises the issue that how hard will it be possible to sort by the strings, the text
* Mikkel: live query sorting who is the group?
* Jos: I don't think live queries will be efficiently possible on the server side
* group: half and hour - jos, martyn, kubasik, mikael, mikkel (?)
* LUNCH

Ontology discussion:
Link by id - mikkel presenting on postits
* evgenys idea originally as a middle way between semantic graph and the current xesam
* problem is mainly linking relate objects (like linkin document and author) or document contained in an email
* referring e.g. two documents together with isbn
* there are multiple ids (not just uris)
* they will need to be 'sufficiently unique'
* Solving the problem
* xesam id field (any child of it must have a value that is unique over all xesam ids)
* all of the links must always be to ids
* we make a new special kind of field that is child of xesam:related or could be a special data type
* should always hold xesam id
* with this we can find all objects that point to X (or any that X points to)
* so, e.g. pdf file reference isbn - query xesam id field with that isbn
*
* sebastian: subqueries should be enough to allow good usage of this on the search api
* urho: agreed
* Everybody agrees to investigate the idea
* mikkel: suggest using a new field in xesam api id-field
* kubasik: we would need to do nested queries most probably and not probably an optimized index for this
* sebastian: normally you would say give me all emails htat have sender of contact object that has name like this
* now you could do it sender as a range, of person object, it would check all xesam id values in the relation
* mikkel: it shoud be very easy to do these queries
* and it should be very easy to show the values of these fields
* jos: we should do so that we do two fields: radable valua and pointer/relation property. Also, the more strong engines could say that the value is just an alias of the actual objects relations property
* sebastian: why not use the uri for data representation plugins that would then be able to create the visible widgets of the data items
* sebastian: i see that there are some issues with people wanting to not to do two queries
* evgeny: you would need inference for it and it's easier so that we make it so that xesam:strings: would contain the string representation of the url / link values.
* so, this way, we only use the string representation for only full text search.
* evgeny: I feel that we have a bit of problem on the specification of what should be in the FTI
* Anders: we need to also be able to show how/why the relation was created and to be able to do that for all the related content
* evgeny: we cannot have the stuff linking to everything on the database
* sebastian: we don't need to present on how a relation was found and it's a GUI thing
* jamie: two fields would be more clean
* jamie draws example below evgenys example
* jos agrees on the two field model
* evgeny isn't completely convinced
* the point is that the UI will likely match the actual contact
* jamie: this way the application would have the choice
* jamie: if we have just a name on the author text, then we don't want to try to create the dummy object
* evgeny: compromise solution in my opinion is that if we have to use have use the subqueries
* discussion on that we want a value of properties on a single query on xesam
* jamie: we could always deprecate the fields
* jos: i liked the suggestion of author text and author link and group the fields on a string text
* sebastian: why not make all dummy objects to have the same data layout
* at least the data is syntatically correct if we use dummy objects
* jamie: it's not worth it if we don't have the semantic info
* sebastian: this way we handle the data in same way for the 'proper' objects as well as the dummy ones
* <lots of discussion>
* Conclusion:
* We make some older strings as URIs instead of the previous string values
* All new URI properties also have a .label that allows to get the textual representation of the property, which in essence is the old xesam ontology value of the property. The ideal is that this is a pointer to a specific property of the linked object
* We will draft nested queries and they will most probably go to 1.1
*

Desktop Search Hackfest/Day one notes

2008-09-21T12:47:53Z

84.22.107.1:

lightning talks

beagle
* gmail
* compatibility between extractors and similar components should be discussed about
* avahi, web services provided by the daemon itself
* online results shown in firefox
* external devices/sources working
* feature wise beagle feels they have reached a complete state
* more interested in dashboard now
* a masters student working on dashboard at the moment
* million command line tools to proof the concept
* how to tie documents and objects together (asociations) without consumin lots of processing power all the time for the creation of the associations

Strigi

* ported to mac and windows
* Basic requirement of kde4
* modularized into 4 c++ libraries
* libstreams
* efficient access to files as streams
* reading nested streams without overhead: no copying of intermediate data
* tar, bz2, zip, rpm, deb pdf, ole2, mail, .a
* jstream://
* Efficient for actually getting inner contents of objects without the need to create intermediate copy of the objects
* libstreamanalyzer
* api for accessing metadata from streams
* uses libstreams
* uses 5 plugins for analyzers, each optimized for speed of specific data type
* most analyzers can be used in parallel
* all analyzers always run, with little overhead
* index object is getting the data from each content item
* analyzers also run on the embedded filescontent
* plugins for the indexes, so in theory different indexes can be used
* most important clucene and soprano
* clucene very fast
* soprano used for nepomuk for semantic storage
* could use tracker as the index as well
* libseachclient
* socket access to strigidaemon
* libstrigihtmlgui
* libstrigiqtdbusclient
* strigidaemon
* c++
* relativelhy little code in the daemon
* abstract interface for communications
* thread pool
* initial xesam support, partially shared with pinot
* POWER OF STRIGI IN IN LIBRARIES THAT CAN BE SHARED

Xesam
* sd
* Using mirror
* beginnint - dashbar used in beginning
* seemed poor to make compatibility layer for all engines (strigi, beagle, ...)
* unite existing apis
* hide implementation details of backends
* allow simpler indexes such as grepp
* support for web services such as google
* keeping it simple was the leading thought
* does not support everything, but instead mostly desktop and mobile devices
* keep low barrier of entry
* preoactive openess
* community effort
* history
* 2 apis
* simple query and 'live'
* simple api was too simple - so, live was the way to go
* xesam
* dbus search api
* ontology
* xml query language
* user search language
* full draft online - devil in the details
* summarizing critic:
* too complex onto
* feature creeping (it's etting too complex)
* not extensible enough
* vulnerability to extend and embrace tactics

tracker
* last half year
* work has revolved around splitting daemon and indexer into separate entities
* extractor process spwns and pipes data to the indexer
* filters handle the files
* weighting data items as 'hot' based on the headingness or boldness
* daemon has proper introspection
* dbus api has had only a little changes
* planning to change that quite a lot to support xesam
* throttling - pausing indexing with monitoring events, nice, dynamic blacklisting of files, (blacklisting of dirs?)
* q: wrapper of streamanalyzer?
* kde4 metadata extraction using streamanalyzers - all metadata provided with those
* suggestion for traker to consider streamanalyzers
* Suggestion from kubasic, jos, jamie: use a common extraction pipeing model
* jos: suggestion to not to use dbus between the extractor and daemon process
* daemon only there to service the data
* indexer there to handle the writing of the actual data
* suggestion to keep this in tips and tricks session
* last issue before merge - fix jamies tst on his laptop
*

ontologies:
* evgeny giving introduction
* basic design decisions
* why rdf triples
* inheritance needed
* gives example of hierarchy (xesam:contributor in core, client extension this as xesam:majorContributor and xesam:minorContributor)
* this makes applications that do not know of the cleint extensions to be able to interoperate with the data
* How many features we want to implement. 95% (but not more?)
* idea to drop corner cases
* not only what features we implement but also to implement those well, this will lead to change in user habits (example file navigation used to cover 95% of file location needs . after indexers, this can be dimished to 60-70% - but only if indexers work well, are reliable and easy to use)
* thus, we need simple enough fw that is powerful enough, but easy enough to implement and start to use
* content and source split
* source is that the file is and how is it stored
* content deals with documents, messages and such
* for the content tree, it does not matter how it is stored
* source is the place for acl
* document has the created date - it is the actual created date of the document
* source created date is the filesystem level creation date
* also modified on source could be when e.g. acl was changed, on document tree, changed means when someone actually edited the document
* evgeny gives example of a scientific paper
* xesam:author links the item to xesam:contact
* the xesam:contact - country could be e.g. UK
* now, if we want to find list documents of people from uk
* the multiple query solution for this use case can be very slow to implement if the contects contain tens of thousands of people
* so, the dbus traffic is unnecessarily large
* and there are many other use cases of this type of relationships that will be too difficult to implement with the current xesam model efficiently
* photo annotations
* defining region of a photo and who is there
* thus, the annotation is complex
* example - photos of old people
* move toward semantic representation of data. FOF example of the photo annotations
* semantic web activities going on in this area at the moment
* another example: papers referring it to other papers via identifiers without directly pointing to a file
* point being that the client will have to be doing the work that really makes sense to be done on the backend side
* suggestion: use xesam (tm) if it correctly implements the core set of the functionality
* we will need to be future proof and not stagnate and have people making hacks and workarounds
* philip van hoof: standard will be successful only if the client developers take it to use
* martyn: it's an iterative process
* client developers are our users
* using xesam needs to be easy and it needs to be able to provide easily the needed information
* evgeny: how do we solve this conflict of interest: we need to define xesam in flexible enough way
* evgeny: it is not simple enough for the users as it is
* mikkel: two camps: semantic camp and field based camp, my opinion is more on the field based camp - thus, I don't see the needs of this type very relevant for our needs
* kubasic: I agree that mutidimensional graphs not so interesting - maybe we could provide a convenience library to do this kind of depth relationships. So, perhaps xesam could just provide the field based stuff and let the wrappers worry about the more extended multidimensional use cases
* evgeny: my opinion would be to make it possible for the backend to be able to do this and provide the wrapper for the simple backends to do the field too graph use cases.
* maybe we could roadmap that only some parts would be available of the query language and ontology so that
* kubasic: if we do paged browsing the deeper relationships will be completely awful to be implement efficiently - so most often the deeper levels should not be so needed to be done
* evgeny: this need will either be implemented by the cleint or the server. use cases are there
* jos: can you provide a list of items to change
* evgeny: we need to decide whether we want to support these structures or not
* evgeny: can provide list of drawbacks
* current situation undecided what is the type of the e.g. author (reference as url or string of the author) - needs to be decided
* nepomuk guy: <missed>
* jos: my suggestion - if I have author email address - then we go to the next version, where we have contacts - I will store the contact url t database
* urho: suggesting inner queries to the query api
* evgeny: let me give more examples
* sparql - and current query language
*
* we can replace the current query language later on
* jamie: the mapping really doesn't exist on the actual contents, so the documents usually don't map the actual authors, but instead they just contain the freetext of the authors
* so, as long as the applications do not contain the possibilities, the graphs won't happen
* evgeny: we need to make it possible for the applications to do this, otherwise the applications wil lnever support it
* nepomuk guy: shouldn't we make the inner queries optional as well as the graph queries
* intermediate solution - flat view would map queries to text and on the graph capable implementations to the object url instead
* possiblity to create dummy items for each url and containing the string in that object
* qubasic: this will be needing lot of more support from the backend will be needed and it will be much more complicated to do - would be more future compatible to be on the xesam
* nepomuk guy: internal stuff could create the internal representations in hackish way and just expose the data in graph way
* evgeny: proposing a far reaching goal to make it easy for users in mid term future to transition to this - maybe roadmat for applications to be able to produce more complex queries
* Urho: so, do you propose SPARQL?
* evgeny: nope - we should be able to extend current XML
* nepomuk guy: we could create related to inner queries
* mikkel: why not jus tallow the results of one query to be source for the next one
* urho: so inner queries - yeah
* evgeny: makes an example of the paper question in sparql
* evgeny: we are not looking for using sparql, just similar functionality
* evgeny: mapping sparql to sql can be done
* jos: I propose that we won't implement this to 1.0
* just make the ontology as future proof
* make a temporary solution and future path
* evgeny: list of use cases
* we have no way to query - semantic desktop guys will not be able to use xesam in the way they can use nepomuk
* maybe we could at least make a wrapper library?
* JOS: making the proposal
* usually we store the name of author in a field on document
* in graph we would store it on separate object
* so, propose that we do it like this now and if engine supports the denormalized model, it will do the conversion from the object to the name
* and we extend the ontology the denormalized way
* nepomuk guy: we have the proper ontology in nepomuk, we could just translate that to xesam
* qubasik: suggest that we make a small team to discuss this in real detail
* agreed: 1st item: FAIL -

Search API (d-bus api)
* Notes taking by urho
* latest changes for sorting and some session properties
* we simply list all the problems that people have with it
* inner queries agreed to be handled separately
* jamie raising issue of ranged search
* philip: why don't we remove the session completely - it's completely unused
* jos: i'll explain the session - it's for live queries
* you can have multiple searches per session
* search thus should have a separate id so that that can be closed, there is no need for the session at all
* kubasic:
* rob: you need to know what searches are running
* mikkel: if we create the session at the time of the start
* martyn: we need to have a separate id for searches
* rob: we have a separate id for searches
* can't we add the properties to the query itself?
* go for large and infrequent messages
* kubasik: we should decide whether to use the properties on the xml or on the dbus
* mikkel: properties can go on the search object instead (written)
* philip: I agree with sebastian (nepomuk guy) hit fields should be in the query
* philip: we can go instead for the session changes to be for the xesam 2.0 and not yet to the 1.0
* philip: if we change the query language, that'll break everything anyway
* rob: seems like you are using ids for the objects on the server side - perhaps they actually should be d-bus objects
* jos: so, current model is imperfect, but enough for 1.0
* jos: let's keep it like it is for now as it's works
* versioning discussion - should dbus have the version number in the dbus namespace?
* rob checks- yes you can
* kubasik: we need to have a bit of better way to decide which engine to use
* but we don't need to specify the way to do it
* philip: we should have announcement of capabilities to allow applications to choose the right engine with the right capabilities
* kubasik: distributions need to be taken into account here
* mikkel: we need to have the documentation about the capabilities and make the apis to discover
* mikkel: can be considered for 1.0 (at least guidelines)
* let's make a group to specify this
* jos: gethitdata will be capable of handling the ranges quite easily as it's capable
* urho: we have the case where hitsadded hit is on a sorted live query and on place on the visible resultset. without the id and uri of the hitadded, you will have to re-query your entire set
* kubasik: most of the time the issue is really that single item has been modified
* mikkel: so, we would emit: livehitsadded
* jos: live search never sends researchdone
* mikkel: yes it sends once the indexing is done
* mikkel: let's add livesearch added that would contain also the hit metadata
* jos: we need to minimize the changes needed
* everyone can live with even the paging
* jamie: so, no changes for 1.0 for hitsadded, but for 2.0 yes
* jos: idea for ranged search will mean that we supply the ids of the hits
* michael: d-bus api
* sometimes several search engines in parallel is an issue
* one engine refuses to start if d-bus api not available
* we should make search engines to que on d-bus
* no way to decide which engine is started
* mikkel: we have also xesam interface on tracker, so that can be used org.freedesktop.tracker.xesam?
* philip: we don't
* mikkel: perhpas that would be a recommendation
* urho: how about org.freedesktop.xesam.tracker and org.freedesktop.beagle
* mikkel: good idea
* michael raising issues about the specialist engines existing on the same system
* philip: wants to raise something
* this suggestion is unimplementable on sqlite as it is
* ottela: we get hits 1 - 1000 - we change the value of item 1 to be last on the list
* ottela: if one file changes - hitsmodified tells that one changed to 1000 and 2 changed to 1, 3 to 2,...
* jos: why don't we say the gethitsdata needs to be sequential
* philip: the issues with 1, 10000, 500 will mean the complexity of the corner cases will become very difficulta
* and this will make it quite complex to do properly on the server side
* <discussion that has been too hard to type on the report>
* urho: how about adding getrangedhits
* jos: if we don't remove the gethisdata that already exists
* agreed by everyone
* martyn: I'd rather have a new hitsmoved rather than having the hitsremoved and hitsadded
* jos: currently the positionshould not be changing?
* kubasik explains beagle issues
* martyn: sounds nice, but the issue is that the new api would make it more clear for the client applications to use
* kubasik: it's going to be difficult to implement the live queries
* martyn: surely we should add the possibility to handle the things without the need to re-create the live query
* sebastian: how about another working group?
* mikkel agreed:
* so, group to discuss the live sorting and hits added / moved issue
* kubasik: we'll have the group and I can tell how beagle is doing this
* mikkel: one for this and another group for the accessibility
* sebastian proposes to use floating points for the ordering
* ben raises the issue that how hard will it be possible to sort by the strings, the text
* Mikkel: live query sorting who is the group?
* Jos: I don't think live queries will be efficiently possible on the server side
* group: half and hour - jos, martyn, kubasik, mikael, mikkel (?)
* LUNCH

Ontology discussion:
Link by id - mikkel presenting on postits
* evgenys idea originally as a middle way between semantic graph and the current xesam
* problem is mainly linking relate objects (like linkin document and author) or document contained in an email
* referring e.g. two documents together with isbn
* there are multiple ids (not just uris)
* they will need to be 'sufficiently unique'
* Solving the problem
* xesam id field (any child of it must have a value that is unique over all xesam ids)
* all of the links must always be to ids
* we make a new special kind of field that is child of xesam:related or could be a special data type
* should always hold xesam id
* with this we can find all objects that point to X (or any that X points to)
* so, e.g. pdf file reference isbn - query xesam id field with that isbn
*
* sebastian: subqueries should be enough to allow good usage of this on the search api
* urho: agreed
* Everybody agrees to investigate the idea
* mikkel: suggest using a new field in xesam api id-field
* kubasik: we would need to do nested queries most probably and not probably an optimized index for this
* sebastian: normally you would say give me all emails htat have sender of contact object that has name like this
* now you could do it sender as a range, of person object, it would check all xesam id values in the relation
* mikkel: it shoud be very easy to do these queries
* and it should be very easy to show the values of these fields
* jos: we should do so that we do two fields: radable valua and pointer/relation property. Also, the more strong engines could say that the value is just an alias of the actual objects relations property
* sebastian: why not use the uri for data representation plugins that would then be able to create the visible widgets of the data items
* sebastian: i see that there are some issues with people wanting to not to do two queries
* evgeny: you would need inference for it and it's easier so that we make it so that xesam:strings: would contain the string representation of the url / link values.
* so, this way, we only use the string representation for only full text search.
* evgeny: I feel that we have a bit of problem on the specification of what should be in the FTI
* Anders: we need to also be able to show how/why the relation was created and to be able to do that for all the related content
* evgeny: we cannot have the stuff linking to everything on the database
* sebastian: we don't need to present on how a relation was found and it's a GUI thing
* jamie: two fields would be more clean
* jamie draws example below evgenys example
* jos agrees on the two field model
* evgeny isn't completely convinced
* the point is that the UI will likely match the actual contact
* jamie: this way the application would have the choice
* jamie: if we have just a name on the author text, then we don't want to try to create the dummy object
* evgeny: compromise solution in my opinion is that if we have to use have use the subqueries
* discussion on that we want a value of properties on a single query on xesam
* jamie: we could always deprecate the fields
* jos: i liked the suggestion of author text and author link and group the fields on a string text
* sebastian: why not make all dummy objects to have the same data layout
* at least the data is syntatically correct if we use dummy objects
* jamie: it's not worth it if we don't have the semantic info
* sebastian: this way we handle the data in same way for the 'proper' objects as well as the dummy ones
* <lots of discussion>
* Conclusion:
* We make some older strings as URIs instead of the previous string values
* All new URI properties also have a .label that allows to get the textual representation of the property, which in essence is the old xesam ontology value of the property. The ideal is that this is a pointer to a specific property of the linked object
* We will draft nested queries and they will most probably go to 1.1
*

Desktop Search Hackfest/Day one notes

2008-09-21T12:47:19Z

84.22.107.1:

lightning talks

beagle
* gmail
* compatibility between extractors and similar components should be discussed about
* avahi, web services provided by the daemon itself
* online results shown in firefox
* external devices/sources working
* feature wise beagle feels they have reached a complete state
* more interested in dashboard now
* a masters student working on dashboard at the moment
* million command line tools to proof the concept
* how to tie documents and objects together (asociations) without consumin lots of processing power all the time for the creation of the associations

Strigi

* ported to mac and windows
* Basic requirement of kde4
* modularized into 4 c++ libraries
* libstreams
* efficient access to files as streams
* reading nested streams without overhead: no copying of intermediate data
* tar, bz2, zip, rpm, deb pdf, ole2, mail, .a
* jstream://
‣ Efficient for actually getting inner contents of objects without the need to create intermediate copy of the objects
* libstreamanalyzer
* api for accessing metadata from streams
* uses libstreams
* uses 5 plugins for analyzers, each optimized for speed of specific data type
* most analyzers can be used in parallel
* all analyzers always run, with little overhead
* index object is getting the data from each content item
* analyzers also run on the embedded filescontent
* plugins for the indexes, so in theory different indexes can be used
‣ most important clucene and soprano
* clucene very fast
* soprano used for nepomuk for semantic storage
‣ could use tracker as the index as well
* libseachclient
* socket access to strigidaemon
* libstrigihtmlgui
* libstrigiqtdbusclient
* strigidaemon
* c++
* relativelhy little code in the daemon
* abstract interface for communications
* thread pool
* initial xesam support, partially shared with pinot
* POWER OF STRIGI IN IN LIBRARIES THAT CAN BE SHARED

Xesam
* sd
* Using mirror
* beginnint - dashbar used in beginning
* seemed poor to make compatibility layer for all engines (strigi, beagle, ...)
* unite existing apis
* hide implementation details of backends
* allow simpler indexes such as grepp
* support for web services such as google
* keeping it simple was the leading thought
* does not support everything, but instead mostly desktop and mobile devices
* keep low barrier of entry
* preoactive openess
* community effort
* history
* 2 apis
* simple query and 'live'
* simple api was too simple - so, live was the way to go
* xesam
‣ dbus search api
‣ ontology
‣ xml query language
‣ user search language
* full draft online - devil in the details
* summarizing critic:
‣ too complex onto
‣ feature creeping (it's etting too complex)
‣ not extensible enough
‣ vulnerability to extend and embrace tactics

tracker
* last half year
* work has revolved around splitting daemon and indexer into separate entities
* extractor process spwns and pipes data to the indexer
* filters handle the files
* weighting data items as 'hot' based on the headingness or boldness
* daemon has proper introspection
* dbus api has had only a little changes
* planning to change that quite a lot to support xesam
* throttling - pausing indexing with monitoring events, nice, dynamic blacklisting of files, (blacklisting of dirs?)
* q: wrapper of streamanalyzer?
* kde4 metadata extraction using streamanalyzers - all metadata provided with those
* suggestion for traker to consider streamanalyzers
* Suggestion from kubasic, jos, jamie: use a common extraction pipeing model
* jos: suggestion to not to use dbus between the extractor and daemon process
* daemon only there to service the data
* indexer there to handle the writing of the actual data
* suggestion to keep this in tips and tricks session
* last issue before merge - fix jamies tst on his laptop
*

ontologies:
* evgeny giving introduction
* basic design decisions
* why rdf triples
* inheritance needed
* gives example of hierarchy (xesam:contributor in core, client extension this as xesam:majorContributor and xesam:minorContributor)
* this makes applications that do not know of the cleint extensions to be able to interoperate with the data
* How many features we want to implement. 95% (but not more?)
* idea to drop corner cases
* not only what features we implement but also to implement those well, this will lead to change in user habits (example file navigation used to cover 95% of file location needs . after indexers, this can be dimished to 60-70% - but only if indexers work well, are reliable and easy to use)
* thus, we need simple enough fw that is powerful enough, but easy enough to implement and start to use
* content and source split
* source is that the file is and how is it stored
* content deals with documents, messages and such
* for the content tree, it does not matter how it is stored
* source is the place for acl
* document has the created date - it is the actual created date of the document
* source created date is the filesystem level creation date
* also modified on source could be when e.g. acl was changed, on document tree, changed means when someone actually edited the document
* evgeny gives example of a scientific paper
* xesam:author links the item to xesam:contact
* the xesam:contact - country could be e.g. UK
* now, if we want to find list documents of people from uk
* the multiple query solution for this use case can be very slow to implement if the contects contain tens of thousands of people
* so, the dbus traffic is unnecessarily large
* and there are many other use cases of this type of relationships that will be too difficult to implement with the current xesam model efficiently
* photo annotations
‣ defining region of a photo and who is there
‣ thus, the annotation is complex
‣ example - photos of old people
‣ move toward semantic representation of data. FOF example of the photo annotations
‣ semantic web activities going on in this area at the moment
‣ another example: papers referring it to other papers via identifiers without directly pointing to a file
‣ point being that the client will have to be doing the work that really makes sense to be done on the backend side
‣ suggestion: use xesam (tm) if it correctly implements the core set of the functionality
‣ we will need to be future proof and not stagnate and have people making hacks and workarounds
‣ philip van hoof: standard will be successful only if the client developers take it to use
‣ martyn: it's an iterative process
‣ client developers are our users
‣ using xesam needs to be easy and it needs to be able to provide easily the needed information
‣ evgeny: how do we solve this conflict of interest: we need to define xesam in flexible enough way
‣ evgeny: it is not simple enough for the users as it is
‣ mikkel: two camps: semantic camp and field based camp, my opinion is more on the field based camp - thus, I don't see the needs of this type very relevant for our needs
‣ kubasic: I agree that mutidimensional graphs not so interesting - maybe we could provide a convenience library to do this kind of depth relationships. So, perhaps xesam could just provide the field based stuff and let the wrappers worry about the more extended multidimensional use cases
‣ evgeny: my opinion would be to make it possible for the backend to be able to do this and provide the wrapper for the simple backends to do the field too graph use cases.
‣ maybe we could roadmap that only some parts would be available of the query language and ontology so that
‣ kubasic: if we do paged browsing the deeper relationships will be completely awful to be implement efficiently - so most often the deeper levels should not be so needed to be done
‣ evgeny: this need will either be implemented by the cleint or the server. use cases are there
‣ jos: can you provide a list of items to change
‣ evgeny: we need to decide whether we want to support these structures or not
‣ evgeny: can provide list of drawbacks
‣ current situation undecided what is the type of the e.g. author (reference as url or string of the author) - needs to be decided
‣ nepomuk guy: <missed>
‣ jos: my suggestion - if I have author email address - then we go to the next version, where we have contacts - I will store the contact url t database
‣ urho: suggesting inner queries to the query api
‣ evgeny: let me give more examples
* sparql - and current query language
*
* we can replace the current query language later on
‣ jamie: the mapping really doesn't exist on the actual contents, so the documents usually don't map the actual authors, but instead they just contain the freetext of the authors
‣ so, as long as the applications do not contain the possibilities, the graphs won't happen
‣ evgeny: we need to make it possible for the applications to do this, otherwise the applications wil lnever support it
‣ nepomuk guy: shouldn't we make the inner queries optional as well as the graph queries
* intermediate solution - flat view would map queries to text and on the graph capable implementations to the object url instead
* possiblity to create dummy items for each url and containing the string in that object
‣ qubasic: this will be needing lot of more support from the backend will be needed and it will be much more complicated to do - would be more future compatible to be on the xesam
‣ nepomuk guy: internal stuff could create the internal representations in hackish way and just expose the data in graph way
‣ evgeny: proposing a far reaching goal to make it easy for users in mid term future to transition to this - maybe roadmat for applications to be able to produce more complex queries
‣ Urho: so, do you propose SPARQL?
‣ evgeny: nope - we should be able to extend current XML
‣ nepomuk guy: we could create related to inner queries
‣ mikkel: why not jus tallow the results of one query to be source for the next one
‣ urho: so inner queries - yeah
‣ evgeny: makes an example of the paper question in sparql
‣ evgeny: we are not looking for using sparql, just similar functionality
‣ evgeny: mapping sparql to sql can be done
‣ jos: I propose that we won't implement this to 1.0
* just make the ontology as future proof
* make a temporary solution and future path
‣ evgeny: list of use cases
* we have no way to query - semantic desktop guys will not be able to use xesam in the way they can use nepomuk
* maybe we could at least make a wrapper library?
‣ JOS: making the proposal
* usually we store the name of author in a field on document
* in graph we would store it on separate object
* so, propose that we do it like this now and if engine supports the denormalized model, it will do the conversion from the object to the name
* and we extend the ontology the denormalized way
* nepomuk guy: we have the proper ontology in nepomuk, we could just translate that to xesam
* qubasik: suggest that we make a small team to discuss this in real detail
* agreed: 1st item: FAIL -

Search API (d-bus api)
* Notes taking by urho
* latest changes for sorting and some session properties
* we simply list all the problems that people have with it
* inner queries agreed to be handled separately
* jamie raising issue of ranged search
* philip: why don't we remove the session completely - it's completely unused
* jos: i'll explain the session - it's for live queries
* you can have multiple searches per session
* search thus should have a separate id so that that can be closed, there is no need for the session at all
* kubasic:
* rob: you need to know what searches are running
* mikkel: if we create the session at the time of the start
* martyn: we need to have a separate id for searches
* rob: we have a separate id for searches
* can't we add the properties to the query itself?
* go for large and infrequent messages
* kubasik: we should decide whether to use the properties on the xml or on the dbus
* mikkel: properties can go on the search object instead (written)
* philip: I agree with sebastian (nepomuk guy) hit fields should be in the query
* philip: we can go instead for the session changes to be for the xesam 2.0 and not yet to the 1.0
* philip: if we change the query language, that'll break everything anyway
* rob: seems like you are using ids for the objects on the server side - perhaps they actually should be d-bus objects
* jos: so, current model is imperfect, but enough for 1.0
* jos: let's keep it like it is for now as it's works
* versioning discussion - should dbus have the version number in the dbus namespace?
* rob checks- yes you can
* kubasik: we need to have a bit of better way to decide which engine to use
* but we don't need to specify the way to do it
* philip: we should have announcement of capabilities to allow applications to choose the right engine with the right capabilities
* kubasik: distributions need to be taken into account here
* mikkel: we need to have the documentation about the capabilities and make the apis to discover
* mikkel: can be considered for 1.0 (at least guidelines)
* let's make a group to specify this
* jos: gethitdata will be capable of handling the ranges quite easily as it's capable
* urho: we have the case where hitsadded hit is on a sorted live query and on place on the visible resultset. without the id and uri of the hitadded, you will have to re-query your entire set
* kubasik: most of the time the issue is really that single item has been modified
* mikkel: so, we would emit: livehitsadded
* jos: live search never sends researchdone
* mikkel: yes it sends once the indexing is done
* mikkel: let's add livesearch added that would contain also the hit metadata
* jos: we need to minimize the changes needed
* everyone can live with even the paging
* jamie: so, no changes for 1.0 for hitsadded, but for 2.0 yes
* jos: idea for ranged search will mean that we supply the ids of the hits
* michael: d-bus api
* sometimes several search engines in parallel is an issue
* one engine refuses to start if d-bus api not available
* we should make search engines to que on d-bus
* no way to decide which engine is started
* mikkel: we have also xesam interface on tracker, so that can be used org.freedesktop.tracker.xesam?
* philip: we don't
* mikkel: perhpas that would be a recommendation
* urho: how about org.freedesktop.xesam.tracker and org.freedesktop.beagle
* mikkel: good idea
* michael raising issues about the specialist engines existing on the same system
* philip: wants to raise something
* this suggestion is unimplementable on sqlite as it is
* ottela: we get hits 1 - 1000 - we change the value of item 1 to be last on the list
* ottela: if one file changes - hitsmodified tells that one changed to 1000 and 2 changed to 1, 3 to 2,...
* jos: why don't we say the gethitsdata needs to be sequential
* philip: the issues with 1, 10000, 500 will mean the complexity of the corner cases will become very difficulta
* and this will make it quite complex to do properly on the server side
* <discussion that has been too hard to type on the report>
* urho: how about adding getrangedhits
* jos: if we don't remove the gethisdata that already exists
* agreed by everyone
* martyn: I'd rather have a new hitsmoved rather than having the hitsremoved and hitsadded
* jos: currently the positionshould not be changing?
* kubasik explains beagle issues
* martyn: sounds nice, but the issue is that the new api would make it more clear for the client applications to use
* kubasik: it's going to be difficult to implement the live queries
* martyn: surely we should add the possibility to handle the things without the need to re-create the live query
* sebastian: how about another working group?
* mikkel agreed:
* so, group to discuss the live sorting and hits added / moved issue
* kubasik: we'll have the group and I can tell how beagle is doing this
* mikkel: one for this and another group for the accessibility
* sebastian proposes to use floating points for the ordering
* ben raises the issue that how hard will it be possible to sort by the strings, the text
* Mikkel: live query sorting who is the group?
* Jos: I don't think live queries will be efficiently possible on the server side
* group: half and hour - jos, martyn, kubasik, mikael, mikkel (?)
* LUNCH

Ontology discussion:
Link by id - mikkel presenting on postits
* evgenys idea originally as a middle way between semantic graph and the current xesam
* problem is mainly linking relate objects (like linkin document and author) or document contained in an email
* referring e.g. two documents together with isbn
* there are multiple ids (not just uris)
* they will need to be 'sufficiently unique'
* Solving the problem
* xesam id field (any child of it must have a value that is unique over all xesam ids)
* all of the links must always be to ids
* we make a new special kind of field that is child of xesam:related or could be a special data type
* should always hold xesam id
* with this we can find all objects that point to X (or any that X points to)
* so, e.g. pdf file reference isbn - query xesam id field with that isbn
*
* sebastian: subqueries should be enough to allow good usage of this on the search api
* urho: agreed
* Everybody agrees to investigate the idea
* mikkel: suggest using a new field in xesam api id-field
* kubasik: we would need to do nested queries most probably and not probably an optimized index for this
* sebastian: normally you would say give me all emails htat have sender of contact object that has name like this
‣ now you could do it sender as a range, of person object, it would check all xesam id values in the relation
* mikkel: it shoud be very easy to do these queries
‣ and it should be very easy to show the values of these fields
* jos: we should do so that we do two fields: radable valua and pointer/relation property. Also, the more strong engines could say that the value is just an alias of the actual objects relations property
* sebastian: why not use the uri for data representation plugins that would then be able to create the visible widgets of the data items
* sebastian: i see that there are some issues with people wanting to not to do two queries
* evgeny: you would need inference for it and it's easier so that we make it so that xesam:strings: would contain the string representation of the url / link values.
* so, this way, we only use the string representation for only full text search.
* evgeny: I feel that we have a bit of problem on the specification of what should be in the FTI
* Anders: we need to also be able to show how/why the relation was created and to be able to do that for all the related content
* evgeny: we cannot have the stuff linking to everything on the database
* sebastian: we don't need to present on how a relation was found and it's a GUI thing
* jamie: two fields would be more clean
* jamie draws example below evgenys example
* jos agrees on the two field model
* evgeny isn't completely convinced
* the point is that the UI will likely match the actual contact
* jamie: this way the application would have the choice
* jamie: if we have just a name on the author text, then we don't want to try to create the dummy object
* evgeny: compromise solution in my opinion is that if we have to use have use the subqueries
* discussion on that we want a value of properties on a single query on xesam
* jamie: we could always deprecate the fields
* jos: i liked the suggestion of author text and author link and group the fields on a string text
* sebastian: why not make all dummy objects to have the same data layout
* at least the data is syntatically correct if we use dummy objects
* jamie: it's not worth it if we don't have the semantic info
* sebastian: this way we handle the data in same way for the 'proper' objects as well as the dummy ones
* <lots of discussion>
* Conclusion:
‣ We make some older strings as URIs instead of the previous string values
‣ All new URI properties also have a .label that allows to get the textual representation of the property, which in essence is the old xesam ontology value of the property. The ideal is that this is a pointer to a specific property of the linked object
‣ We will draft nested queries and they will most probably go to 1.1
*

Maemo Summit 2008

2008-09-20T05:45:41Z

84.22.107.1: /* Links */

[[image:C-logo_claim_blue.png‎|right]]
[[image:MaemoSummit091908.jpg‎ ]]

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after the OSiM World http://www.osimworld.com

'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration]''' - '''[http://maemo.org/news/events/maemo_summit-001/ Who is attending]'''

In Maemo Summit 2008 you will learn more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Schedule ==

The program is still open. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''The sessions and names are confirmed but the day/time they are scheduled might still change.'''
You will see partly what happens and happend at http://maemosummit.ext.c-base.org/index.php/Main_Page.

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+
=== Friday 19 ([http://internettabletblog.de/maemo-summit-friday.ics .ics])===
|-
| width="112" | '''9:00'''
| colspan="3" | '''Doors open'''
|-
| '''9:30'''
| colspan="3" | '''Welcome!''', by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''The outside view''', by [http://dailythemes.wordpress.com/ Jay Sullivan] ([http://www.mozilla.com/ Mozilla Corp.])
|-
| '''10:30'''
| colspan="3" | '''Maemo UI Vision''', by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
|-
| '''11:00'''
| colspan="3" | '''What Maemo users want''', by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk])
|-
| '''11:30'''
| colspan="3" | '''Summary: What can we get out of Fremantle''', by [http://maemo.org/profile/view/peterschneider.html Peter Schneider] (Head of Product Marketing, Maemo Software @ Nokia)
|-
| '''12:00'''
| colspan="3" | '''Break.'''
|-
| '''12:15'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''Maemo in police cars''': presentation of an embedded project based on N800's [[User:smancke|Sebastian Mancke]]
# '''Developing Multilingual Multimodal Applications in Maemo'''. A Mobile Medical Speech Translator & A Mobile Meeting Calendar by [[User:ntsourak|Nikos Tsourakis]]
# '''An activist’s wish list''': A location aware software suite to use in reporting, and forensic investigation of, human rights violations by [[User:TonyPercy|Tony Percy]]
# '''[http://liquid.googlepages.com/lcuk liqbase]''', by Gary Birkett ([http://maemo.org/profile/view/lcuk.html lcuk])
# '''Reality or Vision?''' - The Nokia tablets for mobile and desktop use. LiveDemo/Presentation with [http://xsisusb.garage.maemo.org/ USB2VGA Adapter], bluetooth [http://anyremote.sourceforge.net/ anyremote] control by [http://www.linuxvision.de/ Uwe Koch]. ([http://maemo.org/profile/view/asys3/ asys3]).
# '''Screencasting''': x11vnc and pyvnc2swf bring visual documentation to users by [[User:brontide|Eric Warnke]]
# '''[[Maemo User Interface Issues Overview (Presentation)|Maemo User Interface Issues Overview]]''', by [[User:Timsamoff |Tim Samoff]].
# '''[http://esbox.garage.maemo.org/ ESBox] and [http://pluthon.garage.maemo.org/ Pluthon] Eclipse plugins''': how to use Eclipse to develop Maemo applications, by [[User:andy80|Andrea Grandi]].
# '''[http://elisator.garage.maemo.org Elisator] project and how [http://easy.garage.maemo.org Easy] library has helped and how could be improved'''. Elisator has been developed for cow's milk analisys in poor Africa regions and it has been funded by [http://www.fao.org FAO]. (by [[user:jsmanrique|jsmanrique]])
# '''Teaser: maemo development using [http://illumination.sf.net Illumination]''' by [[User:framstag|Tim Teulings]].
# '''[http://dev.openbossa.org/trac/qedje/ QEdje]''', by [[user:etrunko|Eduardo Lima (Etrunko)]].
# '''Maemo Bug Jar: Origins, Results, and Future Plans''', by Stephen Gadsby ([http://maemo.org/profile/view/sjgadsby/ sjgadsby]).
# '''Unit/Integration Test Framework for Maemo''' by [[User:aheimola|Antti Heimola]].
# '''[http://www.internettablettalk.com/forums/showthread.php?t=21629 Debian in a chroot on the tablet]''', demo by Alan Bruce (qole).
# '''[http://codespeak.net/pypy PyPy] Python for Maemo''' (by [[user:hpk|Holger Krekel]] and/or [[user:fijal|Maciej Fijalkowski]]).
|-
| '''14:00'''
| colspan="3" | '''Lunch!''' [[image:MaemoSummit_catering.jpg‎ ]]
|-
| rowspan="3" | '''15:00'''
| colspan="3" | '''Meet the Maemo SW developers''' (a representation of the main platform and OSS teams developing Maemo @ Nokia + special guests)
|-
| width="33%" | '''STREAM 1: ROOM UPSTAIRS'''
| width="33%" | '''STREAM 2: ROOM DOWNSTAIRS'''
| width="33%" | '''STREAM 3: C-BASE'''
|-
| width="33%" | '''Desktop''' by [http://maemo.org/profile/view/rodarvus/ Rodrigo Novo] (Nokia) and Matthew Allum (OpenedHand)
| width="33%" | '''Connectivity''' by [http://maemo.org/profile/view/kvalo.html Kalle Valo] and [http://maemo.org/profile/view/pfl.html Patrik Flykt]
| width="33%" | '''Development Platform''' by [http://maemo.org/profile/view/bijjal/ Soumya Bijjal], [http://maemo.org/profile/view/kaltsi/ Juha Kallioinen] (tbc), [http://maemo.org/profile/view/marcell/ Marcell Lengyel], [http://maemo.org/profile/view/qgil.html Quim Gil]
|-
| '''16:00'''
| width="33%" | '''Browser''' by [http://maemo.org/profile/view/andreypetrov.html Andrey Petrov], [http://maemo.org/profile/view/timeless.html timeless]
| width="33%" | '''Real-Time Communication''' by [http://maemo.org/profile/view/kh_naba/ Naba Kumar], [http://maemo.org/profile/view/mzabaluev/ Mikhail Zabaluev]
| width="33%" | '''Technology & Architecture''' by [http://maemo.org/profile/view/jtukkine/ Juha Tukkinen], [http://maemo.org/profile/view/bittinen/ Mika Leppinen]
|-
| '''17:00'''
| width="33%" | '''Core System''' by Kai Svahn (tbc), [http://maemo.org/profile/view/nakkebar/ Eero Tamminen], [http://maemo.org/profile/view/igor_stoppa.html Igor Stoppa], [http://maemo.org/profile/view/poussa.html Sakari Poussa]
| width="33%" | '''Multimedia''' by [http://maemo.org/profile/view/ensonic.html Stefan Kost], [http://maemo.org/profile/view/luc/ Luc Pionchon]
| width="33%" | '''[[Desktop_Search_Hackfest|Desktop Search Hackfest]]''' link, by [http://maemo.org/profile/view/konttori/ Urho Konttori], [http://maemo.org/profile/view/ifrade/ Iván Frade] + Jamie McCracken (Tracker)
|-
| '''18:00'''
| colspan="3" | '''c-base reconstruction project³ - be future compatible- reboot universe now'''
*learn more about the crashed spacestation c-base
|-
| '''18:30'''
| colspan="3" | '''Chill out.'''
* Dinner, music, drinks tbd.
* Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)
: Now that the new logo has been chosen, what exactly does this mean? --[[User:timsamoff|timsamoff]] 12:24, 5 August 2008 (UTC)
:: Wear a t-shirt with a maemo.org logo that you like from the competition. The official one isn't allowed ;) --[[User:xfade|xfade]] 14:47, 5 August 2008 (UTC)
::: what if you liked the official one? --[[User:dneary|Dave Neary]] 22:14, 6 August 2008 (UTC)
|}

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+

===Saturday 20===

Coordinated by [[User:brontide| Eric Warnke]]

|-
| width="53" | '''9:00'''
| colspan="3" | '''Opening doors''' and wlan.
|-
| '''9:30'''
| colspan="3" | '''Open Source in Maemo: why and how''', by [http://flors.wordpress.com/ Quim Gil] (marketing manager, open source - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''Introducing the [[Task:Community Council|Maemo Community Council]]''', by [[Community_Council|the members]].
|-
| '''10:30'''
| colspan="3" | '''"We are not the Users": The hate and love behind the custom User experiences on Maemo.''' [[User:handful|Marcelo eduardo]]
|-
| width="53" | '''11:00'''
| colspan="3" | '''BoF: Future of maemo.org extras''', by Niels (and Ed?)
|-
| '''11:30'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''mCalendar and mContact''': advanced syncing with google services [[User:khertan|Benoît HERVIER]]
# '''Cloud storage:''' Improve you app by syncing with internet services like Google Docs or Picasaweb by [[User:brontide|Eric Warnke]]
# '''Tablet-encode''': Converting videos on Linux using [http://mediautils.garage.maemo.org/tablet-encode.html tablet-encode], by Andrew Flegg ([http://maemo.org/profile/view/jaffa/ Jaffa])
# '''py2deb''': packaging your app onboard using py2deb and extras autobuilder [[User:khertan|Benoît HERVIER]]
# '''WorldTV99''': Watching TV on your tablet by [[User:bunanson|bunanson]] and koos
# '''Podcasts on NITs''': [http://maemo.gpodder.org/ gPodder] and [http://thpinfo.com/2008/panucci/ Panucci] by ([http://maemo.org/profile/view/thp.html Thomas Perl])
# '''KDE on maemo''': by Marijn Kruisselbrink
|-
| '''12:05'''
| colspan="3" | '''Break'''
|-
| '''TRACKS'''
| width="33%" | '''Community/Discussion'''
| width="33%" | '''Development'''
| width="33%" | '''Core Platform'''
|-
| '''12:30'''
| width="33%" | '''Community story – Productivity suite in Nokia IT''', by Miika Kuha
| width="33%" | '''Packaging and publishing software'''
| width="33%" | '''[http://clutter-project.org/ Clutter]''', by [http://butterfeet.org/ Matthew Allum] ([http://o-hand.com/ OpenedHand])
|-
| '''13:00'''
| width="33%" | '''[http://dev.openbossa.org/trac/mamona Mamona] & Maemo: 2 way contribution (How to learn and grow up together)''', by Mamona developers from INdT.
| width="33%" | '''Porting Applications and exploiting the maemo platform''' lead by [[User:anidel|Aniello Del Sorbo]]
| width="33%" | '''maemo.org extras Package Cleanup Sprint'''
|-
| '''13:30'''
| width="33%" | '''[[Maemo User Interface Issues (Presentation)|Maemo User Interface Issues]]''', by [[User:Timsamoff |Tim Samoff]].
| width="33%" | '''Using [http://mud-builder.garage.maemo.org/ mud-builder] to build packages''', by [[User:Jaffa|Jaffa]].
| width="33%" | '''[http://blog.haerwu.biz/2008/08/01/nokia-n8x0-emulation-part-ii/ Maemo in QEMU N8x0 emulation:]''' by [[User:hrw|Marcin 'hrw' Juszkiewicz]]
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| '''15:00'''
| width="33%" rowspan="2" | '''Workshop: Maemo hacking introduction''': coordinated by [[User:kate |Kate Alhola]]
| width="33%" | '''Embedded Webapps''' Using webpy framework for on tablet web services by [[user:fpp]]
| width="33%" | '''maemo.org website redesign meeting''': A meeting to specify the design requirements for restyling the maemo.org website (reference: [[Task:Improving_maemo.org#maemo.org_homepage_refresh|Homepage Refresh]] & [[Task:Maemo.org_facelift|maemo.org Facelift]]). by [[User:xfade|Niels Breet]]
|-
| '''15:30'''
| width="33%" | '''Introduction To Telepathy:''' Components and use on the maemo platform. by Marco Barisione from [http://www.collabora.co.uk Collabora]
| width="33%" | '''Introduction to DSP programming''' by [[User:lardman|Simon Pickering]]
|-
| '''16:00'''
| width="33%" | '''Building a Business on Maemo:''' by [[User:dob|Doug Petkanics]] from [http://frogmetrics.com Frogmetrics]
| width="33%" | '''Qt Maemo-Hildon Port & How to Develop Qt Application for the Maemo Platform''', by [[User:kate |Kate Alhola]] & [[User:gnuton |Antonio Aloisio]].
| width="33%" | '''BoF: Building a vector data extension to maemo Mapper''' Soliciting feedback and developers for the project. by [[user:gnuite]]
|-
| '''16:30'''
| width="33%" | '''[[User:Andre/Presentations|Bugsquad meeting]]''' Anybody interested in helping managing the Maemo bugs is welcome! Hosted by [[User:Andre|Andre Klapper]] and [[User:Karstenb|Karsten Bräckelmann]]
| width="33%" | [[Google Data API for Python (Presentation)|'''Introduction to Google's python based Data API's''']] by [[User:Brontide|Eric Warnke]]
| width="33%" | '''Introduction to WebKit''' Come see WebKit's internals, 2 of its ports (Gtk and Qt). by [[User:pierlux |Pierre-Luc Beaudoin]] from [http://www.collabora.co.uk Collabora]
|-
| '''17:00'''
| colspan="3" | [[2010 Agenda|'''Maemo 2010''']]: Brainstorming session discussing current status / future desires for the Maemo platform. Where do we want to go in the next 24 months? What can we learn and share from other mobile platforms? Bring the whole community together to get input.
|-
| '''18:00'''
| colspan="3" | '''End.''' '''Note: Software Freedom Day (20th of September) [http://softwarefreedomday.org/teams/europe/germany/FreieSoftwareBerlin also in Berlin]'''
|}

== Venue ==

The Maemo Summit is held in the headquarter of '''[http://www.c-base.org c-base]''' and the contiguous [http://www.eti-berlin.de/ eti Schauspielschule Berlin].

c-base is a non-profit association which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]). eti Berlin is a school of actors based in a building with several rooms and a total surface available of 1.200m2. The perfect mix, full of creativity!

See [http://share.ovi.com/channel/qgil.public the videos].

c-base is in the very Mitte of Berlin. [http://maps.google.co.uk/maps?ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:unofficial&client=firefox-a&um=1&q=c-base&near=Berlin,+Germany&fb=1&cid=0,0,5828762841994571845&sa=X&oi=local_result&resnum=1&ct=image Map]

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER]'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
See [[Maemo_Summit_2008/Travel|when people are arriving in and leaving Berlin]].

[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxes from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
See [[Maemo Summit 2008/Accommodation]].

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Organization ==
See [[Maemo_Summit_2008/Organization]]. Volunteers needed!

== Streaming video ==
Since nearly all of the attendees are carrying internet-connected video cameras, it is possible that someone may find a way to stream live video of the event. ([https://bugs.maemo.org/show_bug.cgi?id=1889 Bug 1889] makes this harder, but it should still be possible...)

== Links ==

Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]
* [http://www.internettablettalk.com/forums/showthread.php?t=21569 Maemo summit discussion at Internet Tablet Talk]
* [http://lwn.net/Calendar/Monthly/2008-09/ LWN Calendar]

[[Events]]

Maemo Summit 2008

2008-09-20T05:45:21Z

84.22.107.1: /* Links */

[[image:C-logo_claim_blue.png‎|right]]
[[image:MaemoSummit091908.jpg‎ ]]

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after the OSiM World http://www.osimworld.com

'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration]''' - '''[http://maemo.org/news/events/maemo_summit-001/ Who is attending]'''

In Maemo Summit 2008 you will learn more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Schedule ==

The program is still open. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''The sessions and names are confirmed but the day/time they are scheduled might still change.'''
You will see partly what happens and happend at http://maemosummit.ext.c-base.org/index.php/Main_Page.

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+
=== Friday 19 ([http://internettabletblog.de/maemo-summit-friday.ics .ics])===
|-
| width="112" | '''9:00'''
| colspan="3" | '''Doors open'''
|-
| '''9:30'''
| colspan="3" | '''Welcome!''', by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''The outside view''', by [http://dailythemes.wordpress.com/ Jay Sullivan] ([http://www.mozilla.com/ Mozilla Corp.])
|-
| '''10:30'''
| colspan="3" | '''Maemo UI Vision''', by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
|-
| '''11:00'''
| colspan="3" | '''What Maemo users want''', by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk])
|-
| '''11:30'''
| colspan="3" | '''Summary: What can we get out of Fremantle''', by [http://maemo.org/profile/view/peterschneider.html Peter Schneider] (Head of Product Marketing, Maemo Software @ Nokia)
|-
| '''12:00'''
| colspan="3" | '''Break.'''
|-
| '''12:15'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''Maemo in police cars''': presentation of an embedded project based on N800's [[User:smancke|Sebastian Mancke]]
# '''Developing Multilingual Multimodal Applications in Maemo'''. A Mobile Medical Speech Translator & A Mobile Meeting Calendar by [[User:ntsourak|Nikos Tsourakis]]
# '''An activist’s wish list''': A location aware software suite to use in reporting, and forensic investigation of, human rights violations by [[User:TonyPercy|Tony Percy]]
# '''[http://liquid.googlepages.com/lcuk liqbase]''', by Gary Birkett ([http://maemo.org/profile/view/lcuk.html lcuk])
# '''Reality or Vision?''' - The Nokia tablets for mobile and desktop use. LiveDemo/Presentation with [http://xsisusb.garage.maemo.org/ USB2VGA Adapter], bluetooth [http://anyremote.sourceforge.net/ anyremote] control by [http://www.linuxvision.de/ Uwe Koch]. ([http://maemo.org/profile/view/asys3/ asys3]).
# '''Screencasting''': x11vnc and pyvnc2swf bring visual documentation to users by [[User:brontide|Eric Warnke]]
# '''[[Maemo User Interface Issues Overview (Presentation)|Maemo User Interface Issues Overview]]''', by [[User:Timsamoff |Tim Samoff]].
# '''[http://esbox.garage.maemo.org/ ESBox] and [http://pluthon.garage.maemo.org/ Pluthon] Eclipse plugins''': how to use Eclipse to develop Maemo applications, by [[User:andy80|Andrea Grandi]].
# '''[http://elisator.garage.maemo.org Elisator] project and how [http://easy.garage.maemo.org Easy] library has helped and how could be improved'''. Elisator has been developed for cow's milk analisys in poor Africa regions and it has been funded by [http://www.fao.org FAO]. (by [[user:jsmanrique|jsmanrique]])
# '''Teaser: maemo development using [http://illumination.sf.net Illumination]''' by [[User:framstag|Tim Teulings]].
# '''[http://dev.openbossa.org/trac/qedje/ QEdje]''', by [[user:etrunko|Eduardo Lima (Etrunko)]].
# '''Maemo Bug Jar: Origins, Results, and Future Plans''', by Stephen Gadsby ([http://maemo.org/profile/view/sjgadsby/ sjgadsby]).
# '''Unit/Integration Test Framework for Maemo''' by [[User:aheimola|Antti Heimola]].
# '''[http://www.internettablettalk.com/forums/showthread.php?t=21629 Debian in a chroot on the tablet]''', demo by Alan Bruce (qole).
# '''[http://codespeak.net/pypy PyPy] Python for Maemo''' (by [[user:hpk|Holger Krekel]] and/or [[user:fijal|Maciej Fijalkowski]]).
|-
| '''14:00'''
| colspan="3" | '''Lunch!''' [[image:MaemoSummit_catering.jpg‎ ]]
|-
| rowspan="3" | '''15:00'''
| colspan="3" | '''Meet the Maemo SW developers''' (a representation of the main platform and OSS teams developing Maemo @ Nokia + special guests)
|-
| width="33%" | '''STREAM 1: ROOM UPSTAIRS'''
| width="33%" | '''STREAM 2: ROOM DOWNSTAIRS'''
| width="33%" | '''STREAM 3: C-BASE'''
|-
| width="33%" | '''Desktop''' by [http://maemo.org/profile/view/rodarvus/ Rodrigo Novo] (Nokia) and Matthew Allum (OpenedHand)
| width="33%" | '''Connectivity''' by [http://maemo.org/profile/view/kvalo.html Kalle Valo] and [http://maemo.org/profile/view/pfl.html Patrik Flykt]
| width="33%" | '''Development Platform''' by [http://maemo.org/profile/view/bijjal/ Soumya Bijjal], [http://maemo.org/profile/view/kaltsi/ Juha Kallioinen] (tbc), [http://maemo.org/profile/view/marcell/ Marcell Lengyel], [http://maemo.org/profile/view/qgil.html Quim Gil]
|-
| '''16:00'''
| width="33%" | '''Browser''' by [http://maemo.org/profile/view/andreypetrov.html Andrey Petrov], [http://maemo.org/profile/view/timeless.html timeless]
| width="33%" | '''Real-Time Communication''' by [http://maemo.org/profile/view/kh_naba/ Naba Kumar], [http://maemo.org/profile/view/mzabaluev/ Mikhail Zabaluev]
| width="33%" | '''Technology & Architecture''' by [http://maemo.org/profile/view/jtukkine/ Juha Tukkinen], [http://maemo.org/profile/view/bittinen/ Mika Leppinen]
|-
| '''17:00'''
| width="33%" | '''Core System''' by Kai Svahn (tbc), [http://maemo.org/profile/view/nakkebar/ Eero Tamminen], [http://maemo.org/profile/view/igor_stoppa.html Igor Stoppa], [http://maemo.org/profile/view/poussa.html Sakari Poussa]
| width="33%" | '''Multimedia''' by [http://maemo.org/profile/view/ensonic.html Stefan Kost], [http://maemo.org/profile/view/luc/ Luc Pionchon]
| width="33%" | '''[[Desktop_Search_Hackfest|Desktop Search Hackfest]]''' link, by [http://maemo.org/profile/view/konttori/ Urho Konttori], [http://maemo.org/profile/view/ifrade/ Iván Frade] + Jamie McCracken (Tracker)
|-
| '''18:00'''
| colspan="3" | '''c-base reconstruction project³ - be future compatible- reboot universe now'''
*learn more about the crashed spacestation c-base
|-
| '''18:30'''
| colspan="3" | '''Chill out.'''
* Dinner, music, drinks tbd.
* Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)
: Now that the new logo has been chosen, what exactly does this mean? --[[User:timsamoff|timsamoff]] 12:24, 5 August 2008 (UTC)
:: Wear a t-shirt with a maemo.org logo that you like from the competition. The official one isn't allowed ;) --[[User:xfade|xfade]] 14:47, 5 August 2008 (UTC)
::: what if you liked the official one? --[[User:dneary|Dave Neary]] 22:14, 6 August 2008 (UTC)
|}

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+

===Saturday 20===

Coordinated by [[User:brontide| Eric Warnke]]

|-
| width="53" | '''9:00'''
| colspan="3" | '''Opening doors''' and wlan.
|-
| '''9:30'''
| colspan="3" | '''Open Source in Maemo: why and how''', by [http://flors.wordpress.com/ Quim Gil] (marketing manager, open source - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''Introducing the [[Task:Community Council|Maemo Community Council]]''', by [[Community_Council|the members]].
|-
| '''10:30'''
| colspan="3" | '''"We are not the Users": The hate and love behind the custom User experiences on Maemo.''' [[User:handful|Marcelo eduardo]]
|-
| width="53" | '''11:00'''
| colspan="3" | '''BoF: Future of maemo.org extras''', by Niels (and Ed?)
|-
| '''11:30'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''mCalendar and mContact''': advanced syncing with google services [[User:khertan|Benoît HERVIER]]
# '''Cloud storage:''' Improve you app by syncing with internet services like Google Docs or Picasaweb by [[User:brontide|Eric Warnke]]
# '''Tablet-encode''': Converting videos on Linux using [http://mediautils.garage.maemo.org/tablet-encode.html tablet-encode], by Andrew Flegg ([http://maemo.org/profile/view/jaffa/ Jaffa])
# '''py2deb''': packaging your app onboard using py2deb and extras autobuilder [[User:khertan|Benoît HERVIER]]
# '''WorldTV99''': Watching TV on your tablet by [[User:bunanson|bunanson]] and koos
# '''Podcasts on NITs''': [http://maemo.gpodder.org/ gPodder] and [http://thpinfo.com/2008/panucci/ Panucci] by ([http://maemo.org/profile/view/thp.html Thomas Perl])
# '''KDE on maemo''': by Marijn Kruisselbrink
|-
| '''12:05'''
| colspan="3" | '''Break'''
|-
| '''TRACKS'''
| width="33%" | '''Community/Discussion'''
| width="33%" | '''Development'''
| width="33%" | '''Core Platform'''
|-
| '''12:30'''
| width="33%" | '''Community story – Productivity suite in Nokia IT''', by Miika Kuha
| width="33%" | '''Packaging and publishing software'''
| width="33%" | '''[http://clutter-project.org/ Clutter]''', by [http://butterfeet.org/ Matthew Allum] ([http://o-hand.com/ OpenedHand])
|-
| '''13:00'''
| width="33%" | '''[http://dev.openbossa.org/trac/mamona Mamona] & Maemo: 2 way contribution (How to learn and grow up together)''', by Mamona developers from INdT.
| width="33%" | '''Porting Applications and exploiting the maemo platform''' lead by [[User:anidel|Aniello Del Sorbo]]
| width="33%" | '''maemo.org extras Package Cleanup Sprint'''
|-
| '''13:30'''
| width="33%" | '''[[Maemo User Interface Issues (Presentation)|Maemo User Interface Issues]]''', by [[User:Timsamoff |Tim Samoff]].
| width="33%" | '''Using [http://mud-builder.garage.maemo.org/ mud-builder] to build packages''', by [[User:Jaffa|Jaffa]].
| width="33%" | '''[http://blog.haerwu.biz/2008/08/01/nokia-n8x0-emulation-part-ii/ Maemo in QEMU N8x0 emulation:]''' by [[User:hrw|Marcin 'hrw' Juszkiewicz]]
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| '''15:00'''
| width="33%" rowspan="2" | '''Workshop: Maemo hacking introduction''': coordinated by [[User:kate |Kate Alhola]]
| width="33%" | '''Embedded Webapps''' Using webpy framework for on tablet web services by [[user:fpp]]
| width="33%" | '''maemo.org website redesign meeting''': A meeting to specify the design requirements for restyling the maemo.org website (reference: [[Task:Improving_maemo.org#maemo.org_homepage_refresh|Homepage Refresh]] & [[Task:Maemo.org_facelift|maemo.org Facelift]]). by [[User:xfade|Niels Breet]]
|-
| '''15:30'''
| width="33%" | '''Introduction To Telepathy:''' Components and use on the maemo platform. by Marco Barisione from [http://www.collabora.co.uk Collabora]
| width="33%" | '''Introduction to DSP programming''' by [[User:lardman|Simon Pickering]]
|-
| '''16:00'''
| width="33%" | '''Building a Business on Maemo:''' by [[User:dob|Doug Petkanics]] from [http://frogmetrics.com Frogmetrics]
| width="33%" | '''Qt Maemo-Hildon Port & How to Develop Qt Application for the Maemo Platform''', by [[User:kate |Kate Alhola]] & [[User:gnuton |Antonio Aloisio]].
| width="33%" | '''BoF: Building a vector data extension to maemo Mapper''' Soliciting feedback and developers for the project. by [[user:gnuite]]
|-
| '''16:30'''
| width="33%" | '''[[User:Andre/Presentations|Bugsquad meeting]]''' Anybody interested in helping managing the Maemo bugs is welcome! Hosted by [[User:Andre|Andre Klapper]] and [[User:Karstenb|Karsten Bräckelmann]]
| width="33%" | [[Google Data API for Python (Presentation)|'''Introduction to Google's python based Data API's''']] by [[User:Brontide|Eric Warnke]]
| width="33%" | '''Introduction to WebKit''' Come see WebKit's internals, 2 of its ports (Gtk and Qt). by [[User:pierlux |Pierre-Luc Beaudoin]] from [http://www.collabora.co.uk Collabora]
|-
| '''17:00'''
| colspan="3" | [[2010 Agenda|'''Maemo 2010''']]: Brainstorming session discussing current status / future desires for the Maemo platform. Where do we want to go in the next 24 months? What can we learn and share from other mobile platforms? Bring the whole community together to get input.
|-
| '''18:00'''
| colspan="3" | '''End.''' '''Note: Software Freedom Day (20th of September) [http://softwarefreedomday.org/teams/europe/germany/FreieSoftwareBerlin also in Berlin]'''
|}

== Venue ==

The Maemo Summit is held in the headquarter of '''[http://www.c-base.org c-base]''' and the contiguous [http://www.eti-berlin.de/ eti Schauspielschule Berlin].

c-base is a non-profit association which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]). eti Berlin is a school of actors based in a building with several rooms and a total surface available of 1.200m2. The perfect mix, full of creativity!

See [http://share.ovi.com/channel/qgil.public the videos].

c-base is in the very Mitte of Berlin. [http://maps.google.co.uk/maps?ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:unofficial&client=firefox-a&um=1&q=c-base&near=Berlin,+Germany&fb=1&cid=0,0,5828762841994571845&sa=X&oi=local_result&resnum=1&ct=image Map]

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER]'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
See [[Maemo_Summit_2008/Travel|when people are arriving in and leaving Berlin]].

[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxes from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
See [[Maemo Summit 2008/Accommodation]].

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Organization ==
See [[Maemo_Summit_2008/Organization]]. Volunteers needed!

== Streaming video ==
Since nearly all of the attendees are carrying internet-connected video cameras, it is possible that someone may find a way to stream live video of the event. ([https://bugs.maemo.org/show_bug.cgi?id=1889 Bug 1889] makes this harder, but it should still be possible...)

== Links ==
mjmgjhjg
Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]
* [http://www.internettablettalk.com/forums/showthread.php?t=21569 Maemo summit discussion at Internet Tablet Talk]
* [http://lwn.net/Calendar/Monthly/2008-09/ LWN Calendar]

[[Events]]

Maemo Summit 2008 recordings

2008-09-19T00:48:03Z

84.22.107.1:

data should be collected at http://maemosummit.ext.c-base.org

Maemo Summit 2008

2008-09-11T21:34:18Z

84.22.107.1: /* Friday 19 */

[[image:C-logo_claim_blue.png‎|right]]

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after the OSiM World http://www.osimworld.com

'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration]''' - '''[http://maemo.org/news/events/maemo_summit-001/ Who is attending]'''

In Maemo Summit 2008 you will learn more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Schedule ==

The program is still open. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''The sessions and names are confirmed but the day/time they are scheduled might still change.'''

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+
=== Friday 19 ===
|-
| width="112" | '''9:00'''
| colspan="3" | '''Opening doors'''
|-
| '''9:30'''
| colspan="3" | '''Welcome!''', by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''The outside view''', by [http://dailythemes.wordpress.com/ Jay Sullivan] ([http://www.mozilla.com/ Mozilla Corp.])
|-
| '''10:30'''
| colspan="3" | '''Hildon UI Vision''', by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
|-
| '''11:00'''
| colspan="3" | '''What Maemo users want''', by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk]) and [http://www.neoncherry.com/ Krisse] ([http://tabletschool.blogspot.com/ Internet Tablet School])
|-
| '''11:30'''
| colspan="3" | '''Summary: What can we get out of Fremantle''', by [http://maemo.org/profile/view/peterschneider.html Peter Schneider] (Head of Product Marketing, Maemo Software @ Nokia)
|-
| '''12:00'''
| colspan="3" | '''Break.'''
|-
| '''12:15'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''Maemo in police cars''': presentation of an embedded project based on N800's [[User:smancke|Sebastian Mancke]]
# Developing Multilingual Multimodal Applications in Maemo. A Mobile Medical Speech Translator & A Mobile Meeting Calendar by [[User:ntsourak|Nikos Tsourakis]]
# An activist’s wish list: A location aware software suite to use in reporting, and forensic investigation of, human rights violations by [[User:TonyPercy|Tony Percy]]
# [http://liquid.googlepages.com/lcuk liqbase], by Gary Birkett ([http://maemo.org/profile/view/lcuk.html lcuk])
# Yannick Pellet (Nokia)
# Reality or Vision? - The Nokia tablets for mobile and desktop use. LiveDemo/Presentation with [http://xsisusb.garage.maemo.org/ USB2VGA Adapter], bluetooth [http://anyremote.sourceforge.net/ anyremote] control by [http://www.linuxvision.de/ Uwe Koch]. ([http://maemo.org/profile/view/asys3/ asys3]).
# '''Screencasting''': x11vnc and pyvnc2swf bring visual documentation to users by [[User:brontide|Eric Warnke]]
# [[Maemo User Interface Issues Overview (Presentation)|Maemo User Interface Issues Overview]], by [[User:Timsamoff |Tim Samoff]].
# [http://esbox.garage.maemo.org/ ESBox] and [http://pluthon.garage.maemo.org/ Pluthon] '''Eclipse''' plugins: how to use Eclipse to develop Maemo applications, bye [[User:andy80|Andrea Grandi]].
# [http://elisator.garage.maemo.org Elisator] project and how [http://easy.garage.maemo.org Easy] library has helped and how could be improved. Elisator has been developed for cow's milk analisys in poor Africa regions and it has been funded by [http://www.fao.org FAO]. (by [[user:jsmanrique|jsmanrique]])
# Teaser: maemo development using [http://illumination.sf.net Illumination] by [[User:framstag|Tim Teulings]].
# [http://dev.openbossa.org/trac/qedje/ QEdje], by [[user:etrunko|Eduardo Lima (Etrunko)]].
# Maemo Bug Jar: Origins, Results, and Future Plans, by Stephen Gadsby ([http://maemo.org/profile/view/sjgadsby/ sjgadsby]).
# '''STIX''': Maemo Open Source test framework for Unit/Integration testing by Antti Heimola (Nokia)
# [http://www.internettablettalk.com/forums/showthread.php?t=21629 Debian in a chroot on the tablet], demo by Alan Bruce (qole).
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| rowspan="2" | '''15:00'''
| colspan="3" | '''Meet the Maemo SW developers''' (a representation of the main platform and OSS teams developing Maemo @ Nokia + special guests)
|-
| width="33%" | '''Desktop''' by [http://maemo.org/profile/view/rodarvus/ Rodrigo Novo] (Nokia) and Matthew Allum (OpenedHand)
| width="33%" | '''Connectivity''' by [http://maemo.org/profile/view/kvalo.html Kalle Valo] and [http://maemo.org/profile/view/pfl.html Patrik Flykt]
| width="33%" | '''Development Platform''' by [http://maemo.org/profile/view/bijjal/ Soumya Bijjal], [http://maemo.org/profile/view/kaltsi/ Juha Kallioinen] (tbc), [http://maemo.org/profile/view/marcell/ Marcell Lengyel], [http://maemo.org/profile/view/qgil.html Quim Gil]
|-
| '''16:00'''
| width="33%" | '''Browser''' by [http://maemo.org/profile/view/andreypetrov.html Andrey Petrov], [http://maemo.org/profile/view/timeless.html timeless]
| width="33%" | '''Real-Time Communication''' by [http://maemo.org/profile/view/kh_naba/ Naba Kumar] (tbc), [http://maemo.org/profile/view/mzabaluev/ Mikhail Zabaluev] (tbc)
| width="33%" | '''Technology & Architecture''' by [http://maemo.org/profile/view/jtukkine/ Juha Tukkinen], [http://maemo.org/profile/view/bittinen/ Mika Leppinen]
|-
| '''17:00'''
| width="33%" | '''Core System''' by Kai Svahn (tbc), [http://maemo.org/profile/view/nakkebar/ Eero Tamminen], [http://maemo.org/profile/view/igor_stoppa.html Igor Stoppa], [http://maemo.org/profile/view/poussa.html Sakari Poussa]
| width="33%" | '''Multimedia''' by [http://maemo.org/profile/view/ensonic.html Stefan Kost], [http://maemo.org/profile/view/luc/ Luc Pionchon]
| width="33%" | '''[[Desktop_Search_Hackfest|Desktop Search Hackfest]]''' link, by [http://maemo.org/profile/view/konttori/ Urho Konttori], [http://maemo.org/profile/view/ifrade/ Iván Frade] + Jamie McCracken (Tracker)
|-
| '''18:00'''
| colspan="3" | '''c-base reconstruction project³ - be future compatible- reboot universe now'''
*learn more about the crashed spacestation c-base
|-
| '''18:30'''
| colspan="3" | '''Chill out.'''
* Dinner, music, drinks tbd.
* Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)
: Now that the new logo has been chosen, what exactly does this mean? --[[User:timsamoff|timsamoff]] 12:24, 5 August 2008 (UTC)
:: Wear a t-shirt with a maemo.org logo that you like from the competition. The official one isn't allowed ;) --[[User:xfade|xfade]] 14:47, 5 August 2008 (UTC)
::: what if you liked the official one? --[[User:dneary|Dave Neary]] 22:14, 6 August 2008 (UTC)
|}

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+

===Saturday 20===

Coordinated by [[User:brontide| Eric Warnke]]

|-
| width="53" | '''9:00'''
| colspan="3" | '''Opening doors''' and wlan.
|-
| '''9:30'''
| colspan="3" | '''Open Source in Maemo: why and how''', by [http://flors.wordpress.com/ Quim Gil] (marketing manager, open source - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''Introducing the [[Task:Community Council|Maemo Community Council]]''', by [[Community_Council|the members]].
|-
| '''10:30'''
| colspan="3" | '''"We are not the Users": The hate and love behind the custom User experiences on Maemo.''' [[User:handful|Marcelo eduardo]]
|-
| width="53" | '''11:00'''
| colspan="3" | '''BoF: Future of maemo.org extras''', by Niels (and Ed?)
|-
| '''11:30'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''mCalendar and mContact''': advanced syncing with google services [[User:khertan|Benoît HERVIER]]
# Cloud storage: Improve you app by syncing with internet services like Google Docs or Picasaweb by [[User:brontide|Eric Warnke]]
# Converting videos on Linux using [http://mediautils.garage.maemo.org/tablet-encode.html tablet-encode], by Andrew Flegg ([http://maemo.org/profile/view/jaffa/ Jaffa])
# '''py2deb''': packaging your app onboard using py2deb and extras autobuilder [[User:khertan|Benoît HERVIER]]
# '''WorldTV99''': Watching TV on your tablet by [[User:bunanson|bunanson]] and koos
# Podcasts on NITs with [http://maemo.gpodder.org/ gPodder] and [http://thpinfo.com/2008/panucci/ Panucci] by ([http://maemo.org/profile/view/thp.html Thomas Perl])
|-
| '''12:00'''
| colspan="3" | '''Break'''
|-
| '''TRACKS'''
| width="33%" | '''Community/Discussion'''
| width="33%" | '''Development'''
| width="33%" | '''Core Platform'''
|-
| '''12:30'''
| width="33%" | '''Nokia & Productivity Tools''', by Miika Kuha
| width="33%" | '''Packaging and publishing software'''
| width="33%" | '''[http://clutter-project.org/ Clutter]''', by [http://butterfeet.org/ Matthew Allum] ([http://o-hand.com/ OpenedHand])
|-
| '''13:00'''
| width="33%" | '''[http://dev.openbossa.org/trac/mamona Mamona] & Maemo: 2 way contribution (How to learn and grow up together)''', by Mamona developers from INdT.
| width="33%" | '''Porting Applications and exploiting the maemo platform''' lead by [[User:anidel|Aniello Del Sorbo]]
| width="33%" | '''maemo.org extras Package Cleanup Sprint'''
|-
| '''13:30'''
| width="33%" | '''[[Maemo User Interface Issues (Presentation)|Maemo User Interface Issues]]''', by [[User:Timsamoff |Tim Samoff]].
| width="33%" | '''Using [http://mud-builder.garage.maemo.org/ mud-builder] to build packages''', by [[User:Jaffa|Jaffa]].
| width="33%" | '''[http://blog.haerwu.biz/2008/08/01/nokia-n8x0-emulation-part-ii/ Maemo in QEMU N8x0 emulation:]''' by [[User:hrw|Marcin 'hrw' Juszkiewicz]]
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| '''15:00'''
| width="33%" rowspan="2" | '''Workshop: Maemo hacking introduction''': coordinated by [[User:kate |Kate Alhola]]
| width="33%" | '''Embedded Webapps''' Using webpy framework for on tablet web services by [[user:fpp]]
| width="33%" | '''maemo.org website redesign meeting''': A meeting to specify the design requirements for restyling the maemo.org website (reference: [[Task:Improving_maemo.org#maemo.org_homepage_refresh|Homepage Refresh]] & [[Task:Maemo.org_facelift|maemo.org Facelift]]). by [[User:xfade|Niels Breet]]
|-
| '''15:30'''
| width="33%" | '''Introduction To Telepathy:''' Components and use on the maemo platform. by Marco Barisione from [http://www.collabora.co.uk Collabora]
| width="33%" | '''Introduction to DSP programming''' by [[User:lardman|Simon Pickering]]
|-
| '''16:00'''
| width="33%" | '''Building a Business on Maemo:''' by [[User:dob|Doug Petkanics]] from [http://frogmetrics.com Frogmetrics]
| width="33%" | '''Qt Maemo-Hildon Port & How to Develop Qt Application for the Maemo Platform''', by [[User:kate |Kate Alhola]] & [[User:gnuton |Antonio Aloisio]].
| width="33%" | '''BoF: Building a vector data extension to maemo Mapper''' Soliciting feedback and developers for the project. by [[user:gnuite]]
|-
| '''16:30'''
| width="33%" | '''[[User:Andre/Presentations|Bugsquad meeting]]''' Anybody interested in helping managing the Maemo bugs is welcome! Hosted by [[User:Andre|Andre Klapper]] and [[User:Karstenb|Karsten Bräckelmann]]
| width="33%" | [[Google Data API for Python (Presentation)|'''Introduction to Google's python based Data API's''']] by [[User:Brontide|Eric Warnke]]
| width="33%" | '''Introduction to WebKit''' Come see WebKit's internals, 2 of its ports (Gtk and Qt). by [[User:pierlux |Pierre-Luc Beaudoin]] from [http://www.collabora.co.uk Collabora]
|-
| '''17:00'''
| colspan="3" | [[2010 Agenda|'''Maemo 2010''']]: Brainstorming session discussing current status / future desires for the Maemo platform. Where do we want to go in the next 24 months? What can we learn and share from other mobile platforms? Bring the whole community together to get input.
|-
| '''18:00'''
| colspan="3" | '''End.'''
|}

== Venue ==

The Maemo Summit is held in the headquarter of '''[http://www.c-base.org c-base]''' and the contiguous [http://www.eti-berlin.de/ eti Schauspielschule Berlin].

c-base is a non-profit association which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]). eti Berlin is a school of actors based in a building with several rooms and a total surface available of 1.200m2. The perfect mix, full of creativity!

See [http://share.ovi.com/channel/qgil.public the videos].

c-base is in the very Mitte of Berlin. [http://maps.google.co.uk/maps?ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:unofficial&client=firefox-a&um=1&q=c-base&near=Berlin,+Germany&fb=1&cid=0,0,5828762841994571845&sa=X&oi=local_result&resnum=1&ct=image Map]

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER]'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
See [[Maemo_Summit_2008/Travel|when people are arriving in and leaving Berlin]].

[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxes from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
See [[Maemo Summit 2008/Accommodation]].

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Organization ==
See [[Maemo_Summit_2008/Organization]]. Volunteers needed!

== Links ==

Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]
* [http://www.internettablettalk.com/forums/showthread.php?t=21569 Maemo summit discussion at Internet Tablet Talk]
* [http://lwn.net/Calendar/Monthly/2008-09/ LWN Calendar]

[[Events]]

Maemo Summit 2008

2008-09-11T21:33:00Z

84.22.107.1: c-base reconstruction project³

[[image:C-logo_claim_blue.png‎|right]]

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after the OSiM World http://www.osimworld.com

'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration]''' - '''[http://maemo.org/news/events/maemo_summit-001/ Who is attending]'''

In Maemo Summit 2008 you will learn more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Schedule ==

The program is still open. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''The sessions and names are confirmed but the day/time they are scheduled might still change.'''

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+
=== Friday 19 ===
|-
| width="112" | '''9:00'''
| colspan="3" | '''Opening doors'''
|-
| '''9:30'''
| colspan="3" | '''Welcome!''', by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''The outside view''', by [http://dailythemes.wordpress.com/ Jay Sullivan] ([http://www.mozilla.com/ Mozilla Corp.])
|-
| '''10:30'''
| colspan="3" | '''Hildon UI Vision''', by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
|-
| '''11:00'''
| colspan="3" | '''What Maemo users want''', by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk]) and [http://www.neoncherry.com/ Krisse] ([http://tabletschool.blogspot.com/ Internet Tablet School])
|-
| '''11:30'''
| colspan="3" | '''Summary: What can we get out of Fremantle''', by [http://maemo.org/profile/view/peterschneider.html Peter Schneider] (Head of Product Marketing, Maemo Software @ Nokia)
|-
| '''12:00'''
| colspan="3" | '''Break.'''
|-
| '''12:15'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''Maemo in police cars''': presentation of an embedded project based on N800's [[User:smancke|Sebastian Mancke]]
# Developing Multilingual Multimodal Applications in Maemo. A Mobile Medical Speech Translator & A Mobile Meeting Calendar by [[User:ntsourak|Nikos Tsourakis]]
# An activist’s wish list: A location aware software suite to use in reporting, and forensic investigation of, human rights violations by [[User:TonyPercy|Tony Percy]]
# [http://liquid.googlepages.com/lcuk liqbase], by Gary Birkett ([http://maemo.org/profile/view/lcuk.html lcuk])
# Yannick Pellet (Nokia)
# Reality or Vision? - The Nokia tablets for mobile and desktop use. LiveDemo/Presentation with [http://xsisusb.garage.maemo.org/ USB2VGA Adapter], bluetooth [http://anyremote.sourceforge.net/ anyremote] control by [http://www.linuxvision.de/ Uwe Koch]. ([http://maemo.org/profile/view/asys3/ asys3]).
# '''Screencasting''': x11vnc and pyvnc2swf bring visual documentation to users by [[User:brontide|Eric Warnke]]
# [[Maemo User Interface Issues Overview (Presentation)|Maemo User Interface Issues Overview]], by [[User:Timsamoff |Tim Samoff]].
# [http://esbox.garage.maemo.org/ ESBox] and [http://pluthon.garage.maemo.org/ Pluthon] '''Eclipse''' plugins: how to use Eclipse to develop Maemo applications, bye [[User:andy80|Andrea Grandi]].
# [http://elisator.garage.maemo.org Elisator] project and how [http://easy.garage.maemo.org Easy] library has helped and how could be improved. Elisator has been developed for cow's milk analisys in poor Africa regions and it has been funded by [http://www.fao.org FAO]. (by [[user:jsmanrique|jsmanrique]])
# Teaser: maemo development using [http://illumination.sf.net Illumination] by [[User:framstag|Tim Teulings]].
# [http://dev.openbossa.org/trac/qedje/ QEdje], by [[user:etrunko|Eduardo Lima (Etrunko)]].
# Maemo Bug Jar: Origins, Results, and Future Plans, by Stephen Gadsby ([http://maemo.org/profile/view/sjgadsby/ sjgadsby]).
# '''STIX''': Maemo Open Source test framework for Unit/Integration testing by Antti Heimola (Nokia)
# [http://www.internettablettalk.com/forums/showthread.php?t=21629 Debian in a chroot on the tablet], demo by Alan Bruce (qole).
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| rowspan="2" | '''15:00'''
| colspan="3" | '''Meet the Maemo SW developers''' (a representation of the main platform and OSS teams developing Maemo @ Nokia + special guests)
|-
| width="33%" | '''Desktop''' by [http://maemo.org/profile/view/rodarvus/ Rodrigo Novo] (Nokia) and Matthew Allum (OpenedHand)
| width="33%" | '''Connectivity''' by [http://maemo.org/profile/view/kvalo.html Kalle Valo] and [http://maemo.org/profile/view/pfl.html Patrik Flykt]
| width="33%" | '''Development Platform''' by [http://maemo.org/profile/view/bijjal/ Soumya Bijjal], [http://maemo.org/profile/view/kaltsi/ Juha Kallioinen] (tbc), [http://maemo.org/profile/view/marcell/ Marcell Lengyel], [http://maemo.org/profile/view/qgil.html Quim Gil]
|-
| '''16:00'''
| width="33%" | '''Browser''' by [http://maemo.org/profile/view/andreypetrov.html Andrey Petrov], [http://maemo.org/profile/view/timeless.html timeless]
| width="33%" | '''Real-Time Communication''' by [http://maemo.org/profile/view/kh_naba/ Naba Kumar] (tbc), [http://maemo.org/profile/view/mzabaluev/ Mikhail Zabaluev] (tbc)
| width="33%" | '''Technology & Architecture''' by [http://maemo.org/profile/view/jtukkine/ Juha Tukkinen], [http://maemo.org/profile/view/bittinen/ Mika Leppinen]
|-
| '''17:00'''
| width="33%" | '''Core System''' by Kai Svahn (tbc), [http://maemo.org/profile/view/nakkebar/ Eero Tamminen], [http://maemo.org/profile/view/igor_stoppa.html Igor Stoppa], [http://maemo.org/profile/view/poussa.html Sakari Poussa]
| width="33%" | '''Multimedia''' by [http://maemo.org/profile/view/ensonic.html Stefan Kost], [http://maemo.org/profile/view/luc/ Luc Pionchon]
| width="33%" | '''[[Desktop_Search_Hackfest|Desktop Search Hackfest]]''' link, by [http://maemo.org/profile/view/konttori/ Urho Konttori], [http://maemo.org/profile/view/ifrade/ Iván Frade] + Jamie McCracken (Tracker)
|-
| '''18:30'''
| colspan="3" | '''c-base reconstruction project³ - be future compatible- reboot universe now'''
*learn more about the crashed spacestation c-base
|-
| '''18:30'''
| colspan="3" | '''Chill out.'''
* Dinner, music, drinks tbd.
* Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)
: Now that the new logo has been chosen, what exactly does this mean? --[[User:timsamoff|timsamoff]] 12:24, 5 August 2008 (UTC)
:: Wear a t-shirt with a maemo.org logo that you like from the competition. The official one isn't allowed ;) --[[User:xfade|xfade]] 14:47, 5 August 2008 (UTC)
::: what if you liked the official one? --[[User:dneary|Dave Neary]] 22:14, 6 August 2008 (UTC)
|}

{| width="100%" border="1" cellpadding="5" cellspacing="0" bordercolor="#000000"
|+

===Saturday 20===

Coordinated by [[User:brontide| Eric Warnke]]

|-
| width="53" | '''9:00'''
| colspan="3" | '''Opening doors''' and wlan.
|-
| '''9:30'''
| colspan="3" | '''Open Source in Maemo: why and how''', by [http://flors.wordpress.com/ Quim Gil] (marketing manager, open source - Maemo Software @ Nokia)
|-
| '''10:00'''
| colspan="3" | '''Introducing the [[Task:Community Council|Maemo Community Council]]''', by [[Community_Council|the members]].
|-
| '''10:30'''
| colspan="3" | '''"We are not the Users": The hate and love behind the custom User experiences on Maemo.''' [[User:handful|Marcelo eduardo]]
|-
| width="53" | '''11:00'''
| colspan="3" | '''BoF: Future of maemo.org extras''', by Niels (and Ed?)
|-
| '''11:30'''
| colspan="3" | '''Lightning sessions''', 5 min each. No more, no less.
# '''mCalendar and mContact''': advanced syncing with google services [[User:khertan|Benoît HERVIER]]
# Cloud storage: Improve you app by syncing with internet services like Google Docs or Picasaweb by [[User:brontide|Eric Warnke]]
# Converting videos on Linux using [http://mediautils.garage.maemo.org/tablet-encode.html tablet-encode], by Andrew Flegg ([http://maemo.org/profile/view/jaffa/ Jaffa])
# '''py2deb''': packaging your app onboard using py2deb and extras autobuilder [[User:khertan|Benoît HERVIER]]
# '''WorldTV99''': Watching TV on your tablet by [[User:bunanson|bunanson]] and koos
# Podcasts on NITs with [http://maemo.gpodder.org/ gPodder] and [http://thpinfo.com/2008/panucci/ Panucci] by ([http://maemo.org/profile/view/thp.html Thomas Perl])
|-
| '''12:00'''
| colspan="3" | '''Break'''
|-
| '''TRACKS'''
| width="33%" | '''Community/Discussion'''
| width="33%" | '''Development'''
| width="33%" | '''Core Platform'''
|-
| '''12:30'''
| width="33%" | '''Nokia & Productivity Tools''', by Miika Kuha
| width="33%" | '''Packaging and publishing software'''
| width="33%" | '''[http://clutter-project.org/ Clutter]''', by [http://butterfeet.org/ Matthew Allum] ([http://o-hand.com/ OpenedHand])
|-
| '''13:00'''
| width="33%" | '''[http://dev.openbossa.org/trac/mamona Mamona] & Maemo: 2 way contribution (How to learn and grow up together)''', by Mamona developers from INdT.
| width="33%" | '''Porting Applications and exploiting the maemo platform''' lead by [[User:anidel|Aniello Del Sorbo]]
| width="33%" | '''maemo.org extras Package Cleanup Sprint'''
|-
| '''13:30'''
| width="33%" | '''[[Maemo User Interface Issues (Presentation)|Maemo User Interface Issues]]''', by [[User:Timsamoff |Tim Samoff]].
| width="33%" | '''Using [http://mud-builder.garage.maemo.org/ mud-builder] to build packages''', by [[User:Jaffa|Jaffa]].
| width="33%" | '''[http://blog.haerwu.biz/2008/08/01/nokia-n8x0-emulation-part-ii/ Maemo in QEMU N8x0 emulation:]''' by [[User:hrw|Marcin 'hrw' Juszkiewicz]]
|-
| '''14:00'''
| colspan="3" | '''Lunch!'''
|-
| '''15:00'''
| width="33%" rowspan="2" | '''Workshop: Maemo hacking introduction''': coordinated by [[User:kate |Kate Alhola]]
| width="33%" | '''Embedded Webapps''' Using webpy framework for on tablet web services by [[user:fpp]]
| width="33%" | '''maemo.org website redesign meeting''': A meeting to specify the design requirements for restyling the maemo.org website (reference: [[Task:Improving_maemo.org#maemo.org_homepage_refresh|Homepage Refresh]] & [[Task:Maemo.org_facelift|maemo.org Facelift]]). by [[User:xfade|Niels Breet]]
|-
| '''15:30'''
| width="33%" | '''Introduction To Telepathy:''' Components and use on the maemo platform. by Marco Barisione from [http://www.collabora.co.uk Collabora]
| width="33%" | '''Introduction to DSP programming''' by [[User:lardman|Simon Pickering]]
|-
| '''16:00'''
| width="33%" | '''Building a Business on Maemo:''' by [[User:dob|Doug Petkanics]] from [http://frogmetrics.com Frogmetrics]
| width="33%" | '''Qt Maemo-Hildon Port & How to Develop Qt Application for the Maemo Platform''', by [[User:kate |Kate Alhola]] & [[User:gnuton |Antonio Aloisio]].
| width="33%" | '''BoF: Building a vector data extension to maemo Mapper''' Soliciting feedback and developers for the project. by [[user:gnuite]]
|-
| '''16:30'''
| width="33%" | '''[[User:Andre/Presentations|Bugsquad meeting]]''' Anybody interested in helping managing the Maemo bugs is welcome! Hosted by [[User:Andre|Andre Klapper]] and [[User:Karstenb|Karsten Bräckelmann]]
| width="33%" | [[Google Data API for Python (Presentation)|'''Introduction to Google's python based Data API's''']] by [[User:Brontide|Eric Warnke]]
| width="33%" | '''Introduction to WebKit''' Come see WebKit's internals, 2 of its ports (Gtk and Qt). by [[User:pierlux |Pierre-Luc Beaudoin]] from [http://www.collabora.co.uk Collabora]
|-
| '''17:00'''
| colspan="3" | [[2010 Agenda|'''Maemo 2010''']]: Brainstorming session discussing current status / future desires for the Maemo platform. Where do we want to go in the next 24 months? What can we learn and share from other mobile platforms? Bring the whole community together to get input.
|-
| '''18:00'''
| colspan="3" | '''End.'''
|}

== Venue ==

The Maemo Summit is held in the headquarter of '''[http://www.c-base.org c-base]''' and the contiguous [http://www.eti-berlin.de/ eti Schauspielschule Berlin].

c-base is a non-profit association which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]). eti Berlin is a school of actors based in a building with several rooms and a total surface available of 1.200m2. The perfect mix, full of creativity!

See [http://share.ovi.com/channel/qgil.public the videos].

c-base is in the very Mitte of Berlin. [http://maps.google.co.uk/maps?ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:unofficial&client=firefox-a&um=1&q=c-base&near=Berlin,+Germany&fb=1&cid=0,0,5828762841994571845&sa=X&oi=local_result&resnum=1&ct=image Map]

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER]'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
See [[Maemo_Summit_2008/Travel|when people are arriving in and leaving Berlin]].

[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxes from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
See [[Maemo Summit 2008/Accommodation]].

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Organization ==
See [[Maemo_Summit_2008/Organization]]. Volunteers needed!

== Links ==

Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]
* [http://www.internettablettalk.com/forums/showthread.php?t=21569 Maemo summit discussion at Internet Tablet Talk]
* [http://lwn.net/Calendar/Monthly/2008-09/ LWN Calendar]

[[Events]]

Task:Maemo Summit 2008/Organization

2008-09-04T21:30:56Z

84.22.107.1: /* Overall coordination */ added housetier

{{task|ongoing}}

There is plenty of things to do for the [[Maemo Summit 2008]] and you can help in any of them.

Propose yourself in any of the ''Who?'' vacant cordination roles. Add yourself to any task you want to volunteer.

== Infrastructure ==
Rooms, equipement, wlan, caffeine.

Quim (Nokia) and Tierhouse (c-base) coordinate.

* Infrastructure and services agreed with c-base. The infrastructure planned can absorb 150-200 people, which is the expected attendance.
** One [http://share.ovi.com/media/qgil.public/qgil.10003?sort=5 big room] and 2 medium for the Summit tracks.
** One small room for the [[Desktop Serach Hackfest]].
** [http://share.ovi.com/media/qgil.public/qgil.10002?sort=5 c-base] social [http://share.ovi.com/media/qgil.public/qgil.10001?sort=5 space].
** Wardrobe, watched storage for gear.
** Two bars at c-base and actor school: free tea, coffee, water. Soft drinks 2€.
** Tables, chairs, power chords, projectors.
** Wlan
** Reception, security.
** Cleaning before, during (e.g. empty bottles), and after the event.
** Technical support (mics, wlan, electricity)..
** Lunch.

* 3 tablets with video out will be available to speakers.
** Recording screencasts. Through VNC client and PC? Through video card? Screencast recorder installed in device??? '''OPEN, OPTIONAL'''
* Ideally 3 laptops available as well, to avoid technical problems with projects. '''OPEN, OPTIONAL'''
** While PDF's are going to work, what other formats will be supported on the laptops? ( PowerPoint version?, Video formats?). A browser is presumed, but what about SSH or other tools? I just want to make sure that if my own equipment becomes unusable/unavailable that my presentations are 100% portable to one of these loaner devices. [[User:brontide|brontide]] 15:47, 8 August 2008 (UTC)
***I'm sure enough of us will be around with laptops for 'backup'. If you worried brontide I can install what ever you need on my laptop just in case yours goes 'pop' at the summit [[User:baloo|baloo]]
** I can still connect my macbook correct? --[[User:rsuplido|Reggie]] 19:24, 8 August 2008 (UTC)
* Central place to link to all presentations and materials used. '''OPEN''' It's an important detail but easy to fix, to be decided.

== Sponsored participants ==
Approval, instructions, expense claims.

Quim coordinates the approval and anything having to do with money and Nokia.

* List of sponsored participants closed, including Maemo community meembers, bloggers and [[Desktop Search Hackfest]] participants. See the "Accepted" in the [http://maemo.org/news/events/maemo_summit-001/ registration list].

== OSiM ==
Maemo activities at http://www.osimworld.com, registration discount.

Quim coordinates since this is mostly about Nokia driven stuff.

* The list of sponsored community members is available at [[Maemo_in_OSiM_World_2008]].
* The developer session on Thursday 18 will have more than what is explained in the program, based on what Ari Jaaksi will present on Wed 17. Erkko Antila (Fremantle product manager), Quim Gil (OSS marketing manager) and Niels Breet (maemo.org webmaster) will share the schedule to discuss software offering, development platform and Maemo community.
* There will be a 3x2m stand shared between Maemo SW / Nokia and maemo.org /Community. Teemu Sorvisto and Eric Warnke coordinate from Nokia & community side.
::Eric can't organise the OSiM exhibit as he is arriving late. He has passed on the mantle to me. [[User:baloo|baloo]]
* There is a plan for a exhibit: [[Maemo_Summit_2008/Exhibit]].

== Program ==
Define the [[Maemo_Summit_2008#Schedule|schedule]].

Quim coordinates the schedule on Friday, the Nokia strong day.
[[User:brontide|Eric Warnke]] coordinates the schedule on Saturday, the community strong day.

* Progressing fine. Should we put any deadline for proposals to ''scare'' people and make them submit? We can always have last minute changes.--[[User:qgil|qgil]] 22:34, 15 July 2008 (UTC)
* Sarturday starts to need some structure, although we can wait to know better what are the sessions proposed.--[[User:qgil|qgil]] 22:34, 15 July 2008 (UTC)
:Please post your proposals for sessions at [[Talk:Maemo_Summit_2008#Lightning_sessions]] or [[Talk:Maemo_Summit_2008#BoFs_and_workshops]].--[[User:qgil|qgil]] 19:19, 17 July 2008 (UTC)
:: I have volunteered myself for Saturday scheduling, I'll get this beaten into a reasonable schedule soon. [[User:brontide|brontide]] 02:54, 25 July 2008 (UTC)

== Merchandising ==
Shirts, stickers and lanyards with the new maemo.org logo are planned.

Coordinated by [http://maemo.org/profile/view/luovanto.html Jussi].

* We got a new logo to use [[Image:Maemo_org_logo_colour.png]].
* Then we will need asap lovely designs for a shirt and a sticker optimized for tablets. We will also produce lanyards for the Summit badges. Glaubert works on this.
* Amounts and sizes to be defined. The reference is the distribution used for GUADEC'06, that went well. Man: 25 XXL - 175 XL - 225 L - 150 M - 50 S. Woman 25 XL - 25 L - 25 M - 10 S. This time we can add shirts for small children since it seems that there are many young parents in the Maemo community.
* Shirts produced in Helsinki so Jussi can check samples and make sure everything is fine.
* Possibility to send out some to key contributors? To be considered specially if this doesn't bring extra work to Nokians (and to Quim to be more precise) :)
:Jussi investigates, any ideas welcome.--[[User:qgil|qgil]] 11:48, 31 July 2008 (UTC)

== Marketing & coverage ==
Inform and engage before, during and after the Summit.

Coordinated by Who? (Nokia) and Who? (Maemo community). Perhaps Who? (c-base) as well.

* Specific tasks to be defined.
* Priority: cover the sponsorship budget with the best contributors asap.
* Priority: keep the registration up to 150 people getting the relevant people in the Maemo community and upstream.
* Jussi and Teemu from the Maemo SW marketing team will help. Back from holidays in August.
* [[User:baloo |Jamie Bennett]] proposes [[Maemo_Summit_2008_recordings|video coverage]]. Time to get into concrete plans.
* [[User:andy80|Andrea Grandi]] offers to take pictures at the event, and blog (almost real time) what happens during the summit in Italian language for people in Italy. --[[User:andy80|andy80]] 14:54, 17 July 2008 (UTC)
* [[User:Timsamoff |Tim]] is helping Jamie with video planning and execution. They've already decided on equipment. He's also bringing a camera to gather stills from the event (but not living blogging them).
* [[User:thoughtfix |ThoughtFix]] will help with interviewing tasks.

== Social events ==
Friday night and whatever else you feel like doing for fun.

Coordinated by Who? (Maemo community) and Who? (c-base).
Quim can help with budget upon request and availability.

* Friday night for sure. Proposals? c-base is well prepared for night fever, multimedia stuff...
* We need to find a shop doing custom shirts sending or bringing an digital image, for the Summit dresscode. I'm totally serious about it. :) --[[User:qgil|qgil]] 22:34, 15 July 2008 (UTC)

== Overall coordination ==
* Shouldn't be needed if the tasks above work just fine. They should be pretty free during the Summit in order to respond efficiently to any issue. They can take shortcuts deciding in urgent cases.
* Quim (Nokia) + Who? (Maemo community) + housetier (c-base)
** I will be coordinating the exhibit at OSiM and can help out on any other role that is needed whist I'm there. [[User:baloo|baloo]]
* Does Nokia need help with registration processes, etc.? If so, I can stand at a table and check people in, etc. Whatever is needed. --[[User:timsamoff|timsamoff]] 02:52, 25 July 2008 (UTC)