In particular, the new site must be designed to be accessible to various groups of users who have very different needs. Here is a starting point.
1. [[OpenAFS]] administrators
- 1. 1. easy access to the "best" binaries (and perhaps source) for their server and client platforms
- 2. easy access to documentation (man pages, admin guide, wiki, etc.)
- 3. bug reporting
- 4. mailing lists
+ 1. easy access to the "best" binaries (and perhaps source) for their server and client platforms
+ 2. easy access to documentation (man pages, admin guide, wiki, etc.)
+ 3. bug reporting
+ 4. mailing lists
2. [[OpenAFS]] client end users
- 1. 1. easy access to the "best" binaries for their client OS (perhaps auto-detected)
- 2. easy access to end user documentation
- 3. bug reporting
- 4. mailing lists
+ 1. easy access to the "best" binaries for their client OS (perhaps auto-detected)
+ 2. easy access to end user documentation
+ 3. bug reporting
+ 4. mailing lists
3. Senior managers and architects (CTO,CIO,...) of organizations performing long term planning for their organization who have doubts about the future and applicability of [[OpenAFS]] for their storage solutions OR who might want to fund development efforts
- 1. 1. case studies / success stories
- 2. architectural white papers
- 3. development road map
- 4. project status
+ 1. case studies / success stories
+ 2. architectural white papers
+ 3. development road map
+ 4. project status
4. Random individuals who want to know what this AFS thing is
5. Developers
- 1. 1. Source code downloads
- 2. [[WebCVS]]
- 3. RT access
- 4. Coding Style Guide
- 5. Volunteering
- 6. Development mailing lists
+ 1. Source code downloads
+ 2. [[WebCVS]]
+ 3. RT access
+ 4. Coding Style Guide
+ 5. Volunteering
+ 6. Development mailing lists
6. Governance and Communications
- 1. 1. Minutes
- 2. Newsletters
- 3. Announcements
- 4. Who Are We?
+ 1. Minutes
+ 2. Newsletters
+ 3. Announcements
+ 4. Who Are We?