[RDT-Dev] Re: Continuing work

[Markus B. <Mar...@gm...>]

Hi!

Welcome, you are a developer now. Thanks for your contribution and your 
effort. The only thing to be clarified is the license issue. With regard 
to Adams last mail and my mail with comments to the license issue I 
would suggest the following header for the source files:

/*

    Author: <Your Name>

    Copyright (c) 2004 RubyPeople. 

    This file is part of the Ruby Development Tools (RDT) plugin for eclipse.
    You can get copy of the GPL along with further information about RubyPeople 
    and third party software bundled with RDT in the file 
    org.rubypeople.rdt.core_<version>/RDT.license or otherwise at 
    http://www.rubypeople.org/RDT.license.

    RDT is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    RDT is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with RDT; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA


*/

I would not tend to use the RubyLicense, because of point 3 and 4:

3. You may distribute the software in object code or executable
    form, provided that you do at least ONE of the following:

      a) distribute the executables and library files of the software,
         together with instructions (in the manual page or equivalent)
         on where to get the original distribution.

<b to d snipped>
 4. You may modify and include the part of the software into any other
    software (possibly commercial).

As far as I understand that, somebody could make some changes, create a 
binary only distribution, sell it and must only add a link to the 
original source code (i.e. not to the modified). Actually, thats the 
only thing I'd like to be prevented.

In the RDT.license file I would write something like the following:
--- start RDT.licnense ---
RubyPeople is no legal entity but consists of the people who have 
contributed to the RDT. These are:
Michael Hale, Adam Williams, Nathaniel Talbott, Markus Barchfeld, 
Christopher Williams

RDT is bundled with the kxml library, which is available under CPL.

<COPY OF GPL>
--- stop RDT.license ---
I just checked if it is ok to bundle a program which uses the GPL with 
CPL code. Unfortunately, it is NOT. So we have a problem here. Unless we 
used the CPL. Maybe we should check that. For me, it is getting late 
now, and as a suggestion to Chris: Check in with a copyright notice, 
initially.


Christopher Williams wrote:

>Markus,
>            I merged my code with the changes you had made to the UI
>plugin. I've also taken a look at sourceforge's tracker for feature
>requests. One of the requests was to add the new file/new folder/ new
>ruby project menu items. I've added that to my code, made the outline
>view show in the Ruby Perspective and also made the "new wizard" button
>in the Ruby perspective show the relevant wizard options (file, folder,
>ruby project). I've also fixed the icons for globals and modules. Those
>gifs got broken on my machine somehow.
>  
>
OK. Thats cool. I am looking forward to update my workspace with your 
fchanges.

>Any chance I could get developer access soon? I'd like to check all of
>this in, in addition to the re-working of the parser code.
>  
>
Done.

> 
>Also, in all of this somehow now the plugin is working with M7, so I'm
>guessing it's a change that you had made! There is one strange behavior
>on my machine - the icons used for the outline view are showing up very
>small.
>  
>
Can' remember that I changed something fundamental ... I also didn't 
notice that the icons are too small.

> 
>I plan to work more on the parser - I have it recognizing access rights
>a little (realizes attributes default to private, methods to public, and
>can set methods private given a "private :someMethod, :someOtherMethod"
>line) and plan to get it to recognize all access modifiers.
> 
>
Fine, have fun.
Markus