view README.CVS @ 9896:a806e5150eca

[gaim-migrate @ 10785] " summary: This patch adds support for a zephyr proxy tzc. User visible changes will be an options check box to enable tzc, and a text box with the command to run tzc. %s in the command would be replaced by the user's exposure (visibility) level. e.g ssh username@host tzc -e %s Details: What is tzc: tzc aka "trivial zephyr client", is a zephyr helper program, designed originally for use with emacs-zephyr (it takes as input and outputs lisp expressions), and also used as the backend for kzephyr. Why? It is often invoked by a zephyr using on a remote host, by doing ssh username@host tzc -e EXPOSURE so that one can use any of the zephyr clients that use it as a backend, behind NAT "routers" and firewalls, which will generally block zephyr. Also, people will not have to recompile gaim, or have a working zephyr setup as is currently needed - they can merely set the tzc command to a run tzc from a remote host which has zephyr and tzc installed -- most zephyr users are at universities where they have access to such a machine. Where can one get tzc? I tested this against the version (2.6.15-zml) available here: http://www.club.cc.cmu.edu/debian/dists/stable/contrib/source/tzc-cclub_001-3.tar.gz Some older versions won't support buddylists. A lot of the parsing code was borrowed (and converted from C++ to C) from kzephyr (http://www-2.cs.cmu.edu/~colohan/kzephyr/), a GPL'd zephyr client. And tzc is also GPL'd, FWIW." --Arun A Tharuvai committer: Tailor Script <[e-mail]>

If you plan to use gaim CVS, PLEASE read this message in its entirety!

Gaim is a fast-moving project with a somewhat regular release schedule.  
Due to the rate of gaim development, CVS undergoes frequent bursts of 
massive changes, often leaving behind brokenness and partial 
functionality while the responsible developers rewrite some portion of 
code or seek to add new features.

What this all boils down to is that CVS _WILL_ sometimes be broken.
Because of this, we ask that users who are not interested in
personally tracking down bugs and fixing them (without a lot of
assistance from the developers!) avoid CVS and use releases.  Since
releases will be made often, this should not prevent anyone from using
the newest, shiniest features -- but it will prevent users from having
to deal with ugly development bugs that we already know about but
haven't gotten around to fixing.

If you are interested in hacking on gaim, please read README and
HACKING, and take note of the issues in PROGRAMMING_NOTES.  (Note that
they may be somewhat out of date at times.) Win32 developers, please
read README.mingw.

By far the best documentation, however, is the documented code.  Not
all parts of gaim have yet been documented, but the major subsystems
are falling fast.  If you have doxygen, you can use the Doxyfile in
the toplevel directory to generate pretty documentation.  Otherwise
(or even if you do!), the header files for each subsystem contain
documentation for the functions they contain.  For instance,
conversation.h contains documentation for the entire
gaim_conversation_* API, and account.h contains documentation for the
gaim_account_* API.

If you have questions, please feel free to contact the gaim developers
by email at [e-mail], on IRC at
irc.freenode.net in #gaim, or via the sourceforge forums at
http://www.sourceforge.net/projects/gaim.  Please do as much homework
as you can before contacting us; the more you know about your
question, the faster and more effectively we can help you!

Send patches to [e-mail] or post them in the
Sourceforge forums at http://www.sourceforge.net/projects/gaim.