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 "DerbyDev" by DanDebrunner
Date Wed, 12 Jul 2006 22:17:38 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 DanDebrunner:
http://wiki.apache.org/db-derby/DerbyDev

New page:
= Derby Development =
== Getting Started on Development ==
The Derby community welcomes anyone to participate in Derby's development.

Derby's web-site has a [http://db.apache.org/derby/derby_comm.html Get Involved] page that
explains how
all development occurs in the open on the derby-dev at db.apache.org mailing list, Apache's
open source development
model and some mechanics of how to contribute code changes.

This wiki contains a number of pages aimed at getting people started working on Derby, since
these are wiki pages
feel free to improve them based upon your experience on joining the Derby community.

A first action to consider is submitting an ICLA to the ASF, see the [:DerbyContributorChecklist:contributor
checklist]
for how to and other items to be aware of.

There are more ways to get invovled in Derby than submiting code, the [:ForNewDevelopers:information
for new developers]
pages lists many and includes some of the mechanics, such as links to specification &
getting the code. 

Confused or intrigued as to how Derby implements something, then see if it has been written
up by anyone at the
[:HowItWorks:how it works] page, if it hasn't please add to wiki any information you discover.
It could be a simple
as pointers to the best source file to look at for an issue, or a complete write up of the
functionality.

Eager to start coding and submit a patch to Derby, take a moment to read this [:PatchAdvice:advice]
. Heed the
summary, ''communicate, communicate, communicate'', an open source project is all about open
communication, bring those
half-baked, early, partially thought out, incomplete or crazy ideas to the list, others will
help bake (complete) them.

Ready to code? Just one more thing, take a quick look at the complete [:DerbyCommitProcess:process]
of how a change is made in Derby.
This includes using [http://db.apache.org/derby/DerbyBugGuidelines.html JIRA], Derby's bug
& issue tracking system,
to help track the issue and the place to attach the patch file to.

Worked through all of this, made some changes, and you've submitted a patch, congratulations!
B)
While waiting for reviews, see what [:PatchListMaintenance:patches] others have contributed,
review one or two of them. This good karma will come back to you when someone spends the time
to
review your patch.

Everyone ignoring your patch? Don't take it personally, people are just busy. Read the [:PatchAdvice:advice]
again for ways to sell your patch and see if you missed any step that might stop anyone from
spending time on it.


Mime
View raw message