You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by "Branko Čibej (JIRA)" <ji...@apache.org> on 2013/03/24 09:49:16 UTC
[jira] [Updated] (COMDEV-86) [GSoC] Add support for browsing remote
Subversion repositories to Apache Bloodhound
[ https://issues.apache.org/jira/browse/COMDEV-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Branko Čibej updated COMDEV-86:
-------------------------------
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.
Proposed solution:
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 and Trac are written in Python, so a moderate dose of Python programing skills are required. Familiarity with Subversion internals and its Python bindings is also useful.
References:
Link to the original issues:
https://issues.apache.org/bloodhound/ticket/89
https://issues.apache.org/bloodhound/ticket/483
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
was:
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.
Proposed solution:
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 and Trac are written in Python, so a moderate dose of Python programing skills are required. Familiarity with Subversion internals and its Python bindings is also useful.
References:
Link to the original issues:
https://issues.apache.org/bloodhound/ticket/89
https://issues.apache.org/bloodhound/ticket/483
More GSoC-related tasks for Bloodhound:
https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc
> [GSoC] Add support for browsing remote Subversion repositories to Apache Bloodhound
> -----------------------------------------------------------------------------------
>
> Key: COMDEV-86
> URL: https://issues.apache.org/jira/browse/COMDEV-86
> 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: 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.
> Proposed solution:
> 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 and Trac are written in Python, so a moderate dose of Python programing skills are required. Familiarity with Subversion internals and its Python bindings is also useful.
> References:
> Link to the original issues:
> https://issues.apache.org/bloodhound/ticket/89
> https://issues.apache.org/bloodhound/ticket/483
> 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