I don't see a link from the project policy on the k5wiki to code change/integration policy. So I do not know if a code review is necessary and what sort of testing is expected.
- There is not a formalized code review policy. Certainly requesting specific code review as part of the community review of a project would be fine. --SamHartman 12:08, 4 April 2008 (EDT)
Submitting a project for review needs work
let no one else's work evade your eyes...
You don't have to copy it, but how do other opensource entities manage it? Some of them hide this information from the general public on their wiki pages -- does Kerberos want this to appear to non-members? Come to that, I don't see a "membership" aspect to the wiki. That might be how other opensource groups control access to the ability to suggest new projects.
- The Wiki cannot send out mail. The procedure is correct, but the text on the project page assumes that you actually follow the directions and send the mail. --SamHartman 12:08, 4 April 2008 (EDT)
LaTex seems to manage this on Project Development, to which anyone can subscribe.
MySQL has a pretty slick site. I didn't delve into it, but their policy might be something like requiring potential developers to pass a certification test. They also have a very nice form page.