db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6870) Google Summer of Code 2016: Derby bug fixing
Date Sat, 13 Feb 2016 04:00:20 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145772#comment-15145772

Bryan Pendleton commented on DERBY-6870:

For those of you looking for some resources to get started:

1) Start by reading Apache's GSoC information:


and Google's information:


2) Read the general information about contributing to and working on Derby:


3) Follow the instructions for downloading the Derby code, building Derby, and running Derby


If you get confused at any point along the way, ask questions on the derby-dev mailing list,
and Derby community members will be glad to help you out.

> Google Summer of Code 2016: Derby bug fixing
> --------------------------------------------
>                 Key: DERBY-6870
>                 URL: https://issues.apache.org/jira/browse/DERBY-6870
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Bryan Pendleton
>              Labels: database, gsoc2016, java, jdbc
> For the 2016 Google Summer of Code, I am offering to mentor a
> student for general bug fixing of the Derby database.
> The Derby JIRA has collected the community's knowledge about
> known bugs in Derby, and there are plenty of bugs for us to work on.
> If you take on this project, with assistance from me, you'll:
> - select Derby issues from the Derby bug tracker to fix
> - reproduce those problems by writing and running tests
> - develop patches to address the problems
> - work with the community to get the patches reviewed
> - have your reviewed and accepted contributions committed to the next Derby release.

This message was sent by Atlassian JIRA

View raw message