Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Fix
Description
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:
Trac (and therefore Bloodhound) effectively only supports Subversion repositories that are on the same server as the Trac instance. More information about why this is and ways to get around this are discussed in http://trac.edgewall.org/ticket/493. A related problem 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:
Task 1: In its next release, Apache Subversion will include a publish/subscribe framework called svnpubsub, which is intended to solve this kind of problem; see http://s.apache.org/svnpubsubrepo . 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 repositories.
Task 2: Write a new repository connector for Apache Bloodhound (and Trac) that talks to remote Subversion repositories. Alternatively: Enhance remote svn plugin (http://www.meadowy.org/~gotoh/hg/remote-svn-plugin/) to integrate it with Bloodhound (and latest Trac), multi-repository APIs and other features included in Trac core since its last change.
Skills needed:
Bloodhound, Trac and svnpubsub are written in Python, so a moderate dose of Python programing skills are required. Familiarity with Subversion internals and its Python bindings would be a benefit.
References:
Link to the original issues:
https://issues.apache.org/bloodhound/ticket/89
https://issues.apache.org/bloodhound/ticket/483
https://issues.apache.org/bloodhound/ticket/478
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