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-85) [GSoC] Twitter card integration (and other social tags) in Apache Bloodhound
Date Sun, 24 Mar 2013 08:49:16 GMT

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

Branko Čibej updated COMDEV-85:
-------------------------------

    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: 

Many big open source projects have issue trackers built on Trac, the same technology Apache
Bloodhound is built on. We're hoping to make it easier for people to refer to objects like
tickets, milestones, versions or whole products in a meaningful way.

Proposed solution: 

One approach to this is to provide ​Twitter card integration (http://dev.twitter.com/docs/cards)
for a richer experience. In addition ​Facebook Meta Tags (http://davidwalsh.name/facebook-meta-tags)
could be helpful. Google Plus ​relies on schema.org metatags, which we may also want to
conform to (http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1211158).

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

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: 

Many big open source projects have issue trackers built on Trac, the same technology Apache
Bloodhound is built on. We're hoping to make it easier for people to refer to objects like
tickets, milestones, versions or whole products in a meaningful way.

Proposed solution: 

One approach to this is to provide ​Twitter card integration (http://dev.twitter.com/docs/cards)
for a richer experience. In addition ​Facebook Meta Tags (http://davidwalsh.name/facebook-meta-tags)
could be helpful. Google Plus ​relies on schema.org metatags, which we may also want to
conform to (http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1211158).

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

More GSoC-related tasks for Bloodhound:

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

    
> [GSoC] Twitter card integration (and other social tags) in Apache Bloodhound
> ----------------------------------------------------------------------------
>
>                 Key: COMDEV-85
>                 URL: https://issues.apache.org/jira/browse/COMDEV-85
>             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: 
> Many big open source projects have issue trackers built on Trac, the same technology
Apache Bloodhound is built on. We're hoping to make it easier for people to refer to objects
like tickets, milestones, versions or whole products in a meaningful way.
> Proposed solution: 
> One approach to this is to provide ​Twitter card integration (http://dev.twitter.com/docs/cards)
for a richer experience. In addition ​Facebook Meta Tags (http://davidwalsh.name/facebook-meta-tags)
could be helpful. Google Plus ​relies on schema.org metatags, which we may also want to
conform to (http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1211158).
> 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/480
> 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