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-5091) Derby Test and Fix 2011 GSoC Project
Date Sat, 05 Mar 2011 16:22:45 GMT

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

Bryan Pendleton commented on DERBY-5091:

A good way to search for Jira issues to work on when you are unfamiliar with Derby
is to search for issues with the 'newcomer' label. These are generally issues that are 
felt to be fairly straightforward and do not require a lot of prior knowledge of Derby in

order to investigate. The Derby Jira issues also have other categories, identifying 
issues which touch certain parts of Derby, such as the SQL subsystem, the 
networking subsystem, or the storage subsystem.

> Derby Test and Fix 2011 GSoC Project
> ------------------------------------
>                 Key: DERBY-5091
>                 URL: https://issues.apache.org/jira/browse/DERBY-5091
>             Project: Derby
>          Issue Type: Task
>            Reporter: Tiago R. Espinha
>            Assignee: Tiago R. Espinha
>            Priority: Minor
> This is the JIRA issue where I will be aggregating issues that might be interesting for
a student to address in a "test-and-fix project" under my mentoring during a Google Summer
of Code project, for this year's edition.
> Ideally, I would like to have a closed set of issues that are to be addressed by a single
student during the whole program before the program itself starts. If you have comments or
suggestions, please feel free to comment on this issue.
> Obviously, in open-source we cannot stop people from working on whichever issues they
feel like. I would actually be quite happy if there were students starting work on some of
these issues even before the program starts. That will certainly weigh in when the time to
make a decision comes.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message