1.2.2 How can I help with GNUstep?

  1. Write/debug library code
  2. Write documentation
  3. Update the task list and library headers
  4. Write applications

Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.

Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. Get in touch with the GNUstep maintainer about this.

Don’t start with large-scale reorganization of anything - instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don’t break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.

Don’t be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It’s much better to ’resign’ and take on a smaller job than to just stop without telling anyone.

Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices). But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation.