Exporting the "related items" functions to an extension

Bug #597632 reported by Seif Lotfy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Won't Fix
Medium
Seif Lotfy

Bug Description

I think we should export the "related items" functionality to an extension for now. This is due the unity release and we should keep everything slim and trim. It will allow us to experiment more while not messing with the main API. It will give us some new grounds for testing different algorithms. The question is should be a main extension like blacklist OR a community extension.
DEBATE

Seif Lotfy (seif)
Changed in zeitgeist:
assignee: nobody → Seif Lotfy (seif)
importance: Undecided → Medium
milestone: none → 0.4.1
Revision history for this message
Siegfried Gevatter (rainct) wrote : Re: [Bug 597632] [NEW] Exporting the "related items" functions to an extension

My take would be: ship something (what we have now?) by default, try
new stuff as extensions, if some extension is better than the default
(considering the quality/resources usage ratio) make it the new
default in a future version.

Seif Lotfy (seif)
Changed in zeitgeist:
status: New → Opinion
Revision history for this message
Seif Lotfy (seif) wrote :

I would like to bring this issue to Mikkel and Markus's attention....
DING DING DING

Revision history for this message
Siegfried Gevatter (rainct) wrote :

There's also the option I suggested on IRC which is, in addition to keeping it like it is, making it possible for extensions to take over the FindRelated functionality replacing it with their own algorithm.

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I'm with Siegfried here... But Siegfried - can't we already do what you say in comment #3, by using some evil setattr(engine, method, new_method) tricks in the extension?

Changed in zeitgeist:
milestone: 0.4.1 → 0.5.1
Revision history for this message
Siegfried Gevatter (rainct) wrote : Re: [Bug 597632] Re: Exporting the "related items" functions to an extension

2010/7/20 Mikkel Kamstrup Erlandsen <email address hidden>:
> But Siegfried - can't we already do what you
> say in comment #3, by using some evil setattr(engine, method,
> new_method) tricks in the extension?

True. So can this bug be closed?

Revision history for this message
Seif Lotfy (seif) wrote :

You can close it for now but I still think we should export it... I did not
understand mikkels opinion on it.

On Wed, Aug 4, 2010 at 11:39 AM, Siegfried Gevatter <email address hidden>wrote:

> 2010/7/20 Mikkel Kamstrup Erlandsen <email address hidden>:
> > But Siegfried - can't we already do what you
> > say in comment #3, by using some evil setattr(engine, method,
> > new_method) tricks in the extension?
>
> True. So can this bug be closed?
>
> --
> Exporting the "related items" functions to an extension
> https://bugs.launchpad.net/bugs/597632
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Zeitgeist Framework: Opinion
>
> Bug description:
> I think we should export the "related items" functionality to an extension
> for now. This is due the unity release and we should keep everything slim
> and trim. It will allow us to experiment more while not messing with the
> main API. It will give us some new grounds for testing different algorithms.
> The question is should be a main extension like blacklist OR a community
> extension.
> DEBATE
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/zeitgeist/+bug/597632/+subscribe
>

--
This is me doing some advertisement for my blog http://seilo.geekyogre.com

Changed in zeitgeist:
status: Opinion → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.