New contributor
Locked
New contributor
 
|
Re: New contributor
|
|
Re: New contributor
|
|
Re: New contributor
|
|
Re: New contributor
|
|
In reply to this post by asdini
Hi Ahmed
Welcome aboard! My advice would be to focus on trying to fix the bugs that people have reported. It is a great way to learn how to quickly sift through lots of code and you'll also end up reading quite a bit of existing code which will help you when you come to writing your own. Bug fixes are also more likely to be quickly reviewed and committed (or rejected with feedback) because they generally require less effort from a committer than new features do. As your confidence grows you can then move on to more complicated bugs or perhaps new features that you're interested in. The basic process for bug fixes is to: 1. Attempt to reproduce the reported problem. (If you are unable to do so then request more information from the reporter) 2. If necessary do some research and discuss with the community (either on the jira issue or the dev list) what the desired behavior should be. 3. Identify and fix the problem code making sure nothing else breaks in the process. 4. Submit a patch and patiently await feedback :-) Best of luck in whatever approach you decide to take. Regards Scott HotWax Media http://www.hotwaxmedia.com On 29/07/2009, at 12:32 AM, Ahmed Dini wrote: > > Hello David, > > Thanks for the welcome and the helpful information. I read your long > article > about Colloboration. It answered a lot of my questions and learned a > lot > from it. > > I was not sure how Jira Issues are assigned, who assignes them, or > how to > pick Issues. But from your email and from other sources I now have a > clear > picture of how system works except one thing which is about picking > the > right JIRA ISSUE, In the Open Issues section some of the unresolved > issues > date back to few years in the past. Shall I always pick recent ones > only? > > I have decided to start with writing patches. > > Thanks again for welcome. > > > David E Jones-4 wrote: >> >> >> Ahmed, >> >> Thanks for reaching, it'll be great to have you involved in the >> project! >> >> Apache OFBiz is a community driven software project. What you're >> talking about here implies a central organization that drives the >> project and could make such assignments. Fortunately (otherwise OFBiz >> would not be what it is today) such a central organization that can >> make assignments does not exist. In other words, there is no one that >> could assign a mentor for you because no one in the organization has >> authority over any of the committers to make them do things. >> >> You could certainly send out an open request and ask for any of the >> committers to volunteer to be a mentor for you. However, please >> understand that you are asking someone to do something for free, so >> at >> least please define what you would like a mentor to do for you. >> >> The normal way of going about this is to interact with the community. >> For some ideas about how to do this effectively please read my blog >> post on the topic: >> >> http://osofbiz.blogspot.com/2009/06/open-source-community-collaboration.html >> >> For this particular email it seems like you have one question. If you >> go into more detail about that question instead of about why you >> think >> others should help you with it, or trying to get more of a commitment >> for regular help, then your chances of getting it answered will be >> better. >> >> What did you click on that resulted in this error message, or what >> were you trying to do? If you were trying to assign the issue to >> yourself, you don't have to do that in order to work on it, just drop >> in a comment and start working. If you have questions or thoughts and >> would like to discuss it, send a message to the dev mailing list. >> Eventually you'll need to work with a committer to actually get your >> changes into SVN, and that person is basically a volunteer mentor for >> that particular issue and they are the ones who will be assigned to >> the issue. Your uploads/patches and comments will all have your name >> on it, and you should be credited in the commit log as well. When we >> are looking for new committers (most of what the PMC does) this is >> exactly what we look at, so if you want to become a committer then >> this is just the sort of activity you want to get involved in. >> >> And of course, please send any other questions you have (with as much >> detail and background as possible!) right here in the future. I look >> forward to hearing more from you. >> >> -David >> >> >> On Jul 27, 2009, at 2:18 AM, Ahmed Dini wrote: >> >>> >>> >>> Hello Everyone. >>> >>> First of all, I would like congratulate everyone involved in the >>> development >>> and maintenance of Ofbiz project for the wonderful Job done so far. >>> Although, I have not contributed to the project yet, I have always >>> been a >>> great fan of Obiz. I have been learning about Ofbiz since my final >>> year >>> project at University about a year and half a go as I have chosen it >>> for my >>> project which was about ERP solutions. I have gone through the >>> entire >>> tutorial I could find and also bought and studied the advanced >>> framework >>> tutorials by David. >>> >>> Now I am ready to participate in the development of Ofbiz project. I >>> have >>> read the Ofbiz Contributors Best Practice and yet I feel I might >>> mess up >>> things. Just a fear of starting. I know Ofbiz contributors have >>> their own >>> tight schedules and problems but I think to bring new contributors >>> on board, >>> it would be a good Idea if every new contributor could be assigned a >>> committer or an experienced contributor as a mentor until the new >>> contributor is confident enough to work on his/her own. >>> The advantage is the assigned committer or the experienced >>> contributor can >>> follow closely the growing experience and capabilities of the new >>> contributor, assign them Jira issues they know the new contributor >>> can fix. >>> A lot of people including me feel comfortable in working under >>> guidance >>> particularly when trying new things especially if they are new >>> graduates or >>> have not commercial experience. >>> >>> Please let me know if you have a quick way I can get started. Under >>> WorkLog >>> in my Jira account, it says >>> You don't have permission to work on this issue for every Jira Issue >>> I open >>> no matter what status it is in. Does that mean I can't do anything >>> to any >>> Issue, also can I assign an Issue to myself? >>> >>> Regards, >>> Ahmed >>> -- >>> View this message in context: >>> http://www.nabble.com/New-contributor-tp24675628p24675628.html >>> Sent from the OFBiz - Dev mailing list archive at Nabble.com. >>> >> >> >> > > -- > View this message in context: http://www.nabble.com/New-contributor-tp24675628p24698037.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > |
smime.p7s (3K)
Re: New contributor
|
|
| Free forum by Nabble | Edit this page |