Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/to-do-rules.html
Дата изменения: Wed Apr 13 18:07:51 2005
Дата индексирования: Sun Apr 13 22:50:56 2008
Кодировка:
Поисковые слова: voyager 2

DFS To-Do list rules

DFS Department
DFS projects To-Do lists management

HOME

INDEX

HELP

NEWS

DFS projects To-do lists rules and recommendations

Each DFS project has to manage action items, i.e. create and update his own To-Do list.
These lists are all accessible from the specific DFS Department Home Pages (select one project).

In practice, any DFS Department member can modify any DFS Department To-Do list.

Only "medium-term" actions -i.e. actions to be performed in the next days or weeks- are to be reported here; short-term actions are by definition to be performed very quickly, so it's not useful to manage them with the following procedure; long-term actions are generally rather tasks which are to be defined in a DFS component schedule.

Each To-Do list has to be described via 2 files:

Current open action items must be described in a standard open action items text file.
Each time an action item is closed or cancelled, its description has to be moved into another standard text file.

These 2 files must be named : XXX-to-do-open.txt and XXX-to-do-close.txt where XXX is a standard denomination for the DFS component/project.

A To-Do list contains information about action items to be done.
It can also contain reference to a bug report or a change request, since a fix and a change implementation also corresponds to an action item. Anyway, in that case, just give the SPR number and a short-description here: the complete description (bug symptoms, release reported, worklogs, ...) must be located in Action Remedy only.

A shell command called webcheck is available to archive or check-out files on/from a DFS Department shared directory. Each time a file is checked out by a DFS group member, a lock is set, disabling other members to retrieve it as long as it is checked out.

The 2 To-Do list files must be regularly updated by each DFS project manager, in order to be reviewed during every corresponding DFS bi-monthly project meeting held with the DFS Department Head.

Please, apply the following procedure:

Install the webcheck command.
go to a directory you wish to edit/update your To-Do list file(s). It can be any one, even /tmp as these files are temporarily copied on your machine : the reference versions are always located on the DFS Department shared directory.
then, simply type:
webcheck
to get some details about how the command works: it will give you some help about archive, check-out or list the content of the DFS Department shared directory.
type:
webcheck -l -todo
to get the current reference list of To-Do list files located.
if you get some "permission denied" error message when accessing the DFS Department repository, please ask your system administrator.
If you don't understand what a project abbreviation (used for naming those files) means, go to the standard abbreviations list defined for DFS Department.
in any case, you have FIRST to check-out the file you wish to update, then update it locally (using any text editor), and finally check it in. It means that you will not be able to archive a file already archived (and locked or not).
If a file has already been checked out by someone else (without having been archived since then), you will get a warning message.

In most of the cases, it is 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.
Run:
webcheck -l -todo
to see the current classification.
If you wish to create a To-Do list for a new DFS component or project, please contact Karim (khaggouc@eso.org, phone 6507).

DFS DepartmentDFS projects To-Do lists management

DFS Department
DFS projects To-Do lists management