What about attachments? Where can I store them? Did you get them Joao?
I will put them inline:
Eventum specification
Table of Contents
Overview
Permissions and roles
Glossary
Abstract
This document tries to specify Eventum bug-tracking system.
Overview
Aplication can be used to get feedback from clients and to manage internal
process of developing team. In such case system can be used by "very open"
products, that are revealing everything that concerns product and by close
teams, that want to reveal only part of information about project and
project status. Eventum should handle many scenarios. The purpose is to
have one application to manage customer support, bug tracking, feedback,
and change request process.
Permissions and roles
In this section is presented Eventum permission schema.
All users in the system can be divided in two main groups. Internal users
and External users. Internal Users are members of the team. They can see
all internal materials. External users are not permitted to see internal
materials. They can see only materials that were decided to be public. By
default all materials produced by external users are public. As summarize
we can say that there are two areas public and internal. External users
can access only public area . Internal users have access to both -
internal and public.
There are two types of access: read, write, delete. "write access" means
editing materials and adding new materials.
Internal users can have following roles:
* Administrator
* Manager
* Standard user
Glossary
internal user
user that is a member of project team. Has access for project internal
information.
external user
user that is not a member of project team. It can be customer, user of
the product. He cannot see internal project data.
material
It is any element that contains some information. It can be issue,
issues list, issue field, user properties. Whole issue with all its
associated data is called material. Each issue property is called
material. It is general term for element that contain any data.
Marcin Slusarczyk
Message from "Joao Prado Maia" <jpm@stripped> received on 2004-03-03
17:12
2004-03-03 17:12
"Joao Prado Maia" <jpm@stripped>
To: <eventum-devel@stripped>
cc: (bcc: Marcin Slusarczyk/PLCRC/ABB)
Subject: FW: eventum - permissions & roles
Forwarding this email so we have it archived in the list
-----Original Message-----
From: marcin.slusarczyk@stripped [mailto:marcin.slusarczyk@stripped]
Sent: Wednesday, March 03, 2004 8:12 AM
To: Joao Prado Maia
Subject: eventum - permissions & roles
Hi Joao,
Here is my point of view on eventum permission schema. . I used docbook to
create it.
I do not understand what is the purpose of viewer and reporter role. This
is why I haven't included it in document.
I am going to implement such schema as you see in document. I am not good
writer but I hope you will understand. I can implement it by myself and
create my own branch of eventum. But I see many adventages of keeping
common head branch.
Do you have defined any code conventions for eventum?
Do we have common view of what should be implemented to eventum?
Marcin Slusarczyk--
Eventum Developers Mailing List
For list archives: http://lists.mysql.com/eventum-devel
To unsubscribe: http://lists.mysql.com/eventum-devel?unsub=1
Attachment: [text/html]
