community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej (JIRA) <j...@apache.org>
Subject [jira] [Commented] (COMDEV-91) [GSoC] Embeddable tickets / objects
Date Tue, 16 Apr 2013 15:21:16 GMT

    [ https://issues.apache.org/jira/browse/COMDEV-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632921#comment-13632921
] 

Branko ─îibej commented on COMDEV-91:
------------------------------------

HI Antonia,

The best way to start is to subscribe to the Bloodhound development mailing list (send an
empty mail to: dev-subscribe@bloodhound.apache.org), then send an introductory mail (can be
just a copy of your comment here) to dev@bloodhound.apache.org. This is where most of the
discussions on Bloodhound development take place, and this is where we expect GSoC candidates
to discuss the project proposals.

By the way, we don't track issues in Jira (of course!), you can find links to the original
tickets in the project description.

Oh, and since you're at Sheffield University -- a couple Bloodhound developers are right next
door to you at WANdisco. :)
                
> [GSoC] Embeddable tickets / objects
> -----------------------------------
>
>                 Key: COMDEV-91
>                 URL: https://issues.apache.org/jira/browse/COMDEV-91
>             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: 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. 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 ( http://www.kickstarter.com/projects/doublefine/double-fine-adventure/widget
), or Twitter does with tweets ( https://dev.twitter.com/docs/embedded-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: 
>     https://issues.apache.org/bloodhound/ticket/479
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message