community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko Čibej (JIRA) <>
Subject [jira] [Updated] (COMDEV-84) [GSoC] Integrate Subversion's svnpubsub client into Apache Bloodhound
Date Sat, 23 Mar 2013 14:37:15 GMT


Branko Čibej updated COMDEV-84:

    Labels: bloodhound gsoc2013  (was: gsoc2013)
> [GSoC] Integrate Subversion's svnpubsub client into Apache Bloodhound
> ---------------------------------------------------------------------
>                 Key: COMDEV-84
>                 URL:
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Branko Čibej
>              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:
> One drawback inherited from Trac is that it cannot track changes in a Subversion repository
that it does not have local access to ("local" meaning that the Subversion repository has
to reside on a volume accessible to the Bloodhound server).
> Proposed solution:
> In its next release, Apache Subversion will include a publish/subscribe framework called
svnpubsub, which is intended to solve this kind of problem; see
> The goal of this task is to integrate svnpubsub into Apache Bloodhound so that it can
act as a svnpubsub client, allowing it to receive change notifications from remote Subversion
> Skills needed:
> Both Bloodhound (and Trac) and svnpubsub 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:

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