classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Working GridBagLayout and a few other small AWT patches


From: Mark Wielaard
Subject: RE: Working GridBagLayout and a few other small AWT patches
Date: 24 Jul 2003 11:56:46 +0200

Hi,

On Thu, 2003-07-24 at 09:03, Jeroen Frijters wrote:
> Brian Jones wrote:
> > I tried back in March to get Jeroen into direct commits.  ;)  What
> > about it now Jeroen?  
> 
> OK. Thanks. I think Mark wants to set it up though ;-)

I also already offered direct CVS access to Jeroen. Your contributions
have been great. I am happy that you now accept this offer. Please let
me know your savannah.gnu.org user name.

Just so people know how this works. To contribute to GNU Classpath we
have a few requirements. First you have to make sure that you read this:
http://www.gnu.org/software/classpath/docs/hacking.html
(There is a special requirements section.)

Then if you think you meet those requirements and want to make a
contribution you have to contact the GNU Classpath maintainer (currently
me) to arrange some formalities (copyright assignment/disclaimer). The
FSF really wants to make sure that they have the right to distribute
your changes and is pretty strict about getting all the legal issues
right. (This is a hassle and nobody likes it really, but it makes sure
that people can be sure that if the FSF distributes some GNU package
they don't have to worry about using the freedoms that the license gives
them and that there is a clear entity with standing to sue if someone
tries to take those freedoms away.)

Note that the above is not necessary for small incidental contributions
like a simple bug fix or addition of a trivial method. But if you think
you will contribute substantial enhancements to GNU Classpath please
contact me.

Then you can either send patches to the list to discuss them and let
others make suggestion about how to improve them till it is good enough
that someone will commit it for you. Or you can ask for direct CVS
access so you relieve others from the burden of applying your changes.
This means you changes get into the tree sooner, but it is also a big
responsibility since then you really have to make sure to do it
correctly (good ChangeLog entry, respect the coding conventions, no
checkin of anything that could be controversial before announcing it on
the list, and above all not break the build!). for CVS access you will
have to have an account on savannah.gnu.org and contact the Classpath
administrators (currently Brian or me) to add you to the developers
list.

Note that I don't mind reviewing and checking in other peoples patches
myself. It can take a while though. So if it doesn't get applied
immediatly you have to be sure to either add them to the savannah patch
manager and/or to send a reminder to the list after a while when someone
can take another look at it.

Cheers,

Mark




reply via email to

[Prev in Thread] Current Thread [Next in Thread]