[Apache Bloodhound] Proposals/BEP-0015 modified

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

Page "Proposals/BEP-0015" was changed by devenderbindal
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015?action=diff&version=2>
Revision 2
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0015
=========================================================================
--- Proposals/BEP-0015 (version: 1)
+++ Proposals/BEP-0015 (version: 2)
@@ -1,15 +1,15 @@
 
-= BEP <BEP number> : <BEP title> #overview
+= BEP 0015 : Dynamic calendar and scheduling tools for the Bloodhound issue tracker
 
 [[PageOutline]]
 
-|| '''BEP''' || <BEP number> ||
-|| '''Title''' || <BEP title> ||
+|| '''BEP''' || 15 ||
+|| '''Title''' || Dynamic calendar and scheduling tools for the Bloodhound issue tracker ||
 || '''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]) ||
-|| '''Status''' || Draft ||
-|| '''Type''' || <BEP type (see [wiki:/Proposals#bep-types BEP types explained])> ||
+|| '''Author''' || Devender <de...@gmail.com>, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) ||
+|| '''Status''' || Active ||
+|| '''Type''' || Standards Track||
 || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] ||
 || '''Created''' || <leave blank> ||
 || '''Post-History''' || <leave blank> ||
@@ -18,24 +18,61 @@
 
 == 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].
+Enhance Bloodhound by adding calendar view containing the basic feature of week, month and year calendar view, drag and drop feature for the schedule ticket onto the calendar view, other notes feature, showing the due date for tickets and milestone, having several filters,extended to work with various scopes not only with milestone, embed the calendar view in the query page and milestone pages and if time allows, add the Google Calendar plugin.
 
 == 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. >
+After adding this calendar views. By this user can see the schedule of upcoming work and can also schedule work by interacting with it. It will make the user task easy.
 
 == 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'').. >
+2. Important Features, Approach and Detailed Description
+
+2.1 Add Basic feature of month-long calendar view, showing the due date for milestone and tickets. 
+
+This will initially start by using the trac ticket calender plugin(1) which contains the basic month view. It also contains the list view which can also be utilized. It is in python, so can easily be integrated in bloodhound.
+
+2.2 Add Several filters like filter by user, milestone, open/close ticket, sort by priority asc/desc, reopened, status, assigned.
+
+This trac ticket calender plugin have all these filters and additional filters can also be created by adding simple database queries.
+
+2.3 Scale it to week, month and year views.
+
+This feature will initially start by using the trac week plan plugin(2). I can extend this plugin to the month calender as sub plugin and I can create the year plugin similarly as well. So, It will be like calender view containing three view: year, month, and week with month view as default. This plugin uses the jquery plugin named FullCalender(3).
+
+2.4 Add Drag and drop feature for the schedule ticket onto the calendar view.
+
+Various approaches can be used:
+
+2.4.1 Trac plugin
+
+This feature can be developed using the tracdragdrop plugin(4) and Queueplugin(5).
+
+2.4.2 Jquery
+
+Various jquery plugin are available such as drag(6) and drop(7). Other than that Full Calender (3) also provides drag and drop functionality. 
+
+2.4.3 Javascript approach
+
+This feature can be implemented by using the basic javascript. Make the draggable div to true and then write what to drag, where to drag and do the drag functionality(8).
+
+2.5 Allow the calendar to be annotated with arbitrary notes/events feature which save the notes/events in different color than ticket.
+
+A new class will be added to the existing trac ticket calendar plugins to support any note feature, these note can be off different color from ticket/milestones.
+
+2.6 Extend it to work with various scopes, not only with milestone.
+
+The above trac ticket calendar plugin will be changed such it can be extended by other scopes.
+
+2.7 Embed it in the query and milestone pages.
+
+The milestone view page currently displays a table of tickets- the result of a ticket query for the milestone.
+
+So we can implement such that it will allow the user to toggle between the ticket query table and calendar views or we can use some indexing between the calender view and the ticket query(9). 
+
+2.8 If time allows, Google Calendar Plugin.
+
+It will allow a user of Google Calendar to subscribe to the Bloodhound calendar. Google calendar uses the iCAL format. Any other users can also subscribe to it provided there calendar uses the iCAL format.
 
 == Rationale #rationale
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015>
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-0015' page.
If it was not you, please report to .