On 27/01/14 22:51, Ryan Ollos wrote:
On Mon, Jan 27, 2014 at 9:59 AM, Abhijeet Nikam <[email protected]>wrote:
Hi,
I am Abhijeet. I am learning python and have a good grasp of its
fundamentals. I also know C/C++, HTML and CSS.
I really wish to contribute to this project and become a part of this team.
I know git basics and I am new to open source.
Could you please guide me on how to proceed from here on? Any bugs to get
started with?
I'll start building the project on my system today.
Thanks,
Abhijeet
Great, we look forward to having you contribute!
Hopefully everything you need to get started is described on the
BloodhoundContributing page. If you find anything that is not clear, or
have specific questions, please let us know.
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
There are also a number of related development resources available through
the Trac project:
http://trac.edgewall.org/wiki/TracDev
You'll also find some tickets listed on the BloodhoundContributing page
that are tagged as "starter". Those should be good tickets to tackle when
you are getting started with the project. Of course, you are welcome to
work any tickets, or propose a new feature or defect. It is best
to briefly discuss with the list before you get started on anything that is
complex or hasn't been captured in the issue tracker yet.
- Ryan
Hi Abhijeet,
Great to hear from you!
I think you may have missed Ryan's reply if you are not subscribed to
the dev list (send an email to [email protected] and
follow instructions you get from the reply).
As Ryan says, the starter tickets are hopefully aimed at giving
relatively simple tasks so that you can get to know the project. You are
welcome to search beyond those for work that you find interesting of course.
The best advice I can give you for the moment is to make sure that you
discuss any work you do on the dev list. Not only is the dev list a
great source for advice, it is also good for keeping a larger set of
people noticing your contributions.
Cheers,
Gary
