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 extensions using a conf file (maybe we should do it the > same way we do it with the external dataproviders, where we just dump the > stuff into a folder). This will come in handy for new releases. (thekorn) > solve issues with external dataproviders that are also logged by recently > used. I think having duplicate entries is no solution since its manipulates > the "most used" (RainCT) > implemnt the "most used with" idea we use to have (seif) > > Also i think at the moment we should also release an extension with the > 0.3.1 > To hype up the extension feature we need to keep it under the > Zeitgeist-Framework umbrella for now. I was thinking of the libchamplain > extension for locations of events (I dont think we need a full fledged repo > for that) > I will make sure the UI is released within a week from now at max. This > could push up our hype again. Also I think RainCT should look into Shell > again. > Other things i would suggest for the engine 0.3.x would be: > > Add the focus shit as an extension > Add more dataproviders (telepathy and evolution) > Finish an ontology
Ok, I just defered all incomplete bugs and blueprints from 0.3.0 to 0.3.1. There's quite a lot on the table for 0.3.1, so we should probably defer some of it to 0.3.2. @Seif - I think we need some bugs or blueprints to track progress of your items 1 and 2 ("Add the focus shit as an extension" and "Add more dataproviders") -- 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