You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tiago R. Espinha (JIRA)" <ji...@apache.org> on 2011/03/03 22:34:36 UTC

[jira] Created: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

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

        

Re: [jira] Commented: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by Houx Zhang <ho...@gmail.com>.
Thanks for your suggestion, They are useful to me! I will go on following
your advice.

Houx

2011/3/6 Eranda Sooriyabandara <er...@gmail.com>

> If you are looking forward to proceed on the project Derby test and fix
> then the following screencast done by Tiago will help you a lot.
> http://www.vimeo.com/5376690. <http://www.vimeo.com/5376690> Anyway it's
> worth watching and give you a good idea about Apache Derby.
>
> On Sat, Mar 5, 2011 at 9:52 PM, Bryan Pendleton (JIRA) <ji...@apache.org>wrote:
>
>>
>>    [
>> 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
>>
>>
>>
>

Re: [jira] Commented: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by Eranda Sooriyabandara <er...@gmail.com>.
If you are looking forward to proceed on the project Derby test and fix then
the following screencast done by Tiago will help you a lot.
http://www.vimeo.com/5376690. <http://www.vimeo.com/5376690> Anyway it's
worth watching and give you a good idea about Apache Derby.

On Sat, Mar 5, 2011 at 9:52 PM, Bryan Pendleton (JIRA) <ji...@apache.org>wrote:

>
>    [
> 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
>
>
>

[jira] [Commented] (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "David Martín Nieto (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009125#comment-13009125 ] 

David Martín Nieto commented on DERBY-5091:
-------------------------------------------

Hello,

I've been checking the Issues that you they are marked as newcomers on Derby and  I think I could take care of DERBY-3600 and DERBY-3676 although the latter I have not looked at in detail. I have enough experience in programming in Java and therefore these two caught my attention.

I am interested in being a part of the Gsco2011 and would do in this project of Test and Fix 2011. I will keep looking for other Issues to see if I can cover any more.

If you can indicate some other issue to create more appropriate and these two do not seem suitable for this gsoc2011 please tell me.

I have already mounted the environment Derby 10.7 and I made some tests on it after building it, I have the intention to over this week after some more testing begin make some changes on the source related to the DERBY-3600.

A greeting and thanks.

> 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
>              Labels: gsoc2011
>
> 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

[jira] Commented: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Houx Zhang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002985#comment-13002985 ] 

Houx Zhang commented on DERBY-5091:
-----------------------------------

Hi, Tiago. It's an interesting issuse. However, which field of issuses does it focus on? And how can a new comer get start with it, please?

> 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

        

[jira] Commented: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Mike Matrigali (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-5091:
----------------------------------

    Component/s: Test
    
> Derby Test and Fix 2011 GSoC Project
> ------------------------------------
>
>                 Key: DERBY-5091
>                 URL: https://issues.apache.org/jira/browse/DERBY-5091
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>            Reporter: Tiago R. Espinha
>            Assignee: Tiago R. Espinha
>            Priority: Minor
>              Labels: gsoc2011
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Tiago R. Espinha (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009391#comment-13009391 ] 

Tiago R. Espinha commented on DERBY-5091:
-----------------------------------------

@ Houx,

This issue is still work in progress. I plan on aggregating here a mix of some test conversions and open bugs in JIRA. At this point, I'm considering including some (or eventually all) our SQL store tests (java/testing/org/apache/derbyTesting/functionTests/tests/store/*.sql) but this is something I'm still thinking about. Ideally, the GSoC student would do a nice mix of not only test conversions (that, in my experience, get boring after a while) but also bug fixes which tend to be more exciting as they add actual tangible value to Derby.

@ David and Houx,

In the meanwhile, while GSoC hasn't officially started and to demonstrate that you really have everything up and running, it'd be a really good step to pickup an issue on JIRA marked as "Newcomer" and get grinding on it. Those issues David suggested are both for Newcomers so maybe that's a good starting point.

Keep in mind that the competition this year seems to be tough (many candidates and apparently only me as a mentor), so it's really important to get cracking on it even before GSoC starts; obviously, if I have to pick from two students where one of them has everything set up and has already demonstrated that he/she can do test conversions, and the other hasn't really done anything so far, then my choice will be pretty simple to make.

It's also important to get in touch with the community by subscribing and participating (even if with questions) in our mailing lists and eventually in our IRC channel as well; I find that the IRC bit makes for better communication between mentors and mentees. I usually idle around #derby at irc.freenode.net as do several other contributors and students.

So, for now, I would say pick up something for newcomers and try to fix it. And please, if you get stuck or if you need some pointers, feel free to ask on our mailing list.

> 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
>              Labels: gsoc2011
>
> 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

[jira] [Issue Comment Edited] (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "David Martín Nieto (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009125#comment-13009125 ] 

David Martín Nieto edited comment on DERBY-5091 at 3/21/11 1:44 PM:
--------------------------------------------------------------------

Hello,

I've been checking the Issues that you they are marked as newcomers on Derby and  I think I could take care of DERBY-3600 and DERBY-3676 although the latter I have not looked at in detail. I have enough experience in programming in Java and therefore these two caught my attention.

I am interested in being a part of the Gsco2011 and would do in this project of Test and Fix 2011. I will keep looking for other Issues to see if I can cover any more.

If you can indicate some other issues more appropriate or priority or if these two do not seem suitable for this gsoc2011 please tell me.

I have already mounted the environment Derby 10.7 and I made some tests on it after building it, I have the intention to over this week after some more testing begin make some changes on the source related to the DERBY-3600.

A greeting and thanks.

      was (Author: david.martin.nieto):
    Hello,

I've been checking the Issues that you they are marked as newcomers on Derby and  I think I could take care of DERBY-3600 and DERBY-3676 although the latter I have not looked at in detail. I have enough experience in programming in Java and therefore these two caught my attention.

I am interested in being a part of the Gsco2011 and would do in this project of Test and Fix 2011. I will keep looking for other Issues to see if I can cover any more.

If you can indicate some other issue to create more appropriate and these two do not seem suitable for this gsoc2011 please tell me.

I have already mounted the environment Derby 10.7 and I made some tests on it after building it, I have the intention to over this week after some more testing begin make some changes on the source related to the DERBY-3600.

A greeting and thanks.
  
> 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
>              Labels: gsoc2011
>
> 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

[jira] [Resolved] (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Myrna van Lunteren (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-5091.
---------------------------------------

    Resolution: Fixed

I'm marking this as fixed because this GSoC project was completed.

Most of the issues on the list are still open though.
                
> Derby Test and Fix 2011 GSoC Project
> ------------------------------------
>
>                 Key: DERBY-5091
>                 URL: https://issues.apache.org/jira/browse/DERBY-5091
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>            Reporter: Tiago R. Espinha
>            Assignee: Tiago R. Espinha
>            Priority: Minor
>              Labels: gsoc2011
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (DERBY-5091) Derby Test and Fix 2011 GSoC Project

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-5091:
----------------------------------

    Labels: gsoc2011  (was: )

> 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
>              Labels: gsoc2011
>
> 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