 | |
 | |
 | |
 |
 |
 | |
 | |
 | |
 | |
 | |
 | |
| |
Project Requirements
Utility or theoretical interest
XCF projects must either be useful to the general computing community or be of defensible theoretical interest.
Scope and completability
In our experience, one year is less than it seems due to the pressures of schoolwork, outside employment, and shortcomings in the wheel. So scope will be restricted keeping that in mind. Of course, different people work at different rates, so there is always room for developers to expand the scope of their projects once demonstrable progress has been made on the stated goals. Scope requirements do not impinge on the possibilities of a project if the project is properly designed. XCF projects must, therefore, be properly designed.
Finally, projects must focus on clearly defined goals.
Progress
Regular progress must be made. Members are expected to police themselves. In the event of unsatisfactory effort toward the member's stated project or peripheral projects (hacks unrelated to the stated project, system maintenance, etc.), then members are expected to excuse themselves from an active role in XCF until they once again have time to contribute to the organization. This will be enforced. We are understanding of temporary scheduling difficulties and we like to keep our members happy and our organization at the forefront of technology. Part of that is maintaining a high level of productivity. Proposals Project proposals should be submitted to director@xcf.berkeley.edu. After the proposal is reviewed by the Director it is submitted to the general membership for review. Project proposals must address the preceding criteria (1-3). We will not accept hopelessly overscoped projects or applicants who will not contribute positively to our environment.