6 Subscribe to the pptpclient-devel mailing list if you intend to
7 contribute to this project. On this mailing list we discuss problems
10 https://lists.sourceforge.net/lists/listinfo/pptpclient-devel
15 You may send patches by e-mail, direct or to the mailing list, or if
16 you have CVS commit rights, you may use them.
18 Developers have permission (and encouragement) to adjust more than the
19 file that they are submitting. Other files that may be adjusted are:
22 documentation of changes at the code level.
25 a history of changes as far as an end user is concerned.
28 a list of people who want credit for contributions.
31 a list of things yet to be done.
33 See section two of Eric Raymond's Software Release Practice HOWTO for
34 some useful information on good patching practice.
36 http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/
39 CVS Commits Mailing List
41 Subscribe to the pptpclient-commits mailing list and you will receive
42 messages from the CVS server when another developer commits.
44 https://lists.sourceforge.net/lists/listinfo/pptpclient-commits
49 There are two types of tags. Upstream source and release tags.
51 Upstream source tags are set by the person who brings in the upstream
52 version of ppp or ppp-mppe, and are not expected to move. This is
53 because we are not the authoritative maintainer for those two
54 packages; we're just generating a package ourselves.
56 Upstream source tags at the moment are
65 Release tags are set by the release engineer who makes the releases.
66 Only he is to move these tags.
68 Release tags at the moment are
80 Developers who use IRC on a regular basis are welcome to add the
81 project's channel to their list of autojoin channels.
83 Server: irc.freenode.net
87 $Id: DEVELOPERS,v 1.4 2003/01/15 05:29:20 quozl Exp $