[Zeitgeist] [Bug 634740] [NEW] explicitly define on a per testcase basis which extension needs to be loaded
Public bug reported: Right now we load all available extensions in our test runs. So if someone as a random (experimental) extension in ~/.local/share/zeitgeist/extensions which fails all our remote and engine testcases fail too. As we have no influence on the installed extensions on the users system we should explicitly configure them on each test run. ** Affects: zeitgeist Importance: Undecided Status: New -- explicitly define on a per testcase basis which extension needs to be loaded https://bugs.launchpad.net/bugs/634740 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: Right now we load all available extensions in our test runs. So if someone as a random (experimental) extension in ~/.local/share/zeitgeist/extensions which fails all our remote and engine testcases fail too. As we have no influence on the installed extensions on the users system we should explicitly configure them on each test run. ___ 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 634744] [NEW] test suite fails if zeitgeist is installed on the system
Public bug reported: Today I tried to run our test suite on a system which has zeitgeist installed and running (maverick netbook edition). The test suite fails with a lot of errors because it was unable to kill the running daemon instance. We should make sure to run our tests on its own private dbus message bus. ** Affects: zeitgeist Importance: Undecided Status: New -- test suite fails if zeitgeist is installed on the system https://bugs.launchpad.net/bugs/634744 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: Today I tried to run our test suite on a system which has zeitgeist installed and running (maverick netbook edition). The test suite fails with a lot of errors because it was unable to kill the running daemon instance. We should make sure to run our tests on its own private dbus message bus. ___ 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] [Merge] lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist
The proposal to merge lp:~zeitgeist/zeitgeist/HACKING.bugtriaging into lp:zeitgeist has been updated. Status: Needs review = Merged -- https://code.launchpad.net/~zeitgeist/zeitgeist/HACKING.bugtriaging/+merge/34840 Your team Zeitgeist Framework Team is subscribed to branch lp:~zeitgeist/zeitgeist/HACKING.bugtriaging. ___ 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 628678] Re: Add bugtriaging guidlines to HACKING
** Changed in: zeitgeist Status: Confirmed = In Progress ** Changed in: zeitgeist Assignee: Zeitgeist Framework Team (zeitgeist) = Markus Korn (thekorn) ** Changed in: zeitgeist Milestone: 0.5.1 = 0.6 ** Changed in: zeitgeist Status: In Progress = Fix Committed -- Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: I've discussed the bugtriaging topic with Seif on irc yesterday, it turned out that we have different opinions on how to triage bugs for the zeitgeist project. We agreed that this needs some discussion, and the final words should be put in our HACKING document. Here is an extract of our discussion: thekorn seif_: can you please tell me what your criteria for choosing the importance of a bugreport is? thekorn I think we should have one definition for importance level throught the whole team seif_ thekorn, yeah seif_ thekorn, if its a build problem or a crash then its critical seif_ :P seif_ if its a wrong functionality then its high thekorn and medium,low or wishlist? seif_ if its an incomplete feature its medium seif_ low and wishlist are intuition seif_ :P thekorn seif_: so if someone tries to build zeitgeist on some very rare linux system, but the build fails, this bug will automatically be critical? seif_ yeah seif_ it means we cant delivder seif_ but ofcourse define rare thekorn only one affected user seif_ hmm seif_ i think it should be seen on a distro level seif_ thekorn, what distro is he using seif_ actually wrong seif_ if he is using our dependencies seif_ then it should work thekorn seif_: also, what dos fix committed mean for you? seif_ there is a fix in the branches thekorn in which branch? thekorn lp:~thekorn/+junk/boo.bar.baz? seif_ any branch proposed for merging thekorn ok, and fix released means: the fix landed in lp:zeitgeist? thekorn so lp:zeitgeist is our release target, and we do not really care about release tarballs? seif_ thekorn, nope seif_ i thought u said trunk always has to be stable seif_ thus we work in branches thekorn IMHO, fix releasedm eans: we have a tarball release which shipps this fix thekorn and fix committed means it's in lp:zeitgeist thekorn in progress means, there is a fix somewhere seif_ thekorn, ok ___ 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 628678] Re: Add bugtriaging guidlines to HACKING
revno: 1578 [merge] fixes bug(s): https://launchpad.net/bugs/628678 committer: Markus Korn thek...@gmx.de branch nick: trunk timestamp: Fri 2010-09-10 10:16:13 +0200 message: Added information about the bug triaging process within zeitgeist to the HACKING document. -- Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: I've discussed the bugtriaging topic with Seif on irc yesterday, it turned out that we have different opinions on how to triage bugs for the zeitgeist project. We agreed that this needs some discussion, and the final words should be put in our HACKING document. Here is an extract of our discussion: thekorn seif_: can you please tell me what your criteria for choosing the importance of a bugreport is? thekorn I think we should have one definition for importance level throught the whole team seif_ thekorn, yeah seif_ thekorn, if its a build problem or a crash then its critical seif_ :P seif_ if its a wrong functionality then its high thekorn and medium,low or wishlist? seif_ if its an incomplete feature its medium seif_ low and wishlist are intuition seif_ :P thekorn seif_: so if someone tries to build zeitgeist on some very rare linux system, but the build fails, this bug will automatically be critical? seif_ yeah seif_ it means we cant delivder seif_ but ofcourse define rare thekorn only one affected user seif_ hmm seif_ i think it should be seen on a distro level seif_ thekorn, what distro is he using seif_ actually wrong seif_ if he is using our dependencies seif_ then it should work thekorn seif_: also, what dos fix committed mean for you? seif_ there is a fix in the branches thekorn in which branch? thekorn lp:~thekorn/+junk/boo.bar.baz? seif_ any branch proposed for merging thekorn ok, and fix released means: the fix landed in lp:zeitgeist? thekorn so lp:zeitgeist is our release target, and we do not really care about release tarballs? seif_ thekorn, nope seif_ i thought u said trunk always has to be stable seif_ thus we work in branches thekorn IMHO, fix releasedm eans: we have a tarball release which shipps this fix thekorn and fix committed means it's in lp:zeitgeist thekorn in progress means, there is a fix somewhere seif_ thekorn, ok ___ 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 628678] Re: Add bugtriaging guidlines to HACKING
** Branch linked: lp:zeitgeist -- Add bugtriaging guidlines to HACKING https://bugs.launchpad.net/bugs/628678 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: I've discussed the bugtriaging topic with Seif on irc yesterday, it turned out that we have different opinions on how to triage bugs for the zeitgeist project. We agreed that this needs some discussion, and the final words should be put in our HACKING document. Here is an extract of our discussion: thekorn seif_: can you please tell me what your criteria for choosing the importance of a bugreport is? thekorn I think we should have one definition for importance level throught the whole team seif_ thekorn, yeah seif_ thekorn, if its a build problem or a crash then its critical seif_ :P seif_ if its a wrong functionality then its high thekorn and medium,low or wishlist? seif_ if its an incomplete feature its medium seif_ low and wishlist are intuition seif_ :P thekorn seif_: so if someone tries to build zeitgeist on some very rare linux system, but the build fails, this bug will automatically be critical? seif_ yeah seif_ it means we cant delivder seif_ but ofcourse define rare thekorn only one affected user seif_ hmm seif_ i think it should be seen on a distro level seif_ thekorn, what distro is he using seif_ actually wrong seif_ if he is using our dependencies seif_ then it should work thekorn seif_: also, what dos fix committed mean for you? seif_ there is a fix in the branches thekorn in which branch? thekorn lp:~thekorn/+junk/boo.bar.baz? seif_ any branch proposed for merging thekorn ok, and fix released means: the fix landed in lp:zeitgeist? thekorn so lp:zeitgeist is our release target, and we do not really care about release tarballs? seif_ thekorn, nope seif_ i thought u said trunk always has to be stable seif_ thus we work in branches thekorn IMHO, fix releasedm eans: we have a tarball release which shipps this fix thekorn and fix committed means it's in lp:zeitgeist thekorn in progress means, there is a fix somewhere seif_ thekorn, ok ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-10 08:21z (21 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-09-10 08:21z (24 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] [Merge] lp:~thekorn/zeitgeist/fix-634055-ontology-docs into lp:zeitgeist
Markus Korn has proposed merging lp:~thekorn/zeitgeist/fix-634055-ontology-docs
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Out ontology is now documented in a table format, which is a bit less pythonic
than our old format and should be more readable (LP: #634055)
To view the new doc run:
make doc
gnome-open doc/zeitgeist/build/html/index.html
--
https://code.launchpad.net/~thekorn/zeitgeist/fix-634055-ontology-docs/+merge/35066
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~thekorn/zeitgeist/fix-634055-ontology-docs into lp:zeitgeist.
=== modified file '.bzrignore'
--- .bzrignore 2010-06-25 22:34:58 +
+++ .bzrignore 2010-09-10 09:16:50 +
@@ -28,6 +28,7 @@
zeitgeist-datahub
doc/zeitgeist/build
doc/zeitgeist/source/.static
+doc/zeitgeist/source/ontology.rst
extra/ontology/*.py
tools/cli/zeitgeist
tools/gtk/zeitgeist
=== modified file 'doc/zeitgeist/Makefile'
--- doc/zeitgeist/Makefile 2009-12-14 09:18:11 +
+++ doc/zeitgeist/Makefile 2010-09-10 09:16:50 +
@@ -25,8 +25,9 @@
clean:
rm -rf build/* source/.static
+ -rm source/ontology.rst
-init:
+init: ontology
mkdir -p build/changes build/doctrees source/.static
html: init
@@ -69,3 +70,6 @@
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) build/changes
@echo
@echo The overview file is in build/changes.
+
+ontology:
+ python source/make_ontology.py source/ontology.rst
=== modified file 'doc/zeitgeist/source/conf.py'
--- doc/zeitgeist/source/conf.py 2010-09-09 21:40:51 +
+++ doc/zeitgeist/source/conf.py 2010-09-10 09:16:50 +
@@ -191,44 +191,3 @@
# Example configuration for intersphinx: refer to the Python standard library.
intersphinx_mapping = {'http://docs.python.org/dev': None}
-
-from sphinx.ext.autodoc import Documenter
-from zeitgeist.datamodel import Symbol, StorageState, ResultType, EnumValue
-
-class SymbolDocumenter(Documenter):
-
-objtype = 'symbol'
-member_order = 160
-directivetype = attribute
-
-@classmethod
-def can_document_member(cls, member, membername, isattr, parent):
-# Symboldocumenter knows how to handle symbols and enums
-return isinstance(parent, Documenter) and \
-isinstance(member, (Symbol, EnumValue))
-
-def generate(self, more_content=None, real_modname=None,
- check_module=False, all_members=False):
-# for symbols we document per default all members
-return Documenter.generate(self, more_content, real_modname, True, True)
-
-def resolve_name(self, modname, parents, path, base):
-# we know where they are, so hardcode the import path
-return zeitgeist.datamodel, parents + [base,]
-
-def get_object_members(self, want_all):
-# we want a special order for enums
-r = Documenter.get_object_members(self, want_all)
-if self.object in (ResultType, StorageState):
-# we sort our enums by integer values
-r = (r[0], sorted(r[1], key=lambda x: x[1]))
-elif isinstance(self.object, Symbol):
-# we treat symbol objects special and only document their child
-# symbols
-return False, sorted((i.name, i) for i in self.object.get_children())
-return r
-
-
-def setup(app):
-app.add_autodocumenter(SymbolDocumenter)
-
=== modified file 'doc/zeitgeist/source/datamodel.rst'
--- doc/zeitgeist/source/datamodel.rst 2010-04-19 19:55:01 +
+++ doc/zeitgeist/source/datamodel.rst 2010-09-10 09:16:50 +
@@ -19,12 +19,14 @@
Interpretation
++
-.. autosymbol:: Interpretation
+A collection of class:`Symbol` objects which represents the interpretations
+defined by the zeitgeist ontology. For more information see :ref:`symbol-interpretation`.
Manifestation
+
-.. autosymbol:: Manifestation
+A collection of class:`Symbol` objects which represents the manifestations
+defined by the zeitgeist ontology. For more information see :ref:`symbol-manifestation`.
TimeRange
+
=== modified file 'doc/zeitgeist/source/index.rst'
--- doc/zeitgeist/source/index.rst 2010-06-10 21:54:05 +
+++ doc/zeitgeist/source/index.rst 2010-09-10 09:16:50 +
@@ -33,3 +33,11 @@
:maxdepth: 2
HACKING
+
+Ontology
+
+
+.. toctree::
+ :maxdepth: 2
+
+ ontology
=== added file 'doc/zeitgeist/source/make_ontology.py'
--- doc/zeitgeist/source/make_ontology.py 1970-01-01 00:00:00 +
+++ doc/zeitgeist/source/make_ontology.py 2010-09-10 09:16:50 +
@@ -0,0 +1,168 @@
+import sys
+import os.path
+import textwrap
+
+sys.path.insert(0, os.path.abspath('../..'))
+
+from zeitgeist.datamodel import Interpretation, Manifestation
+
+ROWS = [Children, Parent, URI, Description, Python object]
+
+PAGE_TEMPLATE = \
+==
+The Zeitgeist Ontology
+==
+
+.. _symbol-interpretation:
+
+Interpretations
+===
+
Re: [Zeitgeist] ANNOUNCE: Zeitgeist 0.5.1
Oops, somehow the mail ended up with the wrong NEWS entry. Here goes the real one: 2010-09-09: Zeitgeist 0.5.1 Spongebob is not funny Engine: - Don't use the return value of Extension.post_insert_event() when dispatching the post insert hooks. The post_insert_event() method has no return value. - Initialize ZeitgeistEngine after RemoteInterface, so that --replace does its job before the main engine and extensions start (LP: #614315). - Added support for queries on the Subject.Storage field of an Event (LP: #580364). - Some optimizations in the find_events() method. Also the profiling data is much more useful. Python API: - Check arguments of Event.new_for_values() and Subject.new_for_values() (LP: #580372). - Redefined the result of TimeRange.always(), UNIX timestamp 0 is now the left corner of the interval (LP: #614295). - Added a new helper module called zeitgeist.mimetypes which basically provides two functions (LP: #586524): * get_interpretation_for_mimetype(), which tries to get a suitable interpretation for a given mime-type. * get_manifestation_for_uri(), which tries to lookup a manifestation for the given URI. - The DataSource model now provides easy access to the information it holds through properties. Overall: - The tool to build our ontology now supports rdflib2 and rdflib3 (LP: #626224). - Added make check and make doc commands to the rootlevel Makefile (LP: #628661) - Translation updates. - Updated test suite. - Documentation updates. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 ___ 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 634055] Re: documentation of our ontology is hardly readable
** Changed in: zeitgeist Status: New = In Progress ** Changed in: zeitgeist Importance: Undecided = Wishlist ** Changed in: zeitgeist Assignee: (unassigned) = Markus Korn (thekorn) ** Changed in: zeitgeist Milestone: None = 0.6 ** Changed in: zeitgeist Milestone: 0.6 = None -- documentation of our ontology is hardly readable https://bugs.launchpad.net/bugs/634055 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: I just figured that the part of [0] where we list the interpretations and manifestations is hardly readable, esp. for people with no python background. Also it is not obvious at the first glance that these symbols have a certain structure. I think if we could make the documentation of the symbols look like the tables on bottom of [1] it would be a big improvement. [0] doc/zeitgeist/build/html/datamodel.html [1] http://www.semanticdesktop.org/ontologies/2007/01/19/nie/ ___ 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 598449] Re: the folders category is empty
** Changed in: unity Milestone: 2010-09-09 = 2010-09-16 -- the folders category is empty https://bugs.launchpad.net/bugs/598449 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Unity: Triaged Status in Unity Files Place: Triaged Status in Zeitgeist Framework: Fix Released Status in “unity-place-files” package in Ubuntu: Triaged Bug description: Binary package hint: unity-place-files Using 0.5.2-0ubuntu1 in current maverick the Folders category is empty though I've been using nautilus and browsing folders since the update, should it record those or is there another way to add folders to the list? ___ 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] [Bug 612344] Re: Blacklist API sucks
2010/9/10 Manish Sinha 612...@bugs.launchpad.net: Will this clear all the blacklists? I just want to remove one specific blacklist Ask for the list of blacklisting rules, remove the one you don't want from it, and set it again (with that rule removed). -- Blacklist API sucks https://bugs.launchpad.net/bugs/612344 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: Guys, GetBlacklist and SetBlacklist (without any signals) for an asynchrounous-by-nature API? Come on! How about changing it to Get, Add, Remove and a changed signal? That way it'd be actually usable... ___ 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 612344] Re: Blacklist API sucks
@Manish: Right, that will clear all blacklists I am afraid. Which is also partially why we have this bug open to come up with something which is easier for apps to handle. -- Blacklist API sucks https://bugs.launchpad.net/bugs/612344 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: Guys, GetBlacklist and SetBlacklist (without any signals) for an asynchrounous-by-nature API? Come on! How about changing it to Get, Add, Remove and a changed signal? That way it'd be actually usable... ___ 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: [Gnome-zeitgeist-users] ANNOUNCE: Zeitgeist 0.5.1
Oops, somehow the mail ended up with the wrong NEWS entry. Here goes the real one: 2010-09-09: Zeitgeist 0.5.1 Spongebob is not funny Engine: - Don't use the return value of Extension.post_insert_event() when dispatching the post insert hooks. The post_insert_event() method has no return value. - Initialize ZeitgeistEngine after RemoteInterface, so that --replace does its job before the main engine and extensions start (LP: #614315). - Added support for queries on the Subject.Storage field of an Event (LP: #580364). - Some optimizations in the find_events() method. Also the profiling data is much more useful. Python API: - Check arguments of Event.new_for_values() and Subject.new_for_values() (LP: #580372). - Redefined the result of TimeRange.always(), UNIX timestamp 0 is now the left corner of the interval (LP: #614295). - Added a new helper module called zeitgeist.mimetypes which basically provides two functions (LP: #586524): * get_interpretation_for_mimetype(), which tries to get a suitable interpretation for a given mime-type. * get_manifestation_for_uri(), which tries to lookup a manifestation for the given URI. - The DataSource model now provides easy access to the information it holds through properties. Overall: - The tool to build our ontology now supports rdflib2 and rdflib3 (LP: #626224). - Added make check and make doc commands to the rootlevel Makefile (LP: #628661) - Translation updates. - Updated test suite. - Documentation updates. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 ___ Mailing list: https://launchpad.net/~gnome-zeitgeist-users Post to : gnome-zeitgeist-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~gnome-zeitgeist-users More help : https://help.launchpad.net/ListHelp
