Hi Ryan,
Thanks for quick reply. Yeah I setup the basic development environment for
Bloodhound. As you suggested I'm looking at the trac architecture, but i
didn't get the part "Each of the 3 tickets in issues.apache.org has a link
to a plugin
on trac-hacks"  can you please tell more about it, what are the plugins i
should check.

As you suggested try to fix bugs is good to understand the code. I checked
starter issues in Bloodhound and  I like to start with the issue
 https://issues.apache.org/bloodhound/ticket/724 how I can get more
information about this.


On Sat, Mar 1, 2014 at 9:50 PM, Ryan Ollos <[email protected]> wrote:

> On Sat, Mar 1, 2014 at 12:10 AM, Thimal Kempitiya <[email protected]
> >wrote:
>
> > Hi,
> > I'm Thimal Kempitiya,a third year computer science and engineering
> > undergraduate at university of moratuwa. I'm interested in the project
> idea
> > "Dynamic client-side autocompletion features for the Apache Bloodhound
> > ticket system". I have the programming knowledge in python and also I'm
> > currently doing my internship in a company and there I do development
> using
> > html, javascript and ajax. I think I have the knowledge to do this
> project.
> > I clone the repository and build it. Can you please tell me how should I
> > proceed to learn about bloodhound and more of the project
> >
> > --
> >
>
> Hi Thimal,
>
> Assuming you've read through BloodhoundContributing and have the basic
> development environment setup, you might want to start looking at the
> plugins that have been implemented for Trac. Each of them has some
> significant issues and the code is not suitable for direct integration, but
> they can help with understanding the architecture and giving ideas on where
> to start. Each of the 3 tickets in issues.apache.org has a link to a
> plugin
> on trac-hacks. You probably want to setup a Trac development
> environment (1) for installing and evaluating the plugins.
>
> There is more information on the Trac architecture (2). You are also
> welcome to dive right in and try fixing an issue in Bloodhound, just to get
> accustomed to the code and environment. The issues tagged with "starter"
> (3) are good tickets to tackle. There are a few pages that need Bootstrap
> templates. Writing a template is a good way to become familiar with
> Bootstrap.
>
> (1) http://trac.edgewall.org/wiki/TracDev/DevelopmentEnvironmentSetup
> (2) http://trac.edgewall.org/wiki/TracDev
> (3)
> https://issues.apache.org/bloodhound/query?status=!closed&keywords=~starter
>



-- 




*Thimal Kempitiya <http://www.facebook.com/thimalk> UndergraduateDepartment
of Computer Science and Engineering University of Moratuwa.*

Reply via email to