Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Mikkel Kamstrup Erlandsen
2009/7/20 Seif Lotfy s...@lotfy.com: 2009/7/20 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com SNIP LOVE IT LOVE IT LOVE IT however what happens if i want to log an event where the subject has not been registered yet? My initial idea here was to accept that and create a dummy item

Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Mikkel Kamstrup Erlandsen
2009/7/20 Siegfried Gevatter rai...@ubuntu.com: I tend to agree with your comment but I'm unsure about one thing: With this mindset it also makes sense to differentiate the lookup functions, so we have something like:  FindEvents(...filters...)  FindItems(...filters...) Maybe I'm just

Re: [Zeitgeist] Zeitgeist API Ramblings

2009-08-02 Thread Mikkel Kamstrup Erlandsen
2009/8/2 Siegfried Gevatter rai...@ubuntu.com: SNIP... What I think we really need to decide now is how we want to represent events and items (when returned by FindEvents et all). I think you hit the nail on the head here. I think the current Zg API leaves a blurry line for what Zeitgeist

[Zeitgeist] [Bug 404915] Re: Add API method to change annotations of an item

2009-08-10 Thread Mikkel Kamstrup Erlandsen
Note that this bug heavily interlinks with: https://bugs.launchpad.net/zeitgeist/+bug/411399 -- Add API method to change annotations of an item https://bugs.launchpad.net/bugs/404915 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for

[Zeitgeist] Call for testing: querymancer engine

2009-08-12 Thread Mikkel Kamstrup Erlandsen
Hi all, With Siegfried's latest updates (and some trivial fixes from me) the Querymancer engine is ready for testing before we go gold in 0.2.1. We *REALLY* need your help to dust out any hidden regressions! To test it out start you Zeitgeist daemon with ZEITGEIST_ENGINE=querymancer in the

[Zeitgeist] Zeigeist vs launchpad teams

2009-08-12 Thread Mikkel Kamstrup Erlandsen
I was just trying to makte this very list open for the general public to subscribe. Turns out that this is not possible with the current Zg project structure. Launchpad (LP) has a one-to-one mapping of teams-mailing list. So in effect all on this mailing list has commit access to lp:zeitgeist.

[Zeitgeist] [Bug 404914] Re: Inconsistency in FindEvents/CountEvents filter

2009-08-13 Thread Mikkel Kamstrup Erlandsen
Actually I am talking about both. I stand by what you describe in comment 8 and I myself in comment 3 and you realize in comment 8 :-). But the question in comment 6 is about something else. The bookmarked True/False is also a too weak description. It is not fx. not compatible with the standard

[Zeitgeist] [Bug 404914] Re: Inconsistency in FindEvents/CountEvents filter

2009-08-13 Thread Mikkel Kamstrup Erlandsen
Ok, but then I am basically saying that the only possible consumer of the bookmark field is the dedicated Zeitgeist UI. This design concerns me a little... -- Inconsistency in FindEvents/CountEvents filter https://bugs.launchpad.net/bugs/404914 You received this bug notification because you are

