|David W. Van Couvering||Dec 14, 2005 12:28 pm|
|Geir Hoydalsvik - Sun Norway||Dec 15, 2005 12:21 am|
|Daniel John Debrunner||Dec 15, 2005 7:15 am|
|Deepa Remesh||Dec 15, 2005 7:55 am|
|Mike Matrigali||Dec 15, 2005 10:06 am|
|Kathey Marsden||Dec 15, 2005 10:23 am|
|Daniel John Debrunner||Dec 15, 2005 11:09 am|
|Daniel John Debrunner||Dec 15, 2005 11:23 am|
|Mike Matrigali||Dec 15, 2005 11:49 am|
|Dibyendu Majumdar||Dec 15, 2005 12:16 pm|
|Francois Orsini||Dec 15, 2005 12:25 pm|
|John Embretsen||Dec 16, 2005 8:36 am|
|David W. Van Couvering||Dec 22, 2005 7:03 pm|
|Deepa Remesh||Dec 27, 2005 4:27 pm|
|Andrew McIntyre||Jan 10, 2006 3:40 pm|
|Deepa Remesh||Jan 10, 2006 4:19 pm|
|Subject:||Re: So you wanna write some database code|
|From:||Geir Hoydalsvik - Sun Norway (Geir...@Sun.COM)|
|Date:||Dec 15, 2005 12:21:24 am|
A good idea David! Perhaps the community also could work on getting a list of useful tasks suited for students and newcomers. I know this has been attempted before, could it be tried again? Perhaps one also could create a users competition like the best demo app, the best test, or similar? The winner could be recognized on a web page hall of fame?
David W. Van Couvering wrote:
Down at ApacheCon at our BoF we had a good discussion about what might help people who want to contribute to Derby but feel they don't have the database internals background needed. It was generally recognized that there is a pretty hefty learning curve to be able to work on some of the core parts of Derby such as the SQL compiler and the kernel. The skills and background for someone writing database applications is pretty different from someone writing database internals.
The problem is that Derby support can not scale to handle the growing number of users unless more members of the community are able to get to know the code and start contributing.
One thought we had was that those of us who know a certain area of Derby can make ourselves available to mentor/provide guidance to those who want to work in that area but don't feel qualified.
For example, let's say there is a bug in the compiler that is causing me problems. I log the bug, but nobody seems to be responding (scratch your own itch and all that). I could send an email out saying "I'd like to get this fixed, and am willing to do the work, but I don't know anything about the compiler. Is anyone willing to help walk me through this?" Then someone who knows the compiler can volunteer to help.
Alternately, someone who knows the compiler can respond to a JIRA item saying "I don't have time to implement, test, and document this, but I'd be willing to help walk you through how you might do this."
I think this is pretty workable. It does take a willingness on both sides -- from the specialists to not try to fix everything themselves (not scalable long-term) and instead make themselves available to provide guidance, and from the non-specialists to jump in with the support of a specialist.