Warning: Can't synchronize with the repository (The 'repository_dir' has changed, a 'trac-admin resync' operation is needed.). Look in the Trac log for more information.

Notes

Due to the fact that most of the project resources were not fully operative and/or spreaded on different systems (VPS, berlios.de, non-active), this Project Audit contains much more fulfilled tasks than it would contain usually. Within a standard Project Audit, the issues will be filed and assigned.

Issues

Actual Overview of Resulting Issues, grouped by owner, ordered by priority.

Schevo Project Audit Results

Get Required Tools

Installing an SVN Client, and SCP Client and a SSHKey Generator (On Windows, used TortoiseSVN, WinSCP and Putty) is trivially annoying.

Tasks: #50

Get Access Rights

Starting Point as Project Admin:

  • The project infrastructure depends on manual user-management.
  • No automated usermanagement mechanisms available
  • No documentation available

Fulfilled Tasks:

Role Developer:

  • Ask on the Mailinglist for access rights.

Tasks: #59, #62

Get an System Overview

Starting Point:

  • There was no Centralized Overall Schevo System Overview available.
  • Module and Package reference not hierarchical (Pudge generated).

Initialized Tasks:

With milestone:restructure, an organized attemp was made to document and restructure the Schevo Subsystems.

This was interupted by an uncoordinated (without prior verification, see Structural Changes) project structure reorganisation. This Action and the resulting issues (including serveral "BROKEN") are documented within Schevo Split.

Tasks: #39

File an Issue

Starting Point as Project Admin:

  • The project had no operational Issue Tracking System available.

Fulfilled Tasks:

  • Installted Trac on the existent Orbtech VPS
    • documented the installation

Role Developer:

  • Filing Issues within trac is easy

Tasks: #46, #13, #63, #64, #65, Trac Audit

Retrieve Central Code

The initially retrieved code (on which the Pudge development work was done) was broken by the Schevo Split.

For the Schevo Evaluation, the following code was retrieved (after deletion of the old installation): 

svn+ssh://orbtech.com/var/local/svn/schevo/Schevo/trunk Schevo

svn+ssh://orbtech.com/var/local/svn/schevo/SchevoQt/trunk SchevoQt

Tasks: #40, #41

within Schevo: 

python setup.py develop

within Schevo Qt?: 

python setup.py develop

Tasks: #40

Commit Changed Code to Central Repository

This process is simple and straightforward when commiting to the SVN trunk (Trunk Development).

Several coding tasks from the Schevo Evaluation were fulfilled without problems, adding incrementally functionality without breaking existent behaviour.

The main problems are reactions from the existent team members, which have introduced Branch Development (not announced, similar to the introduction of the Schevo Split).

Tasks: #47, #49, #66

Claim Ownership of a Sub-System

To ensure efficient development of the Subsystem "navigator", the Subsystem Lead status was requested.

The request remained unanswered.

Create a Branch

Created a branch to develope an intitial Gtk based Schevo Navigator. It is expected that Schevo and Schevo Qt? must be altered, too.

SVN Repository on Server:

  • Following the Branch Development instructions with TortoiseSVN
  • Created a branch repository "Schevo Gtk?/branches/navgtk"
  • Created a branch repository "Schevo/branches/navgtk"
  • Created a branch repository "Schevo Qt?/branches/navgtk"

Tasks: #48, #49, #60

Retrieve a Branch

Following the instructions on Branch Development

  • create locally a directory "navgtk"
  • Retrieve branch repository to the local space "navgtk/SchevoGtk"
  • run "python setup.py develop
  • Retrieve branch repository to the local space "navgtk/Schevo"
  • run "python setup.py develop
  • Retrieve branch repository to the local space "navgtk/SchevoQt"
  • run "python setup.py develop

Convenience Scripts:

  • create a batch navgtk/develop.bat which executes all 3 "python setup.py develop"
  • create a batch navgtk/develop-revert.bat which recreates old development locations

Rating:

  • The effort to retrieve a branch which spans multiple Sub Systems? is too high

Tasks: #68

Commit Code to Branch Repository

This is trivial and non-critical.

Merging a Branch with the Central Repository

Following the instructions on Branch Development each of the involved Sub Systems? must be merged back:

Rating:

  • The effort to merge-back a branch which spans multiple Sub Systems? is too high

Tasks: #67, #69

Terminate a Branch

It was decided to not continue development within the "navgtk" branches.

Tasks: #71

Create a New Subsystem

Role Subsystem Lead:

  • The navigator should be available as a seperate Subsytem
  • Altough objected, the current active project structure will be used

Trying to create Subsystem Schevo Navigator, unclear how to proceed.

Created via TortoiseSVN repository browser but unsure the if procedure was correct.

Missing ID headers in source-files make verification difficult.

Tasks: #70, #72, #76

Backup

Getting a backup from the project data:

  • login via SSH shell
  • copied relevant data from different locations

Tasks: #73

http://schevo.org

Tried to access the project resources from the schevo.org domain, but they are not available there.

TRAC and other project infrastructure should be accessible directly on the schevo.org domain.

Tasks: #74, #75