Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/to-do-list/common-to-do-open.txt Дата изменения: Wed Jun 27 18:21:54 2001 Дата индексирования: Sat Dec 22 23:56:13 2007 Кодировка: Поисковые слова: http astrokuban.info astrokuban

================================
* LIST OF OPEN ACTION ITEMS *
================================

Last update: Wed Jun 27 16:21:54 MET DST 2001

----------------------------------------------------------------------------------------------
ID Chronological number (to be updated manually).
Comp Name of the DFS project or component (SAF, VCSOlac, FrameIngest, DO, RBS,
-pipe, ...). In most of the cases, it's enough to have a To-Do list
per DFS project (e.g. SAF). However, project managers may decide to have a
To-Do list per component, if appropriate.
Origin Meeting name/review/date during which the action item was originated.
Type ACTION= for a normal action item;
BUG= for an item related to a bug report;
CHANGE= for an item related to a change request.
Prior Priority= LOW, HIGH, CRITIC
DueDate Either a specific date (YYYY-MM-DD) or a specific new release (in that case,
corresponding date has to be specified in associated DFS component schedule).
Resp Responsible name; even if several persons can be involved in the action item, one
should be responsible for follow-up.
Status INIT= to be started; SUSPEND= suspended, waiting for external inputs;
PROGRESS= action in progress.
Description
Detailed description. For BUG and CHANGE, specify the SPR number and a short
description: the complete description of the SPR must be found in Action Remedy.

----------------------------------------------------------------------------------------------
ID Comp Origin Type Prior DueDate Resp Status
Description
----------------------------------------------------------------------------------------------

0001 DICB bleibund/Aug 2000 CHANGE HIGH 2001-02-05 SB PROGRESS
Review and rewrite DICD2.0 draft. Submit to DICB afterwards.
PROGRESS: Draft was submitted to bleibund.
PROGRESS: Reviewed by bleibund and submitted again.
0004 FITSIO ? ACTION HIGH ? JKN PROGRESS
FITS I/O Java Package: Take decision about which package to use +
policy + what to possible implement (JKN, MPE).
0005 FITSIO ? ACTION HIGH ? JKN PROGRESS
FITS I/O C/C++ Package: Take decision about package to use + policy
+ what to possible implement (JKN, MPR, ...).
0006 DFSLANG ? ACTION HIGH ? JKN/KHA PROGRESS
Provide document with an evaluation of the usage of programming
languages within DFS, and recommandations for future policies. The
document is being written.
0007 UTIL ? ACTION HIGH ? JKN PROGRESS
Check man-pages (documentation) for C++ Util packages. Provide User Manual + WEB Page with
overview.
0008 PCC ? ACTION HIGH ? JKN PROGRESS
Python Common Components: Provide User Manual + WEB page with overview.
0009 RW ? ACTION HIGH ? JKN PROGRESS
Take decision concerning future policy of usage of Roguewave within DFS. Report provided to
MPE.
0010 DFSLOG ? ACTION HIGH ? JKN PROGRESS
Analysis of the current situation in conneciton with logging within DFS is provided for
MPE. Take decision of appropriate actions for future streamlining of the logging within DFS.
0011 CSW-PLTF ? ACTION HIGH ? JKN PROGRESS
Make analysis of a future common SW infrastructure to be used as framework for developing
DFS applications.
A presentation of the ACS was done, it should be decided whether to use this as a common
infrastructure.
0012 ESO-XML ? ACTION HIGH ? JKN PROGRESS
Formats and standards for ESO XML documents should be provided. The following should be
defined: Std. ESO XML Document Header, Logging File Format, Parameter File Format, DID Format.
Document is currently being written.
0013 DICB sbogun/June 2001 CHANGE HIGH 2001-07-05 SB PROGRESS
Check-in all QC dictionaries into CMM.
PROGRESS: FORS dictionary checked in. ISAAC and UVES still missing.