community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan J Ollos (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COMDEV-112) Dynamic calendar and scheduling tools for the Bloodhound issue tracker
Date Mon, 24 Feb 2014 23:24:23 GMT

     [ https://issues.apache.org/jira/browse/COMDEV-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ryan J Ollos updated COMDEV-112:
--------------------------------

    Labels: Bootstrap HTML JavaScript Python bloodhound gsco2014 gsoc2014 jQuery  (was: Bootstrap
HTML JavaScript Python bloodhound gsco2014 jQuery)

> Dynamic calendar and scheduling tools for the Bloodhound issue tracker
> ----------------------------------------------------------------------
>
>                 Key: COMDEV-112
>                 URL: https://issues.apache.org/jira/browse/COMDEV-112
>             Project: Community Development
>          Issue Type: New Feature
>          Components: Comdev
>            Reporter: Ryan J Ollos
>              Labels: Bootstrap, HTML, JavaScript, Python, bloodhound, gsco2014, gsoc2014,
jQuery
>
> Apache Bloodhound is a software development collaboration tool, including issue tracking,
wiki and repository browsing (see: http://bloodhound.apache.org). Bloodhound extends Trac
(http://trac.edgewall.org/) with multiple product support, advanced search functionality,
ticket relations, a simpler installer and sleeker user interface. 
> Problem: 
> Bloodhound should provide calendar views so that the user can see the schedule of upcoming
work. User should be able to schedule work by interacting with the calendar.
> Proposed solution: 
> Enhance Bloodhound with the basic feature of a month-long calendar view of a milestone,
showing the milestone due date and due date for tickets. Once the basic calendar view is established,
features that could be incrementally added, in no particular order:
>  * Allow the calendar to work at various scopes, rather than simply scoping it to a single
milestone.
>  * Filters for the calendar view. For example: filter by user, milestone, open/closed
tickets.
>  * Allow tickets to be scheduled by drag 'n drop onto the calendar view.
>  * Allow the calendar to be annotated with arbitrary notes/events that do not represent
tickets.
>  * Scale the view: week, month, year.
>  * Embed the calendar views in the query page and milestone pages.
> The dynamic features will be implemented in JavaScript, using jQuery and Bootstrap. Given
the general nature of the problem, the developer would need to work with the community to
come up with a concise feature set, by developing a Bloodhound Enhancement Proposal. Significant
room for creativity exists in solving the problem.
> Skills needed: 
> Bloodhound and Trac are written in Python, HTML and JavaScript, so a moderate dose of
these programming skills are required. 
> References: 
> Links to the original issues: 
> https://issues.apache.org/bloodhound/ticket/766
> More GSoC-related tasks for Bloodhound: 
> https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc 
> Guidelines for contributing to Apache Bloodhound: 
> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message