Mailing-List: contact commits-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Date: Tue, 16 Apr 2013 08:47:15 +0000 (UTC)
From: "Andreas Weigel (JIRA)" <jira@apache.org>
To: commits@community.apache.org
Message-ID: <JIRA.12638659.1364049201653.172545.1366102035779@arcas>
In-Reply-To: <JIRA.12638659.1364049201653@arcas>
References: <JIRA.12638659.1364049201653@arcas>
Subject: [jira] [Commented] (COMDEV-85) [GSoC] Twitter card integration (and
 other social tags) in Apache Bloodhound
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COMDEV-85?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13632=
667#comment-13632667 ]=20

Andreas Weigel commented on COMDEV-85:
--------------------------------------

Hi Branko =C4=8Cibej,

I'm Andreas Weigel, a final year undergraduate in computer science from Kar=
lsruhe Institute of Technology, Germany.=20
After using tools and frameworks of apache software foundation i would like=
 to give something back to the open source community and would like to part=
icipate in this years GSoC in an apache project.
I'm interested in the idea adding social media integration into a software =
development collaboration tool. Using redmine and chiliproject i'm experien=
ced in using such tools.

I also have developing experience by first working two years in the researc=
h center for information technology in Karlsruhe, Germany and since two yea=
rs as a student in a software developing company.

Developing experience include Java, JSP, JS, jQuery, CSS, Twitter Bootstrap=
, HTML, mySQL, Spring, Spring MVC, Tiles, Spring Data, OpenCms, Maven, GIT/=
SVN, Jenkins, Sonar, Tomcat, Jetty, SCRUM

Can you please provide more information about this project and tell me what=
 the next steps are to move on?

Thanks!
               =20
> [GSoC] Twitter card integration (and other social tags) in Apache Bloodho=
und
> -------------------------------------------------------------------------=
---
>
>                 Key: COMDEV-85
>                 URL: https://issues.apache.org/jira/browse/COMDEV-85
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Branko =C4=8Cibej
>              Labels: bloodhound, gsoc2013
>
> Apache Bloodhound is a software development collaboration tool, including=
 issue tracking, wiki and repository browsing (see: http://bloodhound.apach=
e.org). Bloodhound extends Trac (http://trac.edgewall.org/) with multiple p=
roduct 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.=20
> Problem:=20
> 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 f=
or people to refer to objects like tickets, milestones, versions or whole p=
roducts in a meaningful way.
> Proposed solution:=20
> One approach to this is to provide =E2=80=8BTwitter card integration (htt=
p://dev.twitter.com/docs/cards) for a richer experience. In addition =E2=80=
=8BFacebook Meta Tags (http://davidwalsh.name/facebook-meta-tags) could be =
helpful. Google Plus =E2=80=8Brelies on schema.org metatags, which we may a=
lso want to conform to (http://support.google.com/webmasters/bin/answer.py?=
hl=3Den&answer=3D1211158).
> Skills needed:=20
> Bloodhound and Trac are written in Python, so a moderate dose of Python p=
rograming skills are required.=20
> References:=20
> Link to the original issue:=20
>     https://issues.apache.org/bloodhound/ticket/480
> More GSoC-related tasks for Bloodhound:
>     https://issues.apache.org/bloodhound/query?status=3D!closed&keywords=
=3D~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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira