[Apache Bloodhound] Proposals/BEP-0008 modified

[Apache Bloodhound <de...@bloodhound.apache.org>]

Page "Proposals/BEP-0008" was changed by huaxiang
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diff&version=2>
Revision 2
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0008
=========================================================================
--- Proposals/BEP-0008 (version: 1)
+++ Proposals/BEP-0008 (version: 2)
@@ -1,85 +1,64 @@
 -placeholder for Hua's proposal-
-= BEP <BEP number> : <BEP title> #overview
+= BEP-0008 : Add time series reports #overview
 
 [[PageOutline]]
 
-|| '''BEP''' || <BEP number> ||
-|| '''Title''' || <BEP title> ||
-|| '''Version''' || <leave blank> ||
-|| '''Last-Modified''' || <leave blank> ||
-|| '''Author''' || Author With Email <us...@dom.ain>, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) ||
+|| '''BEP''' || BEP-0008 ||
+|| '''Title''' || Add time series reports ||
+|| '''Version''' || ||
+|| '''Last-Modified''' ||  ||
+|| '''Author''' || Hua Xiang <hu...@gmail.com> ||
 || '''Status''' || Draft ||
-|| '''Type''' || <BEP type (see [wiki:/Proposals#bep-types BEP types explained])> ||
+|| '''Type''' ||  ||
 || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] ||
-|| '''Created''' || <leave blank> ||
-|| '''Post-History''' || <leave blank> ||
+|| '''Created''' ||  ||
+|| '''Post-History''' ||  ||
 
 ----
 
 == Abstract #abstract
+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. The current reports functionality of Bloodhound doesn't serve these cases very well at the moment. Users also can't query information as it was at a given date. For solving this problem, the changes over time must be recorded. Data mining tools should also be involved in order to provide some patterns, generate time series reports, help user get better understanding of the reports and make decisions.
 
-<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].
 
 == 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. >
+The current “Reports” tool of bloodhound can provide a list based on custom queries (https://issues.apache.org/bloodhound/report). The historical statuses of tickets and the time point of such information, however, cannot be illustrated. These data are helpful for user to determine the hottest topics, allocate resources, evaluate performance etc.
+
 
 == 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'').. >
+To help the Bloodhound developers find the hidden information easily and make correct decisions. For example, for a particular type of tickets, the longer the time of changing status from 'assigned' to 'closed', the higher the difficulty level of solving. Therefore, the developers can allocate more resources for such type of tickets.
 
-== Rationale #rationale
+To help users to track the process of their own tickets, e.g., a message/email sent to the user once the status of the ticket was changed.
 
-<The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue trackers or ''Trac'' hacks . The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Take a look at sample rationale below>
+To help developers and users get better understanding of the reports and make decisions.
 
-''BEP'' submissions come in a wide variety of forms, not all adhering to the format guidelines set forth below. Use this template, in conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines], to ensure that your ''BEP'' submission is easy to read and understand.
+Proposed solution:
+· Take snaps to keep the changes of statuses and the time those occurred.
+· Use data mining tools to find some patterns, generate time series reports.
 
-This template allows to create BEPs and is very similar to [http://www.python.org/dev/peps/pep-0012 PEP 12] . However it has been optimized by moving long explanations to the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If you are interested take a look at the  [?action=diff&old_version=1 differences]. The goal is to redact new BEPs just by following in-line instructions between angle brackets (i.e. **<** **>**) . Even if this will allow to write BEPs faster , it is highly recommended to read the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] at least once in your lifetime to be aware of good practices and expected style rules . 
+ == Rationale #rationale
 
-== How to Use This Template #howto
-
-<BEPs may include further sections. This is an example.>
-
-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.
-
-== Backwards Compatibility #backwards-compatibility
-
-<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. >
-
-== Reference Implementation #reference-implementation
-
-< 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] . >
 
 == Resources #resources
+1. Database Schema
+http://trac.edgewall.org/wiki/TracDev/DatabaseSchema
 
-<Provide links to useful resources related to the subject discussed. See sample text below>
+2. Database
+http://trac.edgewall.org/browser/trunk/trac/db_default.py
 
-See WikiFormatting for more help on the markup used to write wiki pages.
+3. Ticket system:
+http://trac.edgewall.org/wiki/TracDev/DatabaseSchema/TicketSystem#Tableticket_change
 
 == References #references
+http://trac.edgewall.org/browser/trunk/trac/db_default.py
 
-<List the references included in BEP body>
+http://trac.edgewall.org/wiki/TracDev/DatabaseSchema
 
-  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/
+http://trac.edgewall.org/wiki/TracDev/DatabaseSchema/TicketSystem#Tableticket_change
 
 == 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-dev@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-0008>
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-0008' page.
If it was not you, please report to .