From time to time, developers define large development efforts that are complex and/or large in scope and/or require developer cooperation for the project duration.
An example for a development project might be the Out of Band project executed by Andrew Deason (Sine Nomine Associates).
Theoretically, each project should have clear specifications, approved by the current Technical Advisors ("Gatekeepers") and should have mapped an overall path how the specifications will be translated into functionality. This preparatory planning is crucial so that, upon completion of your work, the project results end up being suitable for being merged into the OpenAFS main branch. Without such planning and approval by the Technical Advisors, the developer(s) run(s) danger of investing much blood, sweat, and tears writing code that turns out to be incompatible with the OpenAFS main branch and/or is not supportable there. We cannot emphasize enough: it is IMPERATIVE to plan projects and get approval for them prior to actually beginning to write code!
If you identified the need for a future development project, please write a brief description, the need(s) it is intended to meet, and map out a rough plan how you believe the coding work should be executed. If you are unable to do such a write-up but can identify a general need, please identify that need "as-is." In any event, we wait to hear from you and welcome your suggestions and contributions! Thank you.