Data-sources don't identify themselves to Zeitgeist

Bug #602864 reported by Siegfried Gevatter
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Zeitgeist Data-Sources
Fix Released
Low
Michal Hruby
libzeitgeist
Fix Released
Undecided
Unassigned

Bug Description

The first thing they should do before inserting anything is registering themselves with Zeitgeist so that they can be enabled/disabled centrally (and possibly controlled in other ways).

Revision history for this message
Michal Hruby (mhr3) wrote :

Affecting also libzg, as there's missing API for this.

Changed in libzeitgeist:
status: New → Fix Released
Michal Hruby (mhr3)
Changed in zeitgeist-dataproviders:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Michal Hruby (mhr3)
Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

I think this bug should be broken down into individual dataproviders

Revision history for this message
Seif Lotfy (seif) wrote : Re: [Bug 602864] Re: Data-sources don't identify themselves to Zeitgeist

I think this bug is closed :P

2011/4/23 Manish Sinha (मनीष सिन्हा <email address hidden>

> I think this bug should be broken down into individual dataproviders
>
> --
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
> https://bugs.launchpad.net/bugs/602864
>
> Title:
> Data-sources don't identify themselves to Zeitgeist
>
> Status in Zeitgeist Client Library:
> Fix Released
> Status in Zeitgeist Data-Providers:
> Confirmed
>
> Bug description:
> The first thing they should do before inserting anything is
> registering themselves with Zeitgeist so that they can be
> enabled/disabled centrally (and possibly controlled in other ways).
>

Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

Seif,
Do all the dataproviders register themselves to DatasourceRegister before pushing events? I mean all the datasources?

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

This is not our problem. We provide the service to register. Everything we developed registers itself. This bug is related to the datasource-register y. This closing this bug

Changed in zeitgeist-dataproviders:
status: Confirmed → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

On Sun, Apr 24, 2011 at 3:03 AM, Seif Lotfy <email address hidden> wrote:
> This is not our problem. We provide the service to register. Everything
> we developed registers itself. This bug is related to the datasource-
> register y. This closing this bug

I mean the dataproviders which we have created, not the third-party ones.

>
> ** Changed in: zeitgeist-dataproviders
>       Status: Confirmed => Fix Committed
>
> ** Changed in: zeitgeist-dataproviders
>       Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to
> Zeitgeist Data-Sources.
> https://bugs.launchpad.net/bugs/602864
>
> Title:
>  Data-sources don't identify themselves to Zeitgeist
>
> Status in Zeitgeist Client Library:
>  Fix Released
> Status in Zeitgeist Data-Providers:
>  Fix Released
>
> Bug description:
>  The first thing they should do before inserting anything is
>  registering themselves with Zeitgeist so that they can be
>  enabled/disabled centrally (and possibly controlled in other ways).
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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