community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Dreimann (JIRA)" <>
Subject [jira] [Resolved] (COMDEV-91) [GSoC] Bloodhound: Embeddable tickets / objects
Date Tue, 18 Jun 2013 10:43:22 GMT


Joachim Dreimann resolved COMDEV-91.

    Resolution: Fixed

We have accepted Antonia as a student to work on this proposal.
> [GSoC] Bloodhound: Embeddable tickets / objects
> -----------------------------------------------
>                 Key: COMDEV-91
>                 URL:
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Joachim Dreimann
>              Labels: bloodhound, gsoc2013
> Apache Bloodhound is a software development collaboration tool, including issue tracking,
wiki and repository browsing (see: Bloodhound extends Trac
( with multiple product support, advanced search functionality,
ticket relations, a simpler installer and sleeker user interface. Apache Bloodhound recently
graduated from the Apache Incubator as a stand-alone Apache project. 
> Problem: 
> Referring to objects within Bloodhound, such as tickets, milestones, versions or products
is only possible via a "dumb" link on external websites/services. This requires users to click
each link individually to find out more, which isn't very engaging for users. Since the states
of those objects generally change over time and often quickly, static text describing them
is also quickly outdated.
> Proposed solution: 
> Create embeddable, interactive objects that show the current status of objects (like
tickets, versions), like Kickstarter does with its Widgets (
), or Twitter does with tweets ( ).
> Skills needed: 
> Bloodhound and Trac are written in Python, so a moderate dose of Python programing skills
are required. 
> References: 
> Link to the original issue: 
> More GSoC-related tasks for Bloodhound: 
> Guidelines for contributing to Apache Bloodhound: 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message