[Apache Bloodhound] Proposals/BEP-0013 modified
Page Proposals/BEP-0013 was changed by thimal Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013?action=diffversion=3 Revision 3 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0013 = --- Proposals/BEP-0013 (version: 2) +++ Proposals/BEP-0013 (version: 3) @@ -143,7 +143,6 @@ == Copyright #copyright -In this section all licensing issues should be meticulously exposed . Library and plugin dependencies are among the most important topics . On the other hand each BEP will be explicitly labelled with a copyright statement like shown below, so should not change that. Requests for a different copyright statement have to be posted to bloodhound-...@incubator.apache.org . For more details consult [wiki:/Proposals#what-belongs-in-a-successful-bep BEP structure explained] . Copyright © 2009-2012 The [http://www.apache.org Apache Software Foundation] [[BR]] Licensed under the [http://www.apache.org/licenses/LICENSE-2.0 Apache License, Version 2.0]. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0013' page. If it was not you, please report to .
Re: [Apache Bloodhound] #777: User restriction to only tickets they open?
#777: User restriction to only tickets they open? --+ Reporter: mbrownnyc| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: --+ Comment (by gjm): Based on what rjollos said, I just threw attached [attachment:support_desk_tickets.py this] as a possible policy. I haven't taken the time to check th:PrivateTicketsPlugin yet. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/777#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1579442 - in /bloodhound/trunk: bloodhound_dashboard/setup.py bloodhound_multiproduct/setup.py bloodhound_relations/setup.py bloodhound_search/setup.py
Author: rjollos
Date: Wed Mar 19 23:03:08 2014
New Revision: 1579442
URL: http://svn.apache.org/r1579442
Log:
0.8dev: Use the standard message extractors rather than the JS message
extractors. Refs #694.
Modified:
bloodhound/trunk/bloodhound_dashboard/setup.py
bloodhound/trunk/bloodhound_multiproduct/setup.py
bloodhound/trunk/bloodhound_relations/setup.py
bloodhound/trunk/bloodhound_search/setup.py
Modified: bloodhound/trunk/bloodhound_dashboard/setup.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_dashboard/setup.py?rev=1579442r1=1579441r2=1579442view=diff
==
--- bloodhound/trunk/bloodhound_dashboard/setup.py (original)
+++ bloodhound/trunk/bloodhound_dashboard/setup.py Wed Mar 19 23:03:08 2014
@@ -132,8 +132,8 @@ ENTRY_POINTS = r
extra = {}
try:
-from trac.util.dist import get_l10n_js_cmdclass
-cmdclass = get_l10n_js_cmdclass()
+from trac.util.dist import get_l10n_cmdclass
+cmdclass = get_l10n_cmdclass()
if cmdclass:
extra['cmdclass'] = cmdclass
extractors = [
Modified: bloodhound/trunk/bloodhound_multiproduct/setup.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/setup.py?rev=1579442r1=1579441r2=1579442view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/setup.py (original)
+++ bloodhound/trunk/bloodhound_multiproduct/setup.py Wed Mar 19 23:03:08 2014
@@ -36,8 +36,8 @@ if __name__ == '__main__':
extra = {}
try:
-from trac.util.dist import get_l10n_js_cmdclass
-cmdclass = get_l10n_js_cmdclass()
+from trac.util.dist import get_l10n_cmdclass
+cmdclass = get_l10n_cmdclass()
if cmdclass:
extra['cmdclass'] = cmdclass
extractors = [
Modified: bloodhound/trunk/bloodhound_relations/setup.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_relations/setup.py?rev=1579442r1=1579441r2=1579442view=diff
==
--- bloodhound/trunk/bloodhound_relations/setup.py (original)
+++ bloodhound/trunk/bloodhound_relations/setup.py Wed Mar 19 23:03:08 2014
@@ -115,8 +115,8 @@ ENTRY_POINTS = {
extra = {}
try:
-from trac.util.dist import get_l10n_js_cmdclass
-cmdclass = get_l10n_js_cmdclass()
+from trac.util.dist import get_l10n_cmdclass
+cmdclass = get_l10n_cmdclass()
if cmdclass:
extra['cmdclass'] = cmdclass
extractors = [
Modified: bloodhound/trunk/bloodhound_search/setup.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_search/setup.py?rev=1579442r1=1579441r2=1579442view=diff
==
--- bloodhound/trunk/bloodhound_search/setup.py (original)
+++ bloodhound/trunk/bloodhound_search/setup.py Wed Mar 19 23:03:08 2014
@@ -144,8 +144,8 @@ ENTRY_POINTS = {
extra = {}
try:
-from trac.util.dist import get_l10n_js_cmdclass
-cmdclass = get_l10n_js_cmdclass()
+from trac.util.dist import get_l10n_cmdclass
+cmdclass = get_l10n_cmdclass()
if cmdclass:
extra['cmdclass'] = cmdclass
extractors = [
Re: [Apache Bloodhound] #694: Translations scaffolding
#694: Translations scaffolding +--- Reporter: olemis | Owner: olemis Type: task | Status: closed Priority: minor | Milestone: Release 8 Component: trac core |Version: 0.7.0 Resolution: fixed | Keywords: i18n +--- Comment (by rjollos): For reference, a [http://markmail.org/thread/zvithk64nyyica3f link] to the mailing list discussion regarding the changes below. (In [1579442]) 0.8dev: Use the standard message extractors rather than the JS message extractors. Refs #694. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/694#comment:84 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=5 Revision 5 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0012 = --- Proposals/BEP-0012 (version: 4) +++ Proposals/BEP-0012 (version: 5) @@ -67,22 +67,24 @@ == Resources #resources -Provide links to useful resources related to the subject discussed. See sample text below -See WikiFormatting for more help on the markup used to write wiki pages. == References #references -List the references included in BEP body - - 1. PEP 1, PEP Purpose and Guidelines, Warsaw, Hylton - http://www.python.org/dev/peps/pep-0001/ - 2. PEP 9, Sample Plaintext PEP Template, Warsaw - http://www.python.org/dev/peps/pep-0009 - 2. PEP 12, Sample reStructuredText ''PEP'' Template, Goodger, Warsaw - http://www.python.org/dev/peps/pep-0012/ - 3. http://www.opencontent.org/openpub/ - +IRequestHandler interface +http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.IRequestHandler +IRequestFilter interface +http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.IRequestFilter +ITemplateProvider interface +http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.chrome.ITemplateProvider +Ticket Query API +http://trac.edgewall.org/wiki/TracQuery#UsingtheTicketQueryMacro +Autocomplete Users Plugin +https://trac-hacks.org/wiki/AutocompleteUsersPlugin +Keywords Suggest Plugin +http://trac-hacks.org/wiki/KeywordSuggestPlugin +Duplicate Ticket Search Plugin +https://trac-hacks.org/wiki/DuplicateTicketSearchPlugin == Copyright #copyright In this section all licensing issues should be meticulously exposed . Library and plugin dependencies are among the most important topics . On the other hand each BEP will be explicitly labelled with a copyright statement like shown below, so should not change that. Requests for a different copyright statement have to be posted to bloodhound-...@incubator.apache.org . For more details consult [wiki:/Proposals#what-belongs-in-a-successful-bep BEP structure explained] . ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0012' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=7 Revision 7 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0012 = --- Proposals/BEP-0012 (version: 6) +++ Proposals/BEP-0012 (version: 7) @@ -67,6 +67,18 @@ == Resources #resources +1. Typeahead for usernames on 'assign to' fields + +https://issues.apache.org/bloodhound/ticket/185 + +2. Search for duplicate tickets when entering summary + +https://issues.apache.org/bloodhound/ticket/765 + +3. Autocomplete keywords + +https://issues.apache.org/bloodhound/ticket/233 + == References #references ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0012' page. If it was not you, please report to .
Re: [Apache Bloodhound] #787: [patch] mysql support in bloodhound_setup.py
#787: [patch] mysql support in bloodhound_setup.py --+--- Reporter: JoKoT3 | Owner: rjollos Type: enhancement | Status: review Priority: major| Milestone: Release 8 Component: installer|Version: 0.7.0 Resolution: | Keywords: mysql --+--- Changes (by rjollos): * status: accepted = review -- Ticket URL: https://issues.apache.org/bloodhound/ticket/787#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=9 Revision 9 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0012 = --- Proposals/BEP-0012 (version: 8) +++ Proposals/BEP-0012 (version: 9) @@ -18,16 +18,7 @@ == Abstract #abstract -Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below - -This template provides a boilerplate or sample template for creating your -own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] -, this should make it easy for you to conform your own -BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. - -**Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** - -If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. +Autocompletion of ticket fields would be a great feature for the Bloodhound, as it saves user’s search time, catch a user’s mistake and allows repeating a favorite search. Typing the whole search word makes finding information slower and requires more typing and also increases the chance of misspelling that leads to incorrect search results which degrades the interface usability. == Motivation == ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0012' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=10 Revision 10 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0012 = --- Proposals/BEP-0012 (version: 9) +++ Proposals/BEP-0012 (version: 10) @@ -20,21 +20,46 @@ Autocompletion of ticket fields would be a great feature for the Bloodhound, as it saves user’s search time, catch a user’s mistake and allows repeating a favorite search. Typing the whole search word makes finding information slower and requires more typing and also increases the chance of misspelling that leads to incorrect search results which degrades the interface usability. -== Motivation == - -The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. == Proposal #proposal -The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. +The implementation of the project can be splitted into three distinct parts, the keyword and user suggestion components, and duplicate ticket search component. +The keyword suggestion component of the project will suggest entries that are used in existing tickets while user suggestion component will autocomplete the Owner and Cc fields from a list of valid users. Pressing the down key will be sufficient to display suggested keywords in an alphabetical list that the user can scroll through. Instead of an alphabetical order, popularity of entries would be used to order the suggested keywords and also matching would not be case sensitive to give more flexibility to the user in typing. + +The keyword and user suggestion component of the project will be coded using jQuery (JavaScript library). Since most of Bloodhound’s design is done using the Twitter Bootstrap framework, the autocompletion part of the code can also be designed using Twitter Bootstrap Typeahead plugin. + +Suggestions can be stored into the source array and can be retrieved on page load. However, this is really inefficient when there are thousands of keywords/usernames since user needs to wait for a long time for the page to be displayed. Alternative solution to this would be storing the suggestions in dynamically retrieved server-side (i.e. database), which will provide faster and more efficient results. More advanced approach would be using the dynamically retrieved server-side with a JSON format (JavaScript Object Notation) for human-readable data interchange between client and server. + +Using dynamically retrieved server-side for retrieving the suggestions will be faster. However, there will be some latency in retrieving the possible keywords/usernames. In order to overcome the latency, AJAX (Asynchronous JavaScript And XML) would be used to leave client active while the server retrieves the keywords/usernames. + +The duplicate ticket search component of the project will assist the user to search for the duplicate tickets when entering a new ticket’s summary. One of the possible solution would be determining the duplicates by searching the summary of existing tickets whereas searching the ticket description would be better and powerful solution. + + +The duplicate ticket search part of the project will be coded using +jQuery and AJAX. Since most of Bloodhound’s design has been done using the Twitter Bootstrap framework, this part of the code can also be designed using Twitter Bootstrap. First, the duplicate search feature will be implemented to work with the Trac Search API then it will be manipulated to work with the BloodhoundSearchPlugin since it is much more powerful than Trac Search API. However, the ticket Query API would be another solution to implement duplicate search feature rather than interacting with Search components. The ticket Query API has support for searching ticket summaries and descriptions that contain words and phrases. + +We are going to use TicketQuery wiki macro which listing tickets that match certain criteria. Listing tickets according to ticket ID next to the summary, with each ticket on a separate line is one of the format parameters that
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay
Diff URL:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=11
Revision 11
Changes:
---8--8--8--8--8--8--8--8
Index: Proposals/BEP-0012
=
--- Proposals/BEP-0012 (version: 10)
+++ Proposals/BEP-0012 (version: 11)
@@ -61,25 +61,29 @@
Therefore, each of these features can be added to the BloodhoundThemePlugin as
an individual component. This will work well since the client-side
functionality (i.e. the JavaScript parts) can be added directly in each
individual feature and the server-side request handling can also be handled in
individual components within the BloodhoundThemePlugin. Moreover, the user will
able to enable/disable each feature since they are implemented individually
into the BloodhoundThemePlugin.
-== How to Use This Template #howto
+== Implementation
-BEPs may include further sections. This is an example.
+Timeframe
-Quick edits will consist in following the instructions inside angle brackets
(i.e. ) . That should be everything needed to write new BEPs. To be
more informed about advanced considerations please read the [wiki:/Proposals
general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting
WikiFormatting BEP guidelines] . If there is no point in including one of the
sections in this document then feel free to remove it.
+May 19 – June 8
+• Implement the Keyword Suggest Component for BloodhoundThemePlugin.
-== Backwards Compatibility #backwards-compatibility
+June 8 – July 8
+• Implement the Autocomplete Users Component for BloodhoundThemePlugin.
+• Research the Trac Query API
-All BEPs that introduce backwards incompatibilities must include a section
describing these incompatibilities and their severity. The ''BEP'' must explain
how to deal with these incompatibilities. ''BEP'' submissions without a
sufficient backwards compatibility treatise may be rejected outright.
+July 3
+• Midterm Evaluation
-== Reference Implementation #reference-implementation
+July 8 – August 8
+• Implement the duplicate ticket feature to work with the ticket Query API
+• Add support for the multiproduct API
- The reference implementation **must** be completed before any ''BEP'' is
given status **Final**, but it need not be completed before the ''BEP'' is
accepted. It is better to finish the specification and rationale first and
reach consensus on it before writing code. The final implementation **must**
include test code and documentation appropriate for either the wiki pages in
''Bloodhound'' users guide or an specific wiki page in the
[http://issues.apache.org/bloodhound issue tracker] .
+August 8 – August 16
+• Refactor code, finish test and documentation
-In order to list tickets related to a given proposal edit sample text
provided below by including the appropriate **BEP number**. Target tickets
have to be tagged with `bep-BEP number` keyword. Do not forget to remove
curly braces so that the tickets list will be actually rendered.
-
-{{{
-[[Widget(TicketQuery, query=keywords=~bep-BEP
numbercol=idcol=summarycol=statuscol=prioritycol=milestone, title=BEP
BEP number ticket summary)]]
-}}}
+August 18
+• Final Evaluation
== Resources #resources
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0012' page.
If it was not you, please report to .
Re: [Apache Bloodhound] #792: Invalid search result after moving ticket to another product
#792: Invalid search result after moving ticket to another product ---+-- Reporter: olemis| Owner: nobody Type: defect| Status: new Priority: critical | Milestone: next 0.x Component: search|Version: 0.8.0dev Resolution:| Keywords: ticket batch modify, product ---+-- Changes (by rjollos): * milestone: = next 0.x -- Ticket URL: https://issues.apache.org/bloodhound/ticket/792#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1579492 - /bloodhound/trunk/bloodhound_relations/bhrelations/validation.py
Author: rjollos Date: Thu Mar 20 01:03:15 2014 New Revision: 1579492 URL: http://svn.apache.org/r1579492 Log: 0.8dev: Fixed documentation for `BlockerValidator`. Modified: bloodhound/trunk/bloodhound_relations/bhrelations/validation.py Modified: bloodhound/trunk/bloodhound_relations/bhrelations/validation.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_relations/bhrelations/validation.py?rev=1579492r1=1579491r2=1579492view=diff == --- bloodhound/trunk/bloodhound_relations/bhrelations/validation.py (original) +++ bloodhound/trunk/bloodhound_relations/bhrelations/validation.py Thu Mar 20 01:03:15 2014 @@ -219,8 +219,7 @@ class ReferencesOlderValidator(Validator class BlockerValidator(Validator): def validate(self, relation): -If a path exists from relation's destination to its source, - adding the relation will create a cycle. +Prevents adding a cyclical blocker relation. rls = RelationsSystem(self.env) if not rls.is_blocker(relation.type):
