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] [Updated] (COMDEV-84) [GSoC] Integrate Subversion's svnpubsub client into Apache Bloodhound
Date Sun, 24 Mar 2013 08:51:15 GMT

     [ https://issues.apache.org/jira/browse/COMDEV-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Branko Čibej updated COMDEV-84:
-------------------------------

    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:

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 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.

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:

    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

  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:

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 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.

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:

    https://issues.apache.org/bloodhound/ticket/478

More GSoC-related tasks for Bloodhound:

    https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc

    
> [GSoC] Integrate Subversion's svnpubsub client into Apache Bloodhound
> ---------------------------------------------------------------------
>
>                 Key: COMDEV-84
>                 URL: https://issues.apache.org/jira/browse/COMDEV-84
>             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:
> 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 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.
> 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:
>     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

--
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