Difference between revisions of "Developer resources"
From K5Wiki
SamHartman (talk | contribs) |
|||
(19 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
==Documentation== |
==Documentation== |
||
− | * |
+ | * [http://web.mit.edu/kerberos/krb5-current/doc/krb_build/index.html Building Kerberos V5] describes how to build and install MIT Kerberos. |
− | * |
+ | * The [http://web.mit.edu/kerberos/krb5-current/doc/ documentation site] contains administrator and user documentation, and some information for developers; this documentation can help in understanding the product. |
− | * |
+ | * The [[Glossary]] is a quick index of acronyms and terms related to Kerberos, which you may come across while reading the code. |
+ | * [[Plugin development]] notes, pointers, tips, etc (needed!) |
||
==Mailing lists== |
==Mailing lists== |
||
Line 11: | Line 11: | ||
* [http://mailman.mit.edu/mailman/listinfo/krbdev krbdev@mit.edu] is the primary list for developers of [[MIT Kerberos]]. |
* [http://mailman.mit.edu/mailman/listinfo/krbdev krbdev@mit.edu] is the primary list for developers of [[MIT Kerberos]]. |
||
− | * [http://mailman.mit.edu/mailman/listinfo/ |
+ | * [http://mailman.mit.edu/mailman/listinfo/kfwdev kfwdev@mit.edu] serves a similar purpose for [[Kerberos for Windows]]. |
+ | * [http://mailman.mit.edu/mailman/listinfo/cvs-krb5 cvs-krb5@mit.edu] receives all krb5 commit messages and allows developers to track all changes made to MIT Kerberos. |
||
+ | * [http://mailman.mit.edu/mailman/listinfo/krb5-appl-commits krb5-appl-commits@mit.edu] receives all krb5-appl commit messages and allows developers to track all changes made to the MIT Kerberos applications. |
||
* [http://mailman.mit.edu/mailman/listinfo/krb5-bugs krb5-bugs@mit.edu] is notified when a [[ticket]] is created or updated. This list helps track bugs and feature requests. |
* [http://mailman.mit.edu/mailman/listinfo/krb5-bugs krb5-bugs@mit.edu] is notified when a [[ticket]] is created or updated. This list helps track bugs and feature requests. |
||
* krbcore@mit.edu is a private list for [[Krbcore]]; send mail to this list if you need to contact the core team. |
* krbcore@mit.edu is a private list for [[Krbcore]]; send mail to this list if you need to contact the core team. |
||
* krbcore-security@mit.edu is the point of contact for security problems with MIT Kerberos. |
* krbcore-security@mit.edu is the point of contact for security problems with MIT Kerberos. |
||
− | |||
==Source code== |
==Source code== |
||
− | The MIT Kerberos sources are in a [[Subversion]] repository. |
||
+ | * [[Getting source code]] |
||
− | |||
− | * http://anonsvn.mit.edu/svn/krb5 provides web access to the entire repository. |
||
− | * http://anonsvn.mit.edu/svn/krb5/trunk provides access to the current development version of MIT Kerberos. |
||
− | * svn://anonsvn.mit.edu/svn/krb5 provides read-only [[Subversion]] access to the repository. |
||
− | * [http://isda-maven1.mit.edu/source/krb5/ Opengrok] provides an interface that allows you to search for the definition or usage of a specific function. |
||
− | * [[Committers]] have access to a URI that allows them to commit changes to the repository. |
||
==Bug tracking== |
==Bug tracking== |
||
* http://krbdev.mit.edu/rt/ is the interface to the bug tracking server. |
* http://krbdev.mit.edu/rt/ is the interface to the bug tracking server. |
||
− | * Log in with user name guest and password guest. |
+ | * Log in with user name guest and password guest. (or use the guest login button) |
* See {{trunkref|doc/procedures.txt}} for some information on bug states. |
* See {{trunkref|doc/procedures.txt}} for some information on bug states. |
||
− | ==Jabber== |
||
+ | == Instant messaging == |
||
+ | |||
+ | [[Developer chat]] |
||
+ | |||
+ | == Lore == |
||
+ | |||
+ | You may find relevant accumulated lore in [[:Category:Lore]]. |
||
+ | |||
+ | == For committers == |
||
− | The core team and some fairly active developers use a jabber room for instant message chat. The goal is to have kerberos developers around the world available to answers each others' questions and to engage in real-time design discussions. If you are a reasonably active developer and wish to join this chat, contact a core team member for details. |
||
+ | If you're a committer, you should also look at [[committer resources]] for additional information. |
Latest revision as of 16:39, 6 December 2012
This page lists resources that developers use on a regular basis. One goal of the page is to help those beginning to track the project know what they may be interested in looking at.
Contents
Documentation
- Building Kerberos V5 describes how to build and install MIT Kerberos.
- The documentation site contains administrator and user documentation, and some information for developers; this documentation can help in understanding the product.
- The Glossary is a quick index of acronyms and terms related to Kerberos, which you may come across while reading the code.
- Plugin development notes, pointers, tips, etc (needed!)
Mailing lists
Much of the discussion of new proposals, discussion of what direction to take the product and answering of questions takes place on mailing lists.
- krbdev@mit.edu is the primary list for developers of MIT Kerberos.
- kfwdev@mit.edu serves a similar purpose for Kerberos for Windows.
- cvs-krb5@mit.edu receives all krb5 commit messages and allows developers to track all changes made to MIT Kerberos.
- krb5-appl-commits@mit.edu receives all krb5-appl commit messages and allows developers to track all changes made to the MIT Kerberos applications.
- krb5-bugs@mit.edu is notified when a ticket is created or updated. This list helps track bugs and feature requests.
- krbcore@mit.edu is a private list for Krbcore; send mail to this list if you need to contact the core team.
- krbcore-security@mit.edu is the point of contact for security problems with MIT Kerberos.
Source code
Bug tracking
- http://krbdev.mit.edu/rt/ is the interface to the bug tracking server.
- Log in with user name guest and password guest. (or use the guest login button)
- See
doc/procedures.txt
(raw | annotated | history) for some information on bug states.
Instant messaging
Lore
You may find relevant accumulated lore in Category:Lore.
For committers
If you're a committer, you should also look at committer resources for additional information.