[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items

2009-09-07 Thread Mikkel Kamstrup Erlandsen
Note that events should be regarded as sub types of items, meaning that an event is comprised of both the relevant row in the item table and the corresponding row in the event table. This means that events do in fact have origins. I do agree, however, that an origin is a URL, and as such should

[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items

2009-09-07 Thread Mikkel Kamstrup Erlandsen
Would it be possible for anyone to throw up a draft of the new design? (keeping a copy of the old database design spec around...)? -- origin should be a property of events, not items https://bugs.launchpad.net/bugs/425258 You received this bug notification because you are a member of

[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable

2009-11-16 Thread Mikkel Kamstrup Erlandsen
There is quite a lot of whitespace twiddling in your branch, making it hard to review... I can not see exactly how you plan to load the extensions and how you plan to use the __public_methods__ of the extensions..? -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions

[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)

2009-11-17 Thread Mikkel Kamstrup Erlandsen
Siegfried stated on IRC yesterday that he was in favor of the milliesecond resolution using an INTEGER column (ie. what we have now). I think this means that we have rough consensus..? As for use cases with sub-second resolution think of messaging (IRC, IM). If I continuously say spam on IRC I

[Zeitgeist] [Bug 485698] Re: create an external dataprovider for evolution

2009-11-20 Thread Mikkel Kamstrup Erlandsen
Is there a related branch? I am also wondering if we can in some way hook us into the Tracker eplugin? -- create an external dataprovider for evolution https://bugs.launchpad.net/bugs/485698 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-20 Thread Mikkel Kamstrup Erlandsen
For this question to make sense you have to give a use case and explain why it is not good enough to filter out events manually in the Firefox example. For nitpicking: events can have a title that contains zeitgeist. They can have a subject with text field containing 'zeitgeist'. If we want to

[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails

2009-11-23 Thread Mikkel Kamstrup Erlandsen
@Seif: I think we can allow empty timestamps for convenience. And as I said in comment 1 paragraph 3; we meassure time in milliseconds, hence timestamps are genrated with int(time.time()*1000). -- testInsertGetWithoutTimestamp testcase fails https://bugs.launchpad.net/bugs/486996 You received

[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails

2009-11-23 Thread Mikkel Kamstrup Erlandsen
@Seif: I wouldn't have to care about the timestamp format when sending events if my app doesn't need high precision timing. Just create the Event instance and send it along. Recall that not all apps will be written in Python and using our client libs... -- testInsertGetWithoutTimestamp testcase

[Zeitgeist] [Bug 487321] Re: Origin

2009-11-23 Thread Mikkel Kamstrup Erlandsen
WHY NOT? -- Origin https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: New Bug description: + origin =

[Zeitgeist] [Bug 485433] Re: Dont' raise an exception when a duplicate event is detected

2009-11-23 Thread Mikkel Kamstrup Erlandsen
I'll do this tonight, and update the unit tests accordingly ** Changed in: zeitgeist Assignee: Seif Lotfy (seif) = Mikkel Kamstrup Erlandsen (kamstrup) -- Dont' raise an exception when a duplicate event is detected https://bugs.launchpad.net/bugs/485433 You received this bug notification

[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)

2009-11-23 Thread Mikkel Kamstrup Erlandsen
Yes. Plugins *must* send the timestamps in millis since the Epoch. If apps only use second granularity then we will have three zeroes in the end of the timestamps. -- Use timestamps with milliseconds granularity (was: use REAL) https://bugs.launchpad.net/bugs/483603 You received this bug

[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items

2009-11-23 Thread Mikkel Kamstrup Erlandsen
Yeah. We had a discussion about this at the hackfest and everyone agreed that origin must be a property of the subject(s). So the meaning og origin is where does the subject come from?. For files it is the parent folder. For websites it is the root URL (eg. http://youtube.com). We do need to

[Zeitgeist] [Bug 485433] Re: Dont' raise an exception when a duplicate event is detected

2009-11-24 Thread Mikkel Kamstrup Erlandsen
Fixed in revision #1157 ** Changed in: zeitgeist Status: Triaged = Fix Released -- Dont' raise an exception when a duplicate event is detected https://bugs.launchpad.net/bugs/485433 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant

[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items

2009-11-24 Thread Mikkel Kamstrup Erlandsen
Siegfried, I think you make a good case. However I don't see it conflicting with what we have now though. Whether origin is something on the event or the subject(s) is purely a matter of how one looks at it now that we have a 1 to 1 mapping between events and subjects in the db. The tricky part

[Zeitgeist] [Bug 447417] Re: Zeitgeist should have any kind of system to protect users privacy

2009-11-25 Thread Mikkel Kamstrup Erlandsen
Markus - we already have a DeleteEvents() method taking an array of ids. Just do FindEventIds(templates) and pass them to DeleteEvents. This makes it easy to do highly advanced event deletion schemes. As for blacklisting this is really an issue in apps pushing events to Zeitgeist I think. --

[Zeitgeist] [Bug 447417] Re: Zeitgeist should have any kind of system to protect users privacy

2009-11-25 Thread Mikkel Kamstrup Erlandsen
I think that Siegfried has an important point. Since we like to relay events around the system the Zeitgeist core will need a blacklisting mechanism. There are several steps in such a solution as I see it... We need a matches_template(event_templ) method on the Event class. This will be mighty

[Zeitgeist] [Bug 435099] Re: zeitgeist needs a more powerful testing framework

2009-11-25 Thread Mikkel Kamstrup Erlandsen
Yeah, we've got the json importer now. That helps a lot at least. -- zeitgeist needs a more powerful testing framework https://bugs.launchpad.net/bugs/435099 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status

[Zeitgeist] [Bug 488327] Re: Problems with unicode

2009-11-25 Thread Mikkel Kamstrup Erlandsen
I am pretty sure that the reason for this bug is that we would at times try to decode an already decoded unicode string within our magical UnicodeCursor class. I fixed this in lp:zeitgeist r1164. -- Problems with unicode https://bugs.launchpad.net/bugs/488327 You received this bug notification

[Zeitgeist] [Bug 488327] Re: Problems with unicode

2009-11-25 Thread Mikkel Kamstrup Erlandsen
I am wondering how I can link to a particular revision inside a branch in launchpad bugs? Testing: lp:zeitgeist:1164 1164:lp:zeitgeist -- Problems with unicode https://bugs.launchpad.net/bugs/488327 You received this bug notification because you are a member of Zeitgeist-Engine, which is the

[Zeitgeist] [Bug 488327] Re: Problems with unicode

2009-11-25 Thread Mikkel Kamstrup Erlandsen
Fixed in r1166. We had another double decode of a unicode string in querymancer. ** Changed in: zeitgeist Status: Confirmed = Fix Released -- Problems with unicode https://bugs.launchpad.net/bugs/488327 You received this bug notification because you are a member of Zeitgeist-Engine,

[Zeitgeist] [Bug 447417] Re: Zeitgeist should have any kind of system to protect users privacy

2009-11-25 Thread Mikkel Kamstrup Erlandsen
templates they want to listen for. And then we only notify apps that have registered matching templates. Is this even possible at all with D-Bus? Yes. The direct solution is to have clients register some callback interface. The more elegant approach would be to send directed signals. Then a

[Zeitgeist] [Bug 488550] Re: DB BUG: event id column is redundant

2009-11-25 Thread Mikkel Kamstrup Erlandsen
This is a coindidental match. The event.id column is not a primary key (as rowid is). We can have multiple subjects/event which will give more than one row with the same event id. ** Changed in: zeitgeist Status: New = Invalid -- DB BUG: event id column is redundant

[Zeitgeist] [Bug 488656] Re: firefox extension: use XPCOM instead of communicating via files

2009-11-26 Thread Mikkel Kamstrup Erlandsen
Ah, now I get it. You want to load a Zeitgeist XPCOM component, written in Python, into Firefox, and then from that component import DBus (or simply zeitgeist.client.ZeitgeistClient). This component is then used to implement the extension in Javscript, or am I out on a limb? -- firefox

[Zeitgeist] [Bug 488790] Re: inconsistency in DB

2009-11-26 Thread Mikkel Kamstrup Erlandsen
I am unsure what to do. I, for one, have several versions of Firefox installed. To identify which one sending the event we'd need the whole path to the .desktop file. OTOH getting the correct path to the .desktop file might not always be easy. In the .recently-used.xbel apps are identified simply

[Zeitgeist] [Bug 488967] [NEW] Add event notification and subscription system

2009-11-26 Thread Mikkel Kamstrup Erlandsen
... ** Affects: zeitgeist Importance: High Assignee: Mikkel Kamstrup Erlandsen (kamstrup) Status: Confirmed ** Changed in: zeitgeist Status: New = Confirmed ** Changed in: zeitgeist Importance: Undecided = High ** Changed in: zeitgeist Assignee: (unassigned) = Mikkel Kamstrup

[Zeitgeist] [Bug 487321] Re: Origin

2009-11-26 Thread Mikkel Kamstrup Erlandsen
This bug is mostly about eactly what we want to store in origin, and how to interpret origin exactly. I am deferring it to 0.3.1 because it's unrealistic that we get full clarity on this before the weekend. ** Changed in: zeitgeist Milestone: 0.3.0 = 0.3.1 -- Origin

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-11-26 Thread Mikkel Kamstrup Erlandsen
Do we really want to block 0.3.0 because of this bug? I would say no, otherwise we will ship some very untested code if we want to ship 0.3.0 this weekend. I say defer to 0.3.1, it's only a micro API break. -- Using filters (text match / exclusion / etc) https://bugs.launchpad.net/bugs/485966

[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable

2009-11-26 Thread Mikkel Kamstrup Erlandsen
I believe Markus' branch was merged and the focus stuff removed for now? So we can close this bug? -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable https://bugs.launchpad.net/bugs/483556 You received this bug notification because you are

[Zeitgeist] Prepare for Zeitgeist 0.3.0 this weekend

2009-11-26 Thread Mikkel Kamstrup Erlandsen
Hi there, We a prepping up for rolling our first development release in the Zeitgeist 0.3 series (which will lead up to a stable 0.4 eventually). Our plan is to roll the release this weekend. So developers, please have a look over launchpad (fx. starting at

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-26 Thread Mikkel Kamstrup Erlandsen
If we want to re-instate the old system it is a matter of a few lines. But that would be a step back IMHO. And writing a full template based notification system could not be done in two hours by one. It's not a huge task, but definitely more than two hours :-) Besides, I really think we should

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Let me add a comment here on why we can't just emit a signal to everyone... In the future it is not impossible that many apps are connected to Zeitgeist. Indeed if we have a hook in Gtk+ or Glib then *all* apps are connected to us. Thus we'd send a signal to all desktop processes - waking them up

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
I think I read somewhere in the Tracker changelogs that they committed a fix for this, but maybe I mistook a normal comment on the matter as a real committed fix... Regarding 0.3 status I think we should ship 0.3.0 without it. There's nothing stopping us having 0.3.1 next week already of we have

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
I am looking into the directed signals approach, and from a look at the DBus spec this should be possible. If we can somehow create our own dbus.lowlevel.SignalMessage then we can call set_destination(unique_name) on that. See http://dbus.freedesktop.org/doc/dbus-python/api/. Alse see

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Ok. I think I know how to do this now. I just need to find the time to actually write the code :-) Look at the nested emit_signal() method here: http://dbus.freedesktop.org/doc/dbus-python/api/dbus.decorators- pysrc.html#signal -- Add event notification and subscription system

[Zeitgeist] [Bug 489186] [NEW] GetHighestTimestampForActor is superfluous

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Public bug reported: The method GetHighestTimestampForActor is superfluous as far as I can tell. It can be simply done fully client side by using FindEventIds like so: template = Event.new_for_values(actor=gedit) ids = FindEventIds(TimeRange.until_now(), [template], StorageState.Any, 1,

[Zeitgeist] [Bug 489194] [NEW] Implement storage monitor (devices and connectivity)

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Public bug reported: This is a reminder bug. We need to write a storage monitor that manage the various storage mediums we can have event subjects stored on. The storage monitor should write any changes back to the 'storage' table in the DB. What we need to track is connection and

[Zeitgeist] [Bug 489186] Re: GetHighestTimestampForActor is superfluous

2009-11-27 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Status: New = Triaged ** Changed in: zeitgeist Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup) ** Changed in: zeitgeist Importance: Undecided = Medium ** Changed in: zeitgeist Milestone: None = 0.3.0 -- GetHighestTimestampForActor

[Zeitgeist] [Bug 479985] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] move code to compare two event/subject objects to the actual Event/Subject class

2009-11-27 Thread Mikkel Kamstrup Erlandsen
I added code to check if a given Event matches some tempalte event. We'll need that for notifications and bklacklisting. We don't have a method to check for strict equality though afaik... -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] move code to compare two event/subject objects to the

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Mikkel Kamstrup Erlandsen
Cool that you did this test Markus! I am a bit troubled by the results though... I fear that signals are by definition always broadcasted. We may be able to work around this by setting a match rule on each signal connection on the client side, but I am not sure... Something like adding a named

[Zeitgeist] [Bug 489262] Re: Interpretation conventions

2009-11-28 Thread Mikkel Kamstrup Erlandsen
I think open/close/modify makes the most sense. I prefer 'modify' over 'save' since fx. editing a contact or something like that is done in an instant-apply dialog, without any notion of saving. Of course this whole deal is just a corner of our bigger problem - that we need an event ontology.

[Zeitgeist] ANNOUNCE: Zeitgeist 0.3.0

2009-12-01 Thread Mikkel Kamstrup Erlandsen
Hi, On behalf of the Zeitgeist team I am proud to announce our first development release, Zeitgeist 0.3.0, leading up to what will be our stable series which will be 0.4. It is our intent to aim for a 1.0 release as soon as we feel good about the stable series, but that is still a bit in the

Re: [Zeitgeist] ANNOUNCE: Zeitgeist 0.3.0

2009-12-01 Thread Mikkel Kamstrup Erlandsen
2009/12/1 Neil Jagdish Patel neil.pa...@canonical.com: Hey, Congratulations :) I've got it built and running, however have nothing to test it with -- have the tests been ported over to the new API? They seem to fail with broken D-Bus signatures. Also, are there any front-ends working with

[Zeitgeist] [Bug 491646] Re: Delete unused stuff from DB

2009-12-03 Thread Mikkel Kamstrup Erlandsen
Until we see evidence that our DB indeed clutters up in lots of unused URIs and whatnot (after some DeleteEvents), then I don't think the added complexity is worth it. A more pressing issue is to delete unused URIs after a DeleteEvents because of privacy reasons - it's fine that we delete all

[Zeitgeist] [Bug 489262] Re: Interpretation conventions

2009-12-03 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Milestone: 0.3.0 = 0.3.1 -- Interpretation conventions https://bugs.launchpad.net/bugs/489262 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework: Triaged

[Zeitgeist] [Bug 490110] Re: bug in client.py

2009-12-03 Thread Mikkel Kamstrup Erlandsen
Seif has not been able to reproduce afaik, so marking as invalid ** Changed in: zeitgeist Status: New = Invalid -- bug in client.py https://bugs.launchpad.net/bugs/490110 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for

[Zeitgeist] [Bug 406054] Re: Export extensions and dataproviders into a new package

2009-12-03 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Milestone: 0.3.0 = 0.3.1 -- Export extensions and dataproviders into a new package https://bugs.launchpad.net/bugs/406054 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in

[Zeitgeist] [Bug 397715] Re: I18N of zeitgeist

2009-12-03 Thread Mikkel Kamstrup Erlandsen
I agree with Siegfried. It will be very convenient for apps if the display_name of Categories (Interp. and Manif.) af translated ** Changed in: zeitgeist Milestone: 0.3.0 = 0.3.1 -- I18N of zeitgeist https://bugs.launchpad.net/bugs/397715 You received this bug notification because you are a

[Zeitgeist] [Bug 489186] Re: GetHighestTimestampForActor is superfluous

2009-12-03 Thread Mikkel Kamstrup Erlandsen
I removed this method some time before we released 0.3.0. Marking as Fix Released ** Changed in: zeitgeist Status: Triaged = Fix Released -- GetHighestTimestampForActor is superfluous https://bugs.launchpad.net/bugs/489186 You received this bug notification because you are a member of

[Zeitgeist] [Bug 483550] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper unittests

2009-12-03 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Status: Fix Committed = Fix Released -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper unittests https://bugs.launchpad.net/bugs/483550 You received this bug notification because you are a member of Zeitgeist-Engine, which is the

[Zeitgeist] [Bug 489194] Re: Implement storage monitor (devices and connectivity)

2009-12-03 Thread Mikkel Kamstrup Erlandsen
Ok, let me jot some thoughts donw on this so we have it * All monitoring should be done async, without polling. Ie. using signals and callback, not sleep(5); check_drives(); * I think we can use gio.VolumeMonitor() to listen for connect/disconnect of volumes. Then we use

[Zeitgeist] [Bug 489262] Re: Interpretation conventions

2009-12-03 Thread Mikkel Kamstrup Erlandsen
This is very related to the whole events ontology thing, and must also be meticulously documented in our API docs. Since I am knee deep in both, I'll assign this bug to myself. ** Changed in: zeitgeist Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup) -- Interpretation

[Zeitgeist] [Bug 447417] Re: Zeitgeist should have any kind of system to protect users privacy

2009-12-03 Thread Mikkel Kamstrup Erlandsen
See also bug #491646 ** Tags added: privacy -- Zeitgeist should have any kind of system to protect users privacy https://bugs.launchpad.net/bugs/447417 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in

Re: [Zeitgeist] Planning for Zeitgeist 0.3.1

2009-12-03 Thread Mikkel Kamstrup Erlandsen
2009/12/3 Seif Lotfy s...@lotfy.com: I think a 3 week period for our next release is more than enough As for a plan and set of features to be released we should keep it minimal. From the top of my head this is the TODO list: notification and subscribtions (kamstrup) enabling/disabling

[Zeitgeist] [Bug 491646] Re: Delete unused stuff from DB

2009-12-03 Thread Mikkel Kamstrup Erlandsen
** Tags added: privacy -- Delete unused stuff from DB https://bugs.launchpad.net/bugs/491646 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: KaKaRoTo RainCT, I

[Zeitgeist] [Bug 489194] Re: Implement storage monitor (devices and connectivity)

2009-12-03 Thread Mikkel Kamstrup Erlandsen
but why inet and not internet/online/whatever? Because the wind was in the west and it was a full moon when I wrote it :-) Or perhaps I don't have a good reason. One thing though, I don't know if we should take into consideration or not is tunneling or VPN-like setups. So fx. some resources are

[Zeitgeist] [Bug 489194] Re: Implement storage monitor (devices and connectivity)

2009-12-06 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup) -- Implement storage monitor (devices and connectivity) https://bugs.launchpad.net/bugs/489194 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-12-06 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Status: Confirmed = Fix Committed -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Status

[Zeitgeist] [Bug 489262] Re: Event Interpretations Ontology

2009-12-06 Thread Mikkel Kamstrup Erlandsen
** Summary changed: - Interpretation conventions + Event Interpretations Ontology -- Event Interpretations Ontology https://bugs.launchpad.net/bugs/489262 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Status

[Zeitgeist] [Bug 447417] Re: Zeitgeist should have any kind of system to protect users privacy

2009-12-06 Thread Mikkel Kamstrup Erlandsen
anyway... ** Changed in: zeitgeist Assignee: Seif Lotfy (seif) = Mikkel Kamstrup Erlandsen (kamstrup) ** Summary changed: - Zeitgeist should have any kind of system to protect users privacy + Event blacklisting/Privacy mode -- Event blacklisting/Privacy mode https://bugs.launchpad.net/bugs

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-07 Thread Mikkel Kamstrup Erlandsen
I think Physical location at which the subject resided at the moment of interaction is a good formulation. It is still incomplete though. We need to define whether or not trailing slashes should be included - and stuff like that. I'd like to keep this bug open until all of this is thoroughly

[Zeitgeist] [Bug 493903] Re: new queries

2009-12-07 Thread Mikkel Kamstrup Erlandsen
In more technical engine-terms I think you are talking about defining some more zeitgeist.datamodel.ResultTypes? I don't understand 2, but something like 1 might be a good idea. Maybe we need to go full monty on this: MostPopularActor MostRecentActor MP Origin MR Origin For consistency we'd also

[Zeitgeist] [Bug 493923] [NEW] Alternative mainloops

2009-12-07 Thread Mikkel Kamstrup Erlandsen
Public bug reported: I think the core engine only relies on the GObject bindings in order to get the mainloop integration needed to get DBus playing nice. We should have a pluggable mainloop thing so that we can use the Qt mainloop instead. On the longer term we might want to look into writing

[Zeitgeist] [Bug 493923] Re: Alternative mainloops

2009-12-08 Thread Mikkel Kamstrup Erlandsen
Ok. I am removing the 0.3.2 because of the disheartening comment in http://dbus.freedesktop.org/doc/dbus-python/api/dbus- module.html#set_default_main_loop I can see that progress on non-native mainloops in Python DBus has not been made since 2006/2007-ish. I'll look a bit more into this. If we

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-08 Thread Mikkel Kamstrup Erlandsen
There is no need for event origin. If u want the origin of an event u look for the subject of the event before The client has no rigorous way to find out which event came before. We can apply heuristics, but I don't like that -- What value should subject.origin have?

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-08 Thread Mikkel Kamstrup Erlandsen
there are three interesting URIs to log: - The URL my brower window points to That's what I consider as origin, and why I'm asking for other stuff to use a different name (be it domain or whatever else). Ok. Let's skip the finer details of the naming as long as we agree on the basic

[Zeitgeist] [Bug 494288] Re: apriori: get most used (websites/notes/documents/etc...)

2009-12-09 Thread Mikkel Kamstrup Erlandsen
Forgot to add - great work on the branch! -- apriori: get most used (websites/notes/documents/etc...) https://bugs.launchpad.net/bugs/494288 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 494288] Re: apriori: get most used (websites/notes/documents/etc...)

2009-12-09 Thread Mikkel Kamstrup Erlandsen
I don't think we should consider open/close events when calculating these relations. That way it wont work for contacts and other non-file- like items. The initial step of the algorithm: Fetch the last 7 events for this subject uri seems good. The next step where you create a time range

[Zeitgeist] [Bug 494288] Re: apriori: get most used (websites/notes/documents/etc...)

2009-12-09 Thread Mikkel Kamstrup Erlandsen
Siegfried: Ouch. Got me :-) How about if we do ORDER count(subj_uri) LIMIT 5 instead? It would change the ordering (quelle surprise :-)), but I am wondering what the correct ordering here is? By popularity or by recency? -- apriori: get most used (websites/notes/documents/etc...)

[Zeitgeist] [Bug 494288] Re: apriori: get most used (websites/notes/documents/etc...)

2009-12-09 Thread Mikkel Kamstrup Erlandsen
Seif: Fx. delta = 15 minutes, (=90ms). So you take into account all events that happened in a 15 minute radius of the timestamp. As far as I can see the way you do it would be meen that you consider two events related if there are no other events in between? I honestly don't know which

[Zeitgeist] [Bug 495179] [NEW] What to do on failed or blocked event insertions?

2009-12-10 Thread Mikkel Kamstrup Erlandsen
Public bug reported: This bug is filed in relation to bug #495017: AttributeError: 'NoneType' object has no attribute 'payload' Markus asks what to do with failed or blocked events in InsertEvents(). This is an important questions since we can't not raise an error or simply leave the event id

[Zeitgeist] [Bug 495017] Re: AttributeError: 'NoneType' object has no attribute 'payload'

2009-12-10 Thread Mikkel Kamstrup Erlandsen
Bleh, I meant bug #495179 -- AttributeError: 'NoneType' object has no attribute 'payload' https://bugs.launchpad.net/bugs/495017 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework:

[Zeitgeist] [Bug 495017] Re: AttributeError: 'NoneType' object has no attribute 'payload'

2009-12-10 Thread Mikkel Kamstrup Erlandsen
I opened bug #495017 to discuss the case of errors or blocked events. Let's keep this bug on track :-) -- AttributeError: 'NoneType' object has no attribute 'payload' https://bugs.launchpad.net/bugs/495017 You received this bug notification because you are a member of Zeitgeist Framework, which

[Zeitgeist] [Bug 495179] Re: What to do on failed or blocked event insertions?

2009-12-11 Thread Mikkel Kamstrup Erlandsen
We could use negative integers as error indicators, but that would require that we break DBus API since we use uint32 (signatire u) as event _ids now. The alternative is to use 64 bit ints (signature x). It's not a big break though - transpararent in Python actually... Looking at your branch now.

[Zeitgeist] [Bug 495179] Re: What to do on failed or blocked event insertions?

2009-12-11 Thread Mikkel Kamstrup Erlandsen
If you rename _wrap_insert_event() to something like _insert_event_without_error() or something like that to indicate the purpose of the method I think the branch is fine to go in. -- What to do on failed or blocked event insertions? https://bugs.launchpad.net/bugs/495179 You received this bug

[Zeitgeist] [Bug 495392] Re: What to do if an event is not found or blocked when calling GetEvents (or its engine equivalent)

2009-12-12 Thread Mikkel Kamstrup Erlandsen
I think it looks good. The primary missing point is documentation. The DBus API needs to be documented in this regard. This also holds for the recent change with event id 0 indicates an error. It's ok to merge without it. If you don't get around to this it's ok - I'll try to remember doing it

[Zeitgeist] [Bug 494288] Re: apriori: get most used (websites/notes/documents/etc...)

2009-12-12 Thread Mikkel Kamstrup Erlandsen
... maybe we should change the function to take a list of subject URIs ... Agreed -- apriori: get most used (websites/notes/documents/etc...) https://bugs.launchpad.net/bugs/494288 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for

[Zeitgeist] [Bug 485966] Re: Using filters (text match / exclusion / etc)

2009-12-15 Thread Mikkel Kamstrup Erlandsen
Any comments? Yes :-) We also need to support matching semantics in the Event.matches_template() method. If FindEventIds() and Event.matches_template() do not line up 100% then monitors installed with InstallMonitor() will not coincide with the Find* results. There is also the open request to

[Zeitgeist] [Bug 497306] Re: add HACKING document to the zeitgeist project

2009-12-16 Thread Mikkel Kamstrup Erlandsen
- TABs for indentation - All code in zeitgeist.* is our public API and *must* be fully documented - Code in _zeitgeist is private code and should be documented and written in a way so that others can understand it -- add HACKING document to the zeitgeist project

[Zeitgeist] [Bug 488790] Re: What value should event.actor have?

2009-12-16 Thread Mikkel Kamstrup Erlandsen
I think that you proposal is ok, except that application_name should be the base filename of the .desktop file for the app. The reason is that apps need to be able to find the corresponding .desktop file easily - to show icons, internationalized names, etc. With your proposal one needs to sift

[Zeitgeist] [Bug 497324] Re: documentation of zeitgeist

2009-12-16 Thread Mikkel Kamstrup Erlandsen
Can we have the URL links of the Manifestation and Interpretation types like we used to? They are mighty handy because the Nepomuk URLs actually point at the docs. Other than that - mighty good work! The docs look sweet! -- documentation of zeitgeist https://bugs.launchpad.net/bugs/497324 You

[Zeitgeist] [Bug 447417] Re: Event blacklisting/Privacy mode

2009-12-17 Thread Mikkel Kamstrup Erlandsen
I just linked the branch lp:~kamstrup/zeitgeist/blacklist to this bug report. It contains some initial work, but it is *far from finished* - so no need to review it yet. ** Branch linked: lp:~kamstrup/zeitgeist/blacklist -- Event blacklisting/Privacy mode https://bugs.launchpad.net/bugs/447417

[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable

2009-12-17 Thread Mikkel Kamstrup Erlandsen
** Branch linked: lp:~kamstrup/zeitgeist/blacklist -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable https://bugs.launchpad.net/bugs/483556 You received this bug notification because you are a member of Zeitgeist Developers, which is the

[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable

2009-12-17 Thread Mikkel Kamstrup Erlandsen
I just linked lp:~kamstrup/zeitgeist/blacklist to this report because it contains some initial work needed to load extensions dynamically. The work is not nearly done, nor tested or documented, so please hold your reviews back a bit until I ping you :-) --

[Zeitgeist] Wrapping up 0.3.1

2009-12-17 Thread Mikkel Kamstrup Erlandsen
Ladys and Gents, If we want to wrap up 0.3.1 before Christmas I believe this weekend (19+20/12-2009) is our only shot. Glancing at https://launchpad.net/zeitgeist/+milestone/0.3.1 I see that there's a lot of stuff we are going to punt to 0.3.2 if we want 0.3.1 this weekend. This is of course

[Zeitgeist] [Bug 498878] Re: non-clear API: get_*_most_used*

2009-12-20 Thread Mikkel Kamstrup Erlandsen
After flaming each other on IRC (A... it's always a joy fighting with you guys ;-P) we came more or less to the following API: FindRelatedSubjects(in (xx) time_range, in aE event_templates, in aE related_event_templates,

[Zeitgeist] [Bug 499788] [NEW] License change LGPL 3 to LGPL 2.1 or later

2009-12-23 Thread Mikkel Kamstrup Erlandsen
Public bug reported: There's a push to change the license of the codebase from LGPL 3 to LGPL 2.1 or later. As it stands we have full consent from Seif Lotfy and Mikkel Kamstrup. Siegfried Gevatter has made a conditional +1: If _everyone_ else wants to switch from LGPL3 or later to LGPL 2.1or

[Zeitgeist] [Bug 501862] [NEW] Launchpad Mailing List and Group Setup

2009-12-31 Thread Mikkel Kamstrup Erlandsen
Public bug reported: Our Launchpad group and mailing list setup is confusing to new users. People not familiar with Launchpad will most likely go to launchpad.net/zeitgeist and find out that they can't join the mailing list. The technical reason for this is that we use the ~zeitgeist team for

[Zeitgeist] [Bug 503619] Re: Failing remote-test and blacklist-test testcases

2010-01-05 Thread Mikkel Kamstrup Erlandsen
They used to work fine so some recent commit must have broken them -- Failing remote-test and blacklist-test testcases https://bugs.launchpad.net/bugs/503619 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for Zeitgeist Framework.

[Zeitgeist] [Bug 489262] Re: Event Interpretations Ontology

2010-01-07 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Milestone: 0.3.1 = 0.3.2 -- Event Interpretations Ontology https://bugs.launchpad.net/bugs/489262 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework:

[Zeitgeist] [Bug 488790] Re: What value should event.actor have?

2010-01-07 Thread Mikkel Kamstrup Erlandsen
I just documented this in trunk. ** Changed in: zeitgeist Status: Triaged = Fix Released -- What value should event.actor have? https://bugs.launchpad.net/bugs/488790 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for

[Zeitgeist] Code freeze and release 0.3.1 this sunday?

2010-01-07 Thread Mikkel Kamstrup Erlandsen
Hi, In order to get our act together I propose that we go into code freeze tomorrow at midnight (that is only trivial changes and fully approved patches go in) and release 0.3.1 this sunday (10/1-2009). This leaves Saturday and part of Sunday for testing and polish. However the recent UI-flurry

[Zeitgeist] [Bug 499788] Re: License change LGPL 3 to LGPL 2.1 or later

2010-01-08 Thread Mikkel Kamstrup Erlandsen
Ok - I duly accept that I have been over ruled :-) Marking bug as won't fix. ** Changed in: zeitgeist Status: New = Won't Fix -- License change LGPL 3 to LGPL 2.1 or later https://bugs.launchpad.net/bugs/499788 You received this bug notification because you are a member of Zeitgeist

  1   2   3   4   >