An Open Source Framework to extend Cocoa
MOKit Home Page
This page has information that will be of interest to folks who want to get involved with the MOKit project. If you simply want to use MOKit, you should download a released version and just use it. But if you want to become more involved with the development of MOKit itself, read this information.
To get started with MOKit's CVS repository, you can use the following two commands:
Just hit return when it asks for a password.
I recommend using the -P option with "cvs checkout" commands and the -P and -d options with "cvs update" commands. In fact, I recommend simply putting those options into your ~/.cvsrc so they will always be used. Also, I personally like the -u and -w options for the "cvs diff" command.
For more information about using SourceForge's CVS server, please see the SourceForge Site Documentation.
If you want to get involved with the MOKit project by suggesting features, reporting bugs, contributing code, or whatever, post to the discussion forums or just mail me.
I am still becoming familiar with how SourceForge works, so bear with me.
Bugs will be tracked through the SourceForge bug tracker. It might be a good idea to bring up your bug on the forums or mailing lists prior to submitting it just to get confirmation that it sounds like a real bug and that it is not a duplicate of a known issue.
Submitting Patches or New Features
If you have code you would like to contribute to MOKit, start a discussion about it on the Developers forum or post to the mokit-develop mailing list. In your post give the general details of what you're proposing fixing/changing/adding. Do not include code unless it is very small (eg a small bug fix may be best described by the actual code).
Here are some guidelines (I am not going to be real strict about any of this, at least at first, but the less work I have to do to the code, the quicker it might be checked in):
The general process for getting stuff included, at least for now, will be to discuss it on the forums/mailing lists, refine API and so on through the discussion, get some agreement on the change, and then get it checked in. For now, the last step will be done through sending the diffs or modified project to me so I can commit it. Over time, active developers may get CVS commit access of their own.