Page "Proposals/BEP-0015" was changed by devenderbindal Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015?action=diff&version=3> Revision 3 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0015 ========================================================================= --- Proposals/BEP-0015 (version: 2) +++ Proposals/BEP-0015 (version: 3) @@ -22,13 +22,24 @@ == Motivation == -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. +1. 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 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. +2.2 Add Several filters like filter by user, milestone, open/close ticket, sort by priority asc/desc, reopened, status, assigned. +2.3 Scale it to week, month and year views. +2.4 Add Drag and drop feature for the schedule ticket onto the calendar view. +2.5 Allow the calendar to be annotated with arbitrary notes/events feature which save the notes/events in different color than ticket. +2.6 Extend it to work with various scopes, not only with milestone. +2.7 Embed it in the query and milestone pages. +2.8 If time allows, Google Calendar Plugin. + +== Rationale #rationale + +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. @@ -74,51 +85,128 @@ 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 - -<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> - -''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. - -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 . - -== 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] . > - -<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 number>&col=id&col=summary&col=status&col=priority&col=milestone", title=BEP <BEP number> ticket summary)]] -}}} +== Timeline #Timeline + +3.1 Community Bonding Period + +April 21 to April 27 (1 week): Bonding with the community, getting expert feedback, reading documentations and related plugins, exploring more on trac plugins. + +April 28 to May 4 (1 week): Learning about implementing the sub features of the given 8 features above. + +May 5 to May 11 (1 week): Learing about the best option to implement the sub features of the given 8 features above. + +May 12 to May 18 (1 week): Learning about google calendar format such that user of google calendar is allowed to subscribe to the bloodhound calendar. Some reading about the iCal Format and CALDav Format, their support and their integration. + +3.2 Coding period + +May 19 to Jun 1 (2 week): Development of the basic feature of month-long calendar view, showing the milestone due date and due date for tickets as discussed in 2.1. + +June 2 to June 8 (1 week): Development of the several filters like filter by user, milestone, open/close ticket, sort by priority asc/desc, reopened, status, assigned as discussed in 2.2. + +June 9 to June 15 7 (1 week): Development of the above feature such that it can be scaled to week, month and year views as discussed in 2.3. + +June 16 to June 22 (1 weeks): Development of the drag and drop feature for the schedule ticket onto the calendar view as discussed in 2.4. + +June 23 to June 29 (1 weeks): Development of the other notes feature which save the note in different color than ticket as discussed in 2.5. + +June 29 to July 11 (2 weeks): Development of the feature to extended to work with various scopes, not only with milestone as discussed in 2.6. + +July 12 to July 18 (1 week): Embed the calendar views in the query page and milestone pages as discussed in 2.7. + +July 19 to July 25 (1 week): Development of the Google calendar plugin as discussed in 2.8. + +July 26 to August 1 (1 week): Polishing the code , Implementing additional features or improvement as suggested by mentors. + +August 2 to August 8 (1 week): Testing and Documentation. + +August 9 to August 18 (10 days): More Testing and Evaluation. + +== Milestones #Milestones + +Sprint 1: Bonding with community, learning more about trac plugins. + +Sprint 2: Development of the basic feature of month-long calendar view, showing the milestone due date and due date for tickets and Development of the several filters like filter by user, milestone, open/close ticket, sort by priority asc/desc, reopened, status, assigned. + +Sprint 3: Development of the above feature such that it can be scaled to week, month and year views and Development of the drag and drop feature for the schedule ticket onto the calendar view and Development of the other notes feature which save the note in different color than ticket + +Sprint 4: Development of the feature to extended to work with various scopes, not only with milestone and Embed the calendar views in the query page and milestone pages. + +Sprint 5: Development of the Google calendar plugin as discussed in 2.8. + +Sprint 6: Polising the code, Implementing additional features and or improvement as suggested by mentors + +Sprint 7: Testing, Documentation and Evaluation + +== Post GSoC #PostGSoC +After GSoc too, I will like to be involved with the project and the community and will contribute more in the Bloodhound to make it the best project management software. + +== Personal Information #PersonalInformation + +Name: Devender + +University: Indian Institute of Technology (IIT), Kharagpur + +Major: Pursuing Dual Degree(B.tech+M.tech) in Computer Science and Engineering + +Expected Graduation: May 2015 + +Technical Skills: Well-versed in Pyhton, Javascript, Jquery, CSS, HTML, MySQL, Bootstap, AJAX, JSON and C. + +Linkedin Profile: http://in.linkedin.com/pub/devender-bindal/27/70b/133/ + +Email: [email protected], [email protected] + +Skype ID: devenderbindal + +Github: dev9226134 + +IRC: Devender + +== Community Interaction # Community_Interaction + +I have been in constant touch with Ryan Ollos regarding this project from the last two weeks. I have done the environment setup for the bloodhound and looked into the various tickets and made myself familiar with the bloodhound source code and the trac use. + +I have also learned about the bootstrap(10) 2.3(used various bootstrap templates), genshi edgewell. I have discussed several aspects of the proposal with my mentor and I have solved a patch for the ticket #570(11) and submit on github(12). This patch basically creates a "A bootstrap template to replace product_edit.html". + +==Availability #Availability + +I am available full time from May to first week of August as it is summer vacations at my university. + +Typical Working Hours during May to first week of August: 10 am to 1 pm, 2pm to 7 pm IST (6 days a week, amounting to 48 hours per week. If required, I can work 7 days a week too). + +My university classes begin in first week of August, but I will certainly be able to commit at-least 40 hours a week by working in the evening and weekends: + +Typical Working Hours post first Week of August: 5 pm to 8 pm, 9 pm to 11 pm IST during weekdays and 9 am to 1 pm, 2 pm to 5pm, 6pm to 9pm IST during Saturdays and Sundays (amounting to a total of 45 hours per week) + +Other Commitments: None (other than university classes mentioned above from first week of August) + +Any time in Summer where you will be away for more than 2 days: None == 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/ +(1) https://trac-hacks.org/wiki/TicketCalendarPlugin + +(2) https://trac-hacks.org/wiki/WeekPlanPlugin + +(3) http://arshaw.com/fullcalendar/ + +(4) http://trac-hacks.org/wiki/TracDragDropPlugin + +(5) http://trac-hacks.org/wiki/QueuesPlugin + +(6) http://jqueryui.com/draggable/ + +(7) http://jqueryui.com/droppable/ + +(8) http://www.w3schools.com/html/html5_draganddrop.asp + +(9) http://jqueryui.com/tabs/ + +(10) http://getbootstrap.com/2.3.2/ + +(11) https://issues.apache.org/bloodhound/ticket/570 + +(12) https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08 == Copyright #copyright -------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 .
