db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ForNewDevelopers" by DavidVanCouvering
Date Mon, 06 Feb 2006 23:03:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/ForNewDevelopers

------------------------------------------------------------------------------
  = Information for new developers =
  
- This page lists information for a developer to get started with Derby.
+ So you want to start contributing to Derby... We welcome your contributions!  This page
lists information to help a developer to get started contributing to Derby.
+ 
+ [[TableOfContents]]
+ 
  
  == Ongoing Projects ==
  
@@ -72, +75 @@

  
  Take a look at [http://wiki.apache.org/db-derby/DerbyContributorChecklist DerbyContributorChecklist]
  
+ == Working in the Derby Core Systems ==
+ 
+ It is '''relatively''' easy to work on the "outskirts" of Derby such as tools, documentation,
QA, and some runtime services.  But what if there's something you would really like to add
or fix in the core of Derby, and none of the existing contributors are touching the bugs you
have logged.
+ 
+ One of the challenges of contributing to a database system is that the core of the system
involves algorithms, designs and architectures that are well known to those who know them,
but are a bit of a mystery to those who are new to them.  It can seem daunting to venture
into these waters.  We would very much like to have contributions in these areas, and probably
the best way to do this is to enroll a guide or mentor to help you get introduced into this
area.  Here is a suggested approach:
+ 
+    * Indicate your interest - send an email to derby-dev saying you would like to work on
this code, indicate you are a newbie, and ask if any of the old hands would like to guide
you through the waters
+    * If you get a volunteer, work with this person to vet your ideas and get suggestions.
 They can help you understand the code and algorithms and make your experience much more enjoyable.
+    * If you don't get a volunteer, start poking around and sending emails about what you're
thinking of doing, and even submit an initial patch.  It is more than likely that you will
enroll a mentor fairly quickly this way; in general someone who likes to code can't help but
get involved when someone is working on code that is familiar to them.
+ 
+ The main point here is, don't let the inherent complexity of the Derby core system code
be a block to your contribution.  As a community we welcome your contributions, and want to
help you get involved.
+ 
  == Reference Materials ==
  
  For general process and guidelines:

Mime
View raw message