seeks-users Mailing List for Seeks (Page 2)
Status: Beta
Brought to you by:
beniz
Menu
▾
▴
seeks-users — User forum
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(26) |
Feb
(20) |
Mar
(5) |
Apr
|
May
(2) |
Jun
|
Jul
(10) |
Aug
|
Sep
(9) |
Oct
|
Nov
(5) |
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Camille H. <mam...@yo...> - 2011-07-04 17:38:17
|
Hi, our friends from Meta-IT (http://alt.meta-it.fr/) drafted a new logo based on the Braille of the word "Seeks", here it is, attached. Camille. -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Camille H. <mam...@yo...> - 2011-07-04 17:33:48
|
Hi all, I developed a Seeks plugin for Popcorn (the HTML5 Media Framework developed by Mozilla), it's based on Seeks YUI. Popcorn: http://popcornjs.org/ Seeks plugin for Popcorn: http://seeks-project.info/wiki/index.php/Popcorn Sintel trailer demo (with Seeks+Twitter+OpenStreetMap plugins): http://garbure.org/~mammique/soft/seeks/popcorn/sintel.html Camille. -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Camille H. <mam...@yo...> - 2011-07-02 00:13:10
|
Changelog:
* New wiki page: http://seeks-project.info/wiki/index.php/YUI
* Moved Seeks Client to Seeks YUI
(https://gitorious.org/seeks-client/ ->
https://gitorious.org/seeks-yui/)
* Code: comments, documentation & cleanup.
* Split plugins & extensions for more generic mix/match class use
(WidgExt*).
* Atomic .syncUI() for Y.Seeks.SearchResultTextWidget.
* Improved use of Y.Recordset (indexes and result sorting).
* Atomic Y.Seeks.SearchResult*Widget sorting.
* Y.Seeks.SearchResult*Widget re-ranking.
* Generic WidgExtBusy extension.
* Revised signal firing & nomenclature.
* Rearranged Y.Seeks.SearchPad, Y.Seeks.SearchRequestHandler &
Y.Seeks.SearchResultPool hierarchy.
* Rearranged Y.Widget, Y.widgetParent & Y.widgetChild hierarchy.
* Moved widgets within workspace module and merged.
* Minified and combo JavaScript files.
* Minified CSS.
* Revised object nomenclature.
* Rearranged module tree.
* CSS: improvements, nomenclature, class hierarchy.
* Examples.
* Sample code tutorial:
http://seeks-project.info/wiki/index.php/YUI#Sample_code
--
The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1
|
|
From: Emmanuel B. <ebe...@se...> - 2011-07-01 09:21:21
|
Hi, Recent Debian testing & sid seem to undergo some trouble with their packaging of OpenCV: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624917 Waiting for a fix by Debian contributors, Seeks needs to be compiled without OpenCV support, even if the library is installed on the system, and detected by Seeks' configure script. To do this: ./configure --disable-opencv Disabling OpenCV only affects the image similarity analysis in image search. See http://redmine.seeks-project.info/issues/455 for the ticket & report. Thanks Em. |
|
From: Emmanuel B. <ebe...@se...> - 2011-07-01 07:30:58
|
Hi, from 0.3.4 onward, libevent-2.x is default for the built-in Web server plugin. Support for libevent-1.x for systems on which 2.x is not yet packaged, can be forced at configure time: ./configure --enable-libevent1 There is _no_ automatic detection of libevent version. Related redmine entry is here: http://redmine.seeks-project.info/issues/450 Thanks, Em. |
|
From: Camille H. <mam...@yo...> - 2011-05-30 16:33:24
|
Hi all, I drafted a small Firefox extension for Seeks. For the moment it just opens a notification box in pages for active ranking (when such pages has been proposed as a result by a Seeks node). http://www.seeks-project.info/wiki/index.php/Firefox Camille. -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Camille H. <mam...@yo...> - 2011-05-02 02:13:26
|
Hi all, I'm preparing the upcoming release of Seeks YUI 0.1b-4, it has several new features and improvements regarding real time i/o network events, triggered according to client/server interactions. I've set up a temporary minimalistic interface to test this pre-release here: http://garbure.org/~mammique/soft/seeks/yui/experimental/ You're welcome to play with it and feedback. Please note that real time synchronization events are trigger by default from the UI (here re-ranking) because the data sent by the nodes isn't very dynamic yet. But YUI Seeks is ready for it, so if you want the server's data alterations to be reflected in the UI in real time use this alternate mode: http://garbure.org/~mammique/soft/seeks/yui/experimental/index2.html Camille. -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Camille H. <mam...@yo...> - 2011-03-08 03:02:06
|
Le 08/03/2011 09:28, Emmanuel Benazera a écrit :
> Camille,
>
> thanks for the great work, and the patience with YUI, I really mean
> it. Especially since you've made clear that it was difficult but
> powerful.
>
> I haven't had the time to test it. Is there a 'testable' UI you've set
> up online that I and other can try yet ? If I understand you well, the
> procedure is to 'clone' the gitorious repository then to run the code
> directly from a browser, am I right ?
The API is a kind of a Lego box for developpers, they will be able to
build any kind of tool for Seeks, including UIs, but also lightweight
widgets, or background utilities that hasn't any interface.
Some important second level elements are missing (I'm working on it), so
nothing impressive nor usable yet (even if the biggest part fo the API
is realized). There is a search workspace with only a dashboard (without
request handlers yet) for my personnal tests in reloaded/index.html, if
you want to see how to use it. Basically you just call seeks modules in
a YUI instance, and plug elements the way you wish (or extend them in
new classes):
YUI().use('seeks-search-workspace', function (Y) {
var search = new Y.Seeks.SearchWorkspace();
[…]
};
Camille.
>
> Em.
>
> On Mon, Mar 07, 2011 at 11:54:04AM +0700, Camille Harang wrote:
>> Yo bees, sorry I posted this on the wrong list yesterday, and in the
>> wrong language, here it is:
>>
>> I just finished the first YUI API layer for Seeks, I mean the minimal
>> clockwork to conceive modular and robust Seeks enabled Web applications.
>> Some parts are still missing:
>>
>> 1 - few 2nd level elements to get the interest of developers, but it's
>> coming soon (unless unexpected hitches).
>>
>> 2 - few working examples testifying of the emerged part of the iceberg
>> that is the API.
>>
>> It's a consequent piece of software, but still under water. Curious
>> and/or fellow connaisseurs can take a look at the documentation:
>>
>> http://garbure.org/~mammique/soft/seeks/yui/doc/
>>
>> And code:
>>
>> http://gitorious.org/seeks-client/seeks-client/trees/master/reloaded/script/
>>
>> For the other bees, bee patient ;-p
>>
>> Camille.
--
The Good, the Bad and the Ugly under Creative Commons!
https://yooook.net/r/lp1
|
|
From: Emmanuel B. <ebe...@se...> - 2011-03-08 02:41:00
|
Hi all, below is a wrapup of our Seeks' most recent meeting of last March 2nd and 3rd, on IRC. The discussion mostly involved Stephane Bonhomme (waloo), Camille Harang (mammique) and myself (beniz), with interventions from Pablo Joubert (piti), on parsers, scrapers, and input connectors for Seeks'. As a reminder, Seeks acts as a decentralized collaborative filter on top of an arbitrary number of personal and public feeds. Typically, most common feeds include results from conventional search engines, thus building a meta-search engine. Logs from the discussion are available here: http://redmine.seeks-project.info/issues/336 The goal of the discussion was to: - assess the parser theoretical complexity and technical features; - discuss how to make parsers more expressive ane easier at the same time. This would benefit the project twice: by lowering the difficulty to contribute to Seeks; by opening the way to a jungle of tiny parsers / scrapers, able to cover a large part of the Web (an idea defended by mammique extensively in an earlier thread). First we reviewed the two types of parsers, tree-based and event-based. The latter are of linear complexity while tree-based exhibit a log-linear complexity. For this reason, until now, Seeks has only implemented event-based parsers in the form of SAX parsers. However, SAX parsers are not robust to tiny changes in the feed structure, and are expensive to tweak. Tree-based parsers instead allow to express powerful queries, and thus reduce a parser to declarative expressions in a given language. Typically, xpath was recommended by waloo as the number one way to go for this type of parsers. Tree-based is more robust, and fits with all dominant dom-like data structures on the Web (rss / atom / html / xml). Example, it allows to say a 'snippet' is /div[3]/span[12]/after:h2 Waloo sums it up saying 'the balance is between the efficiency / and power of expression'. Next was mentioned the novel ability to check a grammar with libxml2, while parsing it. I'm not sure this has to be considered right now. This seems a path to explore though. On the application side, xpath may not allow to post-process the scrapped snippets (output of the parsers), while a SAX parser does it within its treatment loop (since this loop is directly written in C++ in our case, as opposed to the declarative query language of xpath). Next, it was agreed that we should retain the SAX parsing capability while adding support for at least xpath. Further discussion the next day led to the inclusion of more declarative formats. Typically, support for CSS selectors, regexp (existing), and JSON (input) should come at some point later. xpath remains the first format to add support for. The idea remains to have a number of connectors, at least one per feed source type. The connectors would be instanciated at startup (or hot-pluggable) by reading either a declarative description or by using a derived SAX parser. Waloo sketches a declarative parser description roughly as: - a parse name (unique); - a xpath expression identifying the list of snippets; - an relative xpath expression for each snippet element you need; Finally, it was agreed that OpenSearch response element (http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_response_elements) should be supported ASAP with a SAX parser. This is ticket http://redmine.seeks-project.info/issues/226 From there, the current path seems to be: a/ write a parser configuration file as proposed by waloo. This file would contain what elements are crucially needed to be parsed from input put feed (e.g. title, URL, summary, ...), and some optional fields. b/ Study, design & implement a basic architecture for connectors (parsers, scrapers) better / simpler / more flexible integration in the 'websearch' plugin. Waloo has started working on a/. (I'm missing the URL right now). I should be able to take care of b/ after I'm done with my current bag of tickets. Unless someone else jumps in. In a short future, I'll put down the chain of tickets on the redmine for completing b/. Waloo, Mammique, thanks for taking the time of thinking and then discussing these issues. These extensions of Seeks to the outside world should prove key in the future. Em. |
|
From: Emmanuel B. <ebe...@se...> - 2011-03-08 02:26:42
|
Camille, thanks for the great work, and the patience with YUI, I really mean it. Especially since you've made clear that it was difficult but powerful. I haven't had the time to test it. Is there a 'testable' UI you've set up online that I and other can try yet ? If I understand you well, the procedure is to 'clone' the gitorious repository then to run the code directly from a browser, am I right ? Em. On Mon, Mar 07, 2011 at 11:54:04AM +0700, Camille Harang wrote: > Yo bees, sorry I posted this on the wrong list yesterday, and in the > wrong language, here it is: > > I just finished the first YUI API layer for Seeks, I mean the minimal > clockwork to conceive modular and robust Seeks enabled Web applications. > Some parts are still missing: > > 1 - few 2nd level elements to get the interest of developers, but it's > coming soon (unless unexpected hitches). > > 2 - few working examples testifying of the emerged part of the iceberg > that is the API. > > It's a consequent piece of software, but still under water. Curious > and/or fellow connaisseurs can take a look at the documentation: > > http://garbure.org/~mammique/soft/seeks/yui/doc/ > > And code: > > http://gitorious.org/seeks-client/seeks-client/trees/master/reloaded/script/ > > For the other bees, bee patient ;-p > > Camille. |
|
From: Camille H. <mam...@yo...> - 2011-03-07 04:57:45
|
Le 07/03/2011 11:54, Camille Harang a écrit : > 2 - few working examples testifying of the emerged part of the iceberg > that is the API. s/emerged/immersed/g |
|
From: Camille H. <mam...@yo...> - 2011-03-07 04:54:08
|
Yo bees, sorry I posted this on the wrong list yesterday, and in the wrong language, here it is: I just finished the first YUI API layer for Seeks, I mean the minimal clockwork to conceive modular and robust Seeks enabled Web applications. Some parts are still missing: 1 - few 2nd level elements to get the interest of developers, but it's coming soon (unless unexpected hitches). 2 - few working examples testifying of the emerged part of the iceberg that is the API. It's a consequent piece of software, but still under water. Curious and/or fellow connaisseurs can take a look at the documentation: http://garbure.org/~mammique/soft/seeks/yui/doc/ And code: http://gitorious.org/seeks-client/seeks-client/trees/master/reloaded/script/ For the other bees, bee patient ;-p Camille. -------- Message original -------- Sujet: Seeks YUI API (0.1b) Date : Sun, 06 Mar 2011 01:05:06 +0700 De : Camille Harang <mam...@yo...> Pour : ad...@li... Yo bees, j'ai terminé la première couche de l'API YUI pour Seeks, c'est-à-dire l'horlogerie minimale pour pouvoir concevoir des applis Web Seeks modulaires et robustes. Il manque encore : 1 - quelques éléments de second niveau pour pourvoir intéresser les développeurs, mais ça ne saurait tarder (sauf imprévus). 2 - quelques exemples fonctionnels témoignant de la partie immergé de cet iceberg qu'est l'API. C'est un bon morceau mais encore sous le niveau de l'eau. Les curieux et/ou les connaisseurs peuvent jeter un œil à la doc: http://garbure.org/~mammique/soft/seeks/yui/doc/ Et au code : http://gitorious.org/seeks-client/seeks-client/trees/master/reloaded/script/ Pour les autres (encore) un peu de patience. Camille. -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-28 15:50:19
|
On Tue, Feb 22, 2011 at 10:02:36PM +0100, Emmanuel Benazera wrote: > On Tue, Feb 22, 2011 at 09:45:05PM +0100, Bastien wrote: > > Emmanuel Benazera <ebe...@se...> writes: > > > > >> That's why I reported the problem: ./configure went fine, and > > >> compilation didn't. > > > > > > And that's why I did give a pointer to the AUR packagers :) > > > > Mh.. would be better to be able to configure/compile with no error no? > > When a compilation problem occurs on archlinux *only* and is solved by archlinux > packagers with no intervention nor request to Seeks developpers, I call > it an archlinux problem, until I'm proved otherwise. > > You can also grep the IRC logs to find traces of compilation issues and > fixes with fellow users and archlinux packagers. > http://www.seeks-project.info/irclogs > > Until you or someone else shows that this issue requires code fix > at Seeks level, it will not be considered by Seeks developpers. > > Em. Hi, A contributor running Archlinux did look into the package and reported how to compile on this distribution. Here it is, for the record: ./autogen.sh || return 1 ./configure --prefix=/usr --sysconfdir=/etc --enable-httpserv-plugin --enable-image-websearch-plugin || return 1 sed -i s/-Wl,--as-needed// config.status || return 1 make || return 1 make DESTDIR=$pkgdir install || return 1 mkdir -p $pkgdir/usr/share/licenses/seeks && cp COPYING $pkgdir/usr/share/licenses/seeks || return 1 cd $pkgdir/usr/share/seeks/plugins && ln -s websearch img_websearch || return 1 Note that the compilation above requires that you compile OpenCV on your machine. Let us know if this works for you. Em. |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-23 09:58:31
|
On Wed, Feb 23, 2011 at 11:42:34AM +0700, Camille Harang wrote: > Le 23/02/2011 01:07, Bastien a écrit : > > Hi Camille, > > > > Camille Harang <mam...@yo...> writes: > > > >> I'm pretty sure that there is a Wordpress plugin for forums, if you want > >> I can do this. But maybe a Redmine forum would be better integrated with > >> bugs. > > > > If such a redmine forum is open to anyone, then yes, that may be a good > > solution : open, and integrated. > > I can help quickly on WP, but I'm not familiar with Redmine, Pablo? I don't believe we need forums on WP. Redmine supports forums and we may not even use that, but open a redmine sub-project instead. Em. |
|
From: Camille H. <mam...@yo...> - 2011-02-23 04:42:44
|
Le 23/02/2011 01:07, Bastien a écrit : > Hi Camille, > > Camille Harang <mam...@yo...> writes: > >> I'm pretty sure that there is a Wordpress plugin for forums, if you want >> I can do this. But maybe a Redmine forum would be better integrated with >> bugs. > > If such a redmine forum is open to anyone, then yes, that may be a good > solution : open, and integrated. I can help quickly on WP, but I'm not familiar with Redmine, Pablo? C. > PS: I'm old fashion and I like emails -- it's fast, open, archivable, > and easily hooked to other systems... > -- The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1 |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-22 21:08:18
|
On Tue, Feb 22, 2011 at 09:45:05PM +0100, Bastien wrote: > Emmanuel Benazera <ebe...@se...> writes: > > >> That's why I reported the problem: ./configure went fine, and > >> compilation didn't. > > > > And that's why I did give a pointer to the AUR packagers :) > > Mh.. would be better to be able to configure/compile with no error no? When a compilation problem occurs on archlinux *only* and is solved by archlinux packagers with no intervention nor request to Seeks developpers, I call it an archlinux problem, until I'm proved otherwise. You can also grep the IRC logs to find traces of compilation issues and fixes with fellow users and archlinux packagers. http://www.seeks-project.info/irclogs Until you or someone else shows that this issue requires code fix at Seeks level, it will not be considered by Seeks developpers. Em. |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-22 21:00:39
|
On Tue, Feb 22, 2011 at 09:46:08PM +0100, Bastien wrote: > Emmanuel Benazera <ebe...@se...> writes: > > >> PS: I'm old fashion and I like emails -- it's fast, open, archivable, > >> and easily hooked to other systems... > > > > IMO it doesn't matter. There may be multiple entry points, mailing > > list, forum, sub-project in redmine, before issues get reviewed and > > hit the main dev redmine. > > If there are too many entry points, it's more work for the reviewers. Let's leave that for actual bug reviewers to decide. Em. |
|
From: Bastien <bas...@wi...> - 2011-02-22 20:46:35
|
Emmanuel Benazera <ebe...@se...> writes: >> PS: I'm old fashion and I like emails -- it's fast, open, archivable, >> and easily hooked to other systems... > > IMO it doesn't matter. There may be multiple entry points, mailing > list, forum, sub-project in redmine, before issues get reviewed and > hit the main dev redmine. If there are too many entry points, it's more work for the reviewers. -- Bastien |
|
From: Bastien <bas...@wi...> - 2011-02-22 20:46:03
|
Emmanuel Benazera <ebe...@se...> writes: >> That's why I reported the problem: ./configure went fine, and >> compilation didn't. > > And that's why I did give a pointer to the AUR packagers :) Mh.. would be better to be able to configure/compile with no error no? -- Bastien |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-22 19:32:40
|
On Tue, Feb 22, 2011 at 07:11:09PM +0100, Bastien wrote: > Emmanuel Benazera <ebe...@se...> writes: > > > It is not. Seeks configure script tells you which libraries are detected. If no > > error is thrown during configuration, this means that no mandatory library is > > missing. > > That's why I reported the problem: ./configure went fine, and > compilation didn't. And that's why I did give a pointer to the AUR packagers :) Em. |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-22 19:29:15
|
On Tue, Feb 22, 2011 at 07:07:59PM +0100, Bastien wrote: > Hi Camille, > > Camille Harang <mam...@yo...> writes: > > > I'm pretty sure that there is a Wordpress plugin for forums, if you want > > I can do this. But maybe a Redmine forum would be better integrated with > > bugs. > > If such a redmine forum is open to anyone, then yes, that may be a good > solution : open, and integrated. It is supposed to be an open waiting room before an issue enters the development redmine. > PS: I'm old fashion and I like emails -- it's fast, open, archivable, > and easily hooked to other systems... IMO it doesn't matter. There may be multiple entry points, mailing list, forum, sub-project in redmine, before issues get reviewed and hit the main dev redmine. Em. |
|
From: Bastien <bas...@wi...> - 2011-02-22 18:11:36
|
Emmanuel Benazera <ebe...@se...> writes: > It is not. Seeks configure script tells you which libraries are detected. If no > error is thrown during configuration, this means that no mandatory library is > missing. That's why I reported the problem: ./configure went fine, and compilation didn't. -- Bastien |
|
From: Bastien <bas...@wi...> - 2011-02-22 18:08:33
|
Hi Camille, Camille Harang <mam...@yo...> writes: > I'm pretty sure that there is a Wordpress plugin for forums, if you want > I can do this. But maybe a Redmine forum would be better integrated with > bugs. If such a redmine forum is open to anyone, then yes, that may be a good solution : open, and integrated. PS: I'm old fashion and I like emails -- it's fast, open, archivable, and easily hooked to other systems... -- Bastien |
|
From: Emmanuel B. <ebe...@se...> - 2011-02-22 18:08:07
|
On Tue, Feb 22, 2011 at 06:53:49PM +0100, Bastien wrote: > Heya, > > Emmanuel Benazera <ebe...@se...> writes: > > > Somehow, this problem has been solved by packagers building an AUR package > > for ArchLinux: http://aur.archlinux.org/packages.php?ID=38053 (beware as this > > seems to be an old release of Seeks). > > I just failed to compile seeks from AUR, but it's my fault: not enough > disk space available (uh!) > > > To do this packagers did not request any change on Seeks side. Therefore I'd suggest > > you take a look at the work they did to solve this issue. If you believe this should > > require changes within Seeks codebase, please let us know. > > Whatever the distro, Seeks codebase should compile fine or warn the > user about missing dependancies (if that's the problem at hand with > the error log I just send.) It is not. Seeks configure script tells you which libraries are detected. If no error is thrown during configuration, this means that no mandatory library is missing. Other than that Seeks assumes that it needs to compile with as few libraries as are installed on your systems. Em. |
|
From: Bastien <bas...@wi...> - 2011-02-22 18:06:54
|
Hi, Emmanuel Benazera <ebe...@se...> writes: > Thanks for taking the time of reporting these issues. You're welcome! > After discussion with other developpers on IRC, it seems that the redmine > will remain as it is, requiring registration. The reason is that many reported > 'bugs' are not. Mostly they are configuration problems. If the redmine is just for developers, then it's okay to leave it the way it is right now. > I would favor a user space such as a forum where the problems could be > exposed. When issues are true bugs and recognized as such by > developpers, they'd make it to the redmine. A contributor suggested to > use a sub-project to the existing redmine for this purpose. This > redmine project would be open with no registration required. After > discussion / review, 'true' bugs would be simply 'moved' to the main > development redmine project. I get the spirit and it goes in the right direction: 1) it lowers the threshold for newbies to submit bug reports, 2) it encourages newbies to reply bugs reports themselves (so that they can become developers one day...) Another parameter is: make it easy for developers to *review* bugs. Then you need to find a balance between the two. My intuition is that a mailing list is a good balance, because it's easy to feed a bug tracking system with emails, it's not with forum messages. But people may have different feelings about this. > Note that as of today no user has been denied a registration to the > main development redmine project. Yes -- but if you have to register, you loose 97% of bug reports. -- Bastien |
3 messages has been excluded from this view by a project administrator.