[Zeitgeist] [Bug 447417] Re: Event blacklisting/Privacy mode
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 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework: Confirmed Bug description: Zeitgeist should respect the following use cases: * Tim has a directory ~/Videos/pr0n, he does not want zeitgeist to track any events regarding this directory * Tina played a card game at work and found out that this event is shown in her zeitgeist client, she would like to remove this event to hide it from her boss ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable
** 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 registrant for Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: right now the relevancy-provider is loaded by default. Unfortunately this extension is kind of buggy and not well tested, so in case of errors while loading this extension the whole engine would fail to run. We need a configurable plugin-system for our extensions, and for now we should per default disable loading the relevancy provider. If this provider gets more stable we should easily be able to add this extension to the default extensions which are automatically loaded on engine initialization. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable
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 :-) -- [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 registrant for Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: right now the relevancy-provider is loaded by default. Unfortunately this extension is kind of buggy and not well tested, so in case of errors while loading this extension the whole engine would fail to run. We need a configurable plugin-system for our extensions, and for now we should per default disable loading the relevancy provider. If this provider gets more stable we should easily be able to add this extension to the default extensions which are automatically loaded on engine initialization. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Wrapping up 0.3.1
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 regrettable but I still think we have *plenty* new stuff (and bug fixes!) for another minor release. I would really like to get the Blacklisting+extension loading in 0.3.1, but I can not guarantee that I am ready this weekend (I'll give it a shot though). I'll be quite busy this weekend, but I might be able to find a slot to roll the release Sunday night, unless someone else would like to do that (or has better time). What are your thoughts? -- Cheers, Mikkel ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] Wrapping up 0.3.1
On Thu, Dec 17, 2009 at 9:19 PM, Mikkel Kamstrup Erlandsen wrote: > 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 regrettable but I still think we > have *plenty* new stuff (and bug fixes!) for another minor release. > > I would really like to get the Blacklisting+extension loading in > 0.3.1, but I can not guarantee that I am ready this weekend (I'll give > it a shot though). I'll be quite busy this weekend, but I might be > able to find a slot to roll the release Sunday night, unless someone > else would like to do that (or has better time). > > What are your thoughts? I agree with you, we should just release what we have at the end of this weekend to get our desks clean before holidays. For me moving missing bits to the next point-release is not a big deal, as long as we can guarantee this release being in a not so far future (within the first weeks of January). Markus ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] Wrapping up 0.3.1
On Thu, Dec 17, 2009 at 9:49 PM, markus korn wrote: > On Thu, Dec 17, 2009 at 9:19 PM, Mikkel Kamstrup Erlandsen > wrote: >> 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 regrettable but I still think we >> have *plenty* new stuff (and bug fixes!) for another minor release. >> >> I would really like to get the Blacklisting+extension loading in >> 0.3.1, but I can not guarantee that I am ready this weekend (I'll give >> it a shot though). I'll be quite busy this weekend, but I might be >> able to find a slot to roll the release Sunday night, unless someone >> else would like to do that (or has better time). >> >> What are your thoughts? > > I agree with you, we should just release what we have at the end of > this weekend to get our desks clean before holidays. > For me moving missing bits to the next point-release is not a big > deal, as long as we can guarantee this release being in a not so far > future (within the first weeks of January). > > Markus > Sorry, clicked the wrong button, one thing I would like to add: Blacklisting would be really nice to have, but it won't hurt if we move it to 0.3.2. If I can help you with it, just ping me, I've some time on Saturday morning, as I already brought all my Christmas presents ;) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 497188] Re: add get_most_used_with_subjects to client.py
** Changed in: zeitgeist Assignee: (unassigned) => Siegfried Gevatter (rainct) ** Changed in: zeitgeist Status: New => Triaged ** Changed in: zeitgeist Importance: Undecided => Medium -- add get_most_used_with_subjects to client.py https://bugs.launchpad.net/bugs/497188 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: get_most_used_with_subjects needs to be in client.py ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 494288] Re: "apriori": get most used (websites/notes/documents/etc...)
I think we need to change the api for apriori right now we ask for "most used documents" with x what about asking for "most used documents of mimetype a" with x a simple solution for that is to send a second argument to the most used in form of a list of Subjects where some specifications are set. this way we can ask for not only mimetypes but interpretations or manifestations too. What do u think? -- "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 Framework. Status in Zeitgeist Framework: New Bug description: We have a branch with the 1-step apriori algorithm built. Right now it throws out the most used items with another item We should make it configurable to be able to ask for most used interpretations of items with other items This way we can for example ask for most used "websites" with document X etc what do u think? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
