Changes between Version 3 and Version 4 of SystemAspects


Ignore:
Timestamp:
Aug 19, 2013, 9:55:48 AM (7 years ago)
Author:
pesei
Comment:

Some corrections and improvements (links etc)

Legend:

Unmodified
Added
Removed
Modified
  • SystemAspects

    v3 v4  
    1 = flexpart.eu System =
     1= Short description of the FLEXPART.eu system =
    22
    3 flexpart.eu consists of two "Systems"
     3Two software systems are running at FEXPART.eu
    44
    5   * the [wiki:SvnFlexpart svn]
    6   * trac
     5  * [wiki:SvnFlexpart svn], source-code repository and version control system.
     6  * trac, web-based software project management and bug/issue tracking system
    77
    8 The svn is referenced within trac but there is a different user management.
     8The svn is used as a back-end in trac but its user management is separate.
    99
    1010Within trac there are two major part
     
    1313  * the ticket system
    1414
     15Within the wiki pages can be created and modified (only EXCEPTION is the frontpage).
    1516
    16 Within the wiki pages can be created and modified (only EXCEPTION is the Frontpage, because its part of the System and not the WIKI).
     17Please look at the naming schema as visible from the TitleIndex and name a new page according to this convention, so that it appears in the right place in the TitleIndex.
    1718
    18 Please look at the naming schema and name a new page according to this convention. [[BR]]
    19 (So it will pop up in the right place in a Report).
    20 
    21 The instruction how to use trac is documented in the wiki (use '''Index''' on top of the wiki pages to find this pages)[[BR]]
    22 or have a look at the [http://trac.edgewall.org/wiki/0.11/TracGuide official Guide].
     19The instruction how to use trac is documented in the TracGuide as well as the Trac wiki pages which can be located through the TitleIndex.
    2320
    2421== Procedures ==
     
    2724All developers and the admin are notified automatically.
    2825
    29 For any communication with/between developers, we would also propose to use the ticket system. This will assure that everything is documented and archived for further reference.
     26For any communication with/between developers, ZAMG would also propose to use the ticket system. This will assure that everything is documented and archived for further reference.
    3027
    31 If a proposed change is considered minor, we will implement if no developer disagrees within 1 working day.
     28If a proposed change is considered minor, we (ZAMG) will implement if no developer disagrees within 1 working day.
    3229
    33 If a proposed change is considered not minor, we will implement if no developer disagrees within 3 working days, and at least 3 developer agree.
     30If a proposed change is considered not minor, we (ZAMG) will implement if no developer disagrees within 3 working days, and at least 3 developer agree.
    3431
    3532The system is maintained by ZAMG. As a matter of internal IT security policy, administrator rights are limited to ZAMG IT staff.