Re: [Apache Bloodhound] #479: Embeddable tickets / objects
#479: Embeddable tickets / objects --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Description changed by jdreimann: Old description: Many big open source projects have issue trackers built on trac, the same technology Bloodhound is built on. We're hoping to make it easier for people to refer to objects like tickets, milestones, versions or whole products in a meaningful way. That could be done by providing the ability for users to refer to them as embeddable, interactive objects, like is done with [http://support.google.com/youtube/bin/answer.py?hl=en-GBanswer=171780 youtube videos] and [https://dev.twitter.com/docs/embedded-tweets tweets]. New description: Many big open source projects have issue trackers built on trac, the same technology Bloodhound is built on. We're hoping to make it easier for people to refer to objects like tickets, milestones, versions or whole products in a meaningful way. That could be done by providing the ability for users to refer to them as embeddable, interactive objects, like is done with [http://www.kickstarter.com/projects/doublefine/double-fine- adventure/widget Kickstarter widgets], [http://support.google.com/youtube/bin/answer.py?hl=en-GBanswer=171780 youtube videos] and [https://dev.twitter.com/docs/embedded-tweets tweets]. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/479#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #481: Live syntax highlighting
#481: Live syntax highlighting --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-92 Related GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/481#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Batch modify: #152, #478, #479, #480, #481, #483, #486
Batch modification to #152, #478, #479, #480, #481, #483, #486 by jdreimann: keywords to gsoc2013submitted Comment: Tagging submitted tasks -- Tickets URL: https://issues.apache.org/bloodhound/query?id=152%2C478%2C479%2C480%2C481%2C483%2C486 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin + Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc + Changes (by andrej): * owner: = nobody * keywords: = gsoc * component: = dashboard Old description: New description: Bloodhound Search plugin architecture supports different search backends. Current plugin implementation supports Whoosh search backend. Apache Solr can be used as alternative search backend for Bloodhound Search when requirements are reliability, scalability and fault tolerance. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin + Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc + Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-93 Relevant GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #489: Time series reports
#489: Time series reports -+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Keywords: gsoc | -+ In many organisations reports are tracking changes over time or and/or are prepared in a regular interval to capture information at a fixed point in time. Our reports functionality doesn't serve these cases very well at the moment. Users also can't query information as it was at a given date. One proposed solution to this to enhance reports to be scheduled and represent data in relation to time in better ways, as well as changes over time. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-94 Related GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Changes (by jdreimann): * keywords: gsoc = gsoc, gsoc2013submitted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin +- Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc, gsoc2013submitted +- Changes (by jdreimann): * keywords: gsoc = gsoc, gsoc2013submitted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #485: Topic-based pub/sub for IResourceChangeListener
#485: Topic-based pub/sub for IResourceChangeListener -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: gsoc gsoc2013submitted Resolution: | IResourceChangeListener performance -+- Changes (by jdreimann): * keywords: gsoc IResourceChangeListener performance = gsoc gsoc2013submitted IResourceChangeListener performance Old description: Resource listeners often will watch events for a limited , well-known set of resource realms (e.g. `ticket` + `attachment` ) . The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based] . It behaves in `O(r * l)` order of magnitude . This might lead to a lot of extra (unnecessary) overhead . A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]) , thus turning the dispatch algorithm into `O(l)` , at least when it is a ok to do so ;) PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy . New description: Resource listeners often will watch events for a limited, well-known set of resource realms (e.g. `ticket` + `attachment` ). The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based]. It behaves in `O(r * l)` order of magnitude. This might lead to a lot of extra (unnecessary) overhead. A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]), thus turning the dispatch algorithm into `O(l)` , at least when it is a ok to do so ;) PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy. -- Comment: [https://issues.apache.org/jira/browse/COMDEV-95 Relevant GSoC submission] in COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/485#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Comment (by olemis): jftr . somebody in my team is currently working on something related to this . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Comment (by rjollos): I think this would be a good feature. For reference, the only plugin I know of on trac-hacks that relates to solving this problem is the [th:SnapshotPlugin]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] New user registration: miron
New user registration for user miron -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
