Hi Devender, You may use BEP-0015: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
I will take a look at your proposal and should be on IRC 2 hours from now. On Thu, Mar 20, 2014 at 2:40 AM, Devender <[email protected]> wrote: > Hi Ryan, > > I have submitted my proposal to GSOC 2014 website(1). Please provide > feedback. I want to submit on the wiki page, please create a page. > > (1) > https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/devenderbindal/5629499534213120 > > > On Thu, Mar 20, 2014 at 8:35 AM, Devender <[email protected]>wrote: > >> In previous mail, I forgot to direct to [email protected]. So >> >> >> On Thu, Mar 20, 2014 at 8:26 AM, Devender <[email protected]>wrote: >> >>> Hi Ryan, >>> >>> I have submit a patch for ticket 570.(1) Please provide your feedback >>> about it. I have a doubt about this patch I want to discuss on IRC. Other >>> than that I have to discuss some points about the proposal. What time can I >>> catch you on IRC? >>> >>> >>> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08 >>> >>> >>> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <[email protected]>wrote: >>> >>>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <[email protected]>wrote: >>>> >>>>> Hi Ryan, >>>>> >>>>> I have been working on the proposal. I have mentioned some points >>>>> about the given 6 features. Please provide your feedback on point given >>>>> below, So that I can come with the concise sub-feature set in these 6 >>>>> features: >>>>> >>>>> 1.To add basic feature of a month-long calendar view of a milestone, >>>>> showing the milestone due date and due date for tickets >>>>> As given in the ticket #766 (1) we can use the modified trac ticket >>>>> calender plugin (2), I have installed and tried this plugin. >>>>> or >>>>> we can develop the calender view from scratch using basic web >>>>> development and combine it with the bootstrap to make it look beautiful. >>>>> >>>>> Also we can also extend the calender view to google calender as a >>>>> different plugin in addition to the above plugin (4) but it will be >>>>> requiring the internet and it is not open source. >>>>> >>>> >>>> Utilizing one of the existing plugins as a starting point seems like >>>> the best choice. If you need to significantly modify it or rewrite parts of >>>> the plugin later to fit your needs, then the project can progress in that >>>> direction. >>>> >>>> With regard to Google Calendar, I suppose it would be possible to embed >>>> a Google Calendar view (or another similar 3rd party calendar into >>>> Bloodhound). What I would consider doing instead though, is allowing a user >>>> of Google Calendar to subscribe to the Bloodhound calendar. This would use >>>> the iCAL or CALDav format. Google Calendar at least supports the iCAL >>>> format, and you can subscribe to any calendar that is provided in that >>>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this >>>> format until Gary mentioned it a few weeks back, so we'd need to >>>> investigate what use cases it could support). >>>> >>>> You might want to consider the "calendar subscription" feature to be >>>> implemented later in the project, if time allows. It doesn't have to be >>>> part of the primary deliverable that you are aiming for, but you could >>>> suggest it as an extra feature that will be added if time allows. >>>> >>>> >>>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the calendar >>>>> view. >>>>> First I can make the tickets "div draggable true" and then I can add >>>>> the basic javascript function (7) i.e what to drag, where to drop and do >>>>> the drop. >>>>> or >>>>> I can use jquery plugin (5). >>>>> >>>> >>>> This sounds good. There are some examples on trac-hacks that you can >>>> look at to see how the drag and drop functionality might be implemented. >>>> For example, >>>> http://trac-hacks.org/wiki/TracDragDropPlugin >>>> http://trac-hacks.org/wiki/QueuesPlugin >>>> >>>> >>>>> 3. To Scale the view: week, month, year. >>>>> There is another library mentioned in the ticket #766 as trac week >>>>> plan plugin (3), I have installed and tried this plugin as well. 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. >>>>> >>>>> 4. To add Filters for the calendar view. For example: filter by >>>>> user, milestone, open/closed tickets. >>>>> trac calender plugin also contain several filter which are required or >>>>> If created alone, then also these filters can be done by simple database >>>>> queries. >>>>> >>>>> 5. To Embed the calendar views in the query page and milestone pages. >>>>> I can put a button in query and milestone page and when user click the >>>>> button >>>>> this will add the calender to the right side to the existing page by >>>>> using jquery. or It will go to the calender page or I can add some >>>>> indexing based on the jquery tab (6). >>>>> >>>> >>>> I think you have the right idea. Since the milestone view page >>>> currently displays a table of tickets - the result of a ticket query for >>>> the milestone - another possibility is to allow the user to toggle between >>>> the ticket query table and calendar views. >>>> >>>> >>>>> 6. Allow the calendar to be annotated with arbitrary notes/events >>>>> that do not represent tickets. >>>>> a new class can be added to the existing trac plugins to support any >>>>> note feature, >>>>> these note can be off different color from ticket/milestones. >>>>> >>>> >>>> You seem to have a good grasp of the project. If you want to discuss >>>> details further, feel free to reply, or else you can catch me on IRC. I'll >>>> try to be frequently available on IRC over the next several days. >>>> >>> >>> Hi Devender, >> >> I copied over the file you'll need to start with in r1578595 and r1578599 >> (1, 2). Now we have bloodhound_theme/bhtheme/templates/bh_product_edit.html >> which needs to be modified for Bootstrap markup. This consists of basic >> things like adding the "btn" class to inputs of type "submit", and adding >> the "row" and "span" classes to divs. To learn the markup, you can compare >> templates between Trac and Bloodhound. For example, you can diff >> bloodhound_theme/bhtheme/templates/bh_report_list.html and >> trac/trac/ticket/templates/report_list.html. >> >> The BloodhoundTheme templates are not perfect. Please let us know if you >> spot any inconsistencies or issues on certain platforms or devices. >> >> You can take a look at the recent messages sent to Thimal (3) to get >> additional pointers. He worked on the template for the Roadmap page, which >> was committed over the weekend (4). The changes you'll need to make are >> similar to those made for the Roadmap. Again, it would be good to look at >> the diffs. You can also view the diffs through the links I sent to Apache >> ViewVC (which aren't the nicest to view), through your client-side tool or >> on GitHub (5). For example, the complementary link to (4) on GitHub is (6). >> >> (1) http://svn.apache.org/viewvc?view=revision&revision=r1578595 >> (2) http://svn.apache.org/viewvc?view=revision&revision=r1578599 >> (3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2 >> (4) http://svn.apache.org/viewvc?view=revision&revision=r1578223 >> (5) https://github.com/apache/bloodhound/commits/trunk >> (6) >> https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8 >> >> >
