Contents |
We need to define the tasks more clearly.
It became clear that the process we currently use to create the LSB specification is substandard. In particular, the PDF specifications do not scale. Our current process involves translating the DocBook to RTF, which are then rendered into PDF on Windows using Microsoft Word and Acrobat. For LSB 3.2, the Desktop PDF specs were delayed significantly, and we ended up doing a manual translation using OpenOffice.org for just the Desktop specs.
The state of the art for Docbook-to-PDF tools was significantly different in the past; the available tools could not create output that met the standards set by ISO. There have been a lot of new options recently. We should evaluate those options, and choose a new process if we can.
A rough proposed schedule for this project. When we anticipate that we will reach certain milestones. Also, if the project has an absolutely-must-be-completed-by date, mention it here.
| Milestone | Plan Date | Outlook | Comments |
|---|
No resources have been dedicated to this project.
No hardware has been dedicated to this project.
List of people who are working on the project and their roles.
| Name | Role |
|---|---|
| Jeff Licquia | Project Owner |
Tasks will map many-to-one to milestones. Tasks are specific actionable work items that need to be completed in order to reach a milestone
| Task | Owner | Status | Outlook |
|---|
| Task | Owner | Status | Outlook |
|---|
Tasks that can't be scheduled yet because they are waiting on some other task or external entity
| Task | Owner | Status | Outlook |
|---|
We need to collect data about the requirements for the output. It seems that, beyond the usual aesthetic concerns, we need to satisfy ISO.
The possibility exists that we may not be able to generate the specs with equivalent quality to MS Word and Acrobat. In that case, we may need to decide whether better process or better output is more important. If we choose better output, this could require that we purchase a high-end Windows system for the sole purpose of generating specifications. This would not be as much of a waste as might be expected; it would be a good idea to generate specs on a nightly basis, as we do for the other deliverables.
Jeff Licquia 13:52, 7 April 2008 (PDT)