New GNU Classpath developer Gary Benson

[Mark Wielaard]

Hi all,

As you probably already noticed by reading classpath-patches Gary has
been working on the security framework. And has written several mauve
tests to back up his patches. He now has direct developer access to
speed up his work.

Gary, here are the rules:
        
        The first rule of GNU Classpath is - you do not talk about GNU
        Classpath, you write code. The second rule of Fight Club is -
        you DO NOT talk about GNU Classpath, you write code. Third rule
        of GNU Classpath, someone yells stop!, goes limp, taps out, your
        patch is NOT approved. Fourth rule, a bug report is between just
        two people, the reporter and the fixer. Fifth rule, one commit
        at a time, or get CVS merge conflicts. Sixth rule, no shirt, no
        shoes, just bare ASCII source. Seventh rule, fixes will go in as
        long as they have to. And the eighth and final rule, if this is
        your first night at GNU Classpath, you have to patch the AUTHORS
        file. (*)
        
Please post a patch and ChangeLog entry to classpath-patches to add
yourself to the AUTHORS file. You can consider that patch pre-approved
of course.

Thanks,

Mark

(*) More formal rules are of course in the GNU Classpath Hackers guide:
    http://www.gnu.org/software/classpath/docs/hacking.html

-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/

signature.asc
Description: This is a digitally signed message part