Ä PVT_SAVED (2:291/1934) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ PVT_SAVED Ä
 Msg  : 103 of 108                          Uns Loc                             
 From : Gilles Hemberg                      2:291/1934      07 Aug 98  13:15:00 
 To   : All                                                                     
 Subj : ProBoard development                                                    
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Hi All,

Belw you will find my suggestion for the further development of ProBoard. I want
to state explicitely that no matter what path will be chosen for the further
development, I will continue to give as much support as I possibly can.

-----8<-----------------------------------------------------------------------

===================================
PROBOARD DEVELOPMENT PROPOSAL v0.01
===================================



GENERAL
=======


1. Ties to ProBoard
-------------------

All developers will contribute to the development on a free basis. This does not
mean they will not be rewarded for their work! It simply means the developers
are free to enter and leave the "scene" as they please.

Whenever a developer leaves the scene, he will lose all ties he/she may have had
with the developper's scene.



THE TEAM
========


1. Definition
-------------

The development of ProBoard would be taken care of by a "team". The team will
handle the following aspects of development:

* Programming
* Distribution
* Support / Public relations

Each of these 3 aspects will be taken care of by a separate "workgroup". The
work of these workgroups will be described below in more detail.

The team will be split in 2 major parts:

* Insiders
* Outsiders

The "insiders" will explicitely be part of the development team and will have a 
designated role in the development. The "outsiders" will contribute to the
development without having a designated role in the team (for example people who
provide various code snippets to help the insiders; see further).


2. Organisation of the insiders' team
-------------------------------------

The team will be organised in the following way. The scheme below is an example 
for 1 (one) workgroup and 2 members of that workgroup. More similar branches can
be added.


                             ++====================++
                             || Project supervisor ||
                             ++====================++
                                         |
                     +-------------------+
                     |
         +----------------------+
         | WorkGroup supervisor |
         +----------------------+
                     |
       +-------------+------------+
       |                          |
WorkGroup member #1     WorkGroup member #2


Please note that the vertical appearance of the scheme above does not denote a
different ranking in the team (everyone has 1 vote in the team)!

The set of workgroup supervisors (without the project supervisor) form the
"decisions group" for the project. The supervisor of the project is excluded
from the decision group to maintain integrity in the team. He/she can serve as a
moderator for discussions but can never take part in the votings of the
decisions group.


3. Decision making
------------------

Each decision which might influence the ideas behind the development and the way
ProBoard will evolve, have to be voted for by the "decisions group".

Decisions concerning members of the team (nominations, etc.), rewards for proven
work have to be taken by the complete insiders' development team.

Each POSITION in the organisation of the insiders' team will be awarded one
vote. Thus, if a single person occupies two positions, he/she will be awarded
two votes!

Control on the project is taken care of by the complete insiders' team.


5. Joining the team
-------------------

There is no requirement at all to join the outsiders' team: you do so if you
want to.

Basically everyone is free to join the insiders' team and no single member is
allowed to refuse a new member. However, new candidates are required to present 
themselves to the existing insiders' team members. The insiders' team members
can then send comments to the project supervisor. In case of serious problems,
the matter is presented to the complete team and a vote is taken to see whether 
or not the person should be allowed.

New candidates should report to the support/public relations workgroup.



PROGRAMMING WORKGROUP
=====================

The workgroup supervisor organizes the programming work among the team of
programmers. He collects all the parts and maintains close contact with the
project supervisor.

The workgroup members will each receive an assignment from the workgroup
supervisor and will periodically report back to the supervisor.



DISTRIBUTION WORKGROUP
======================

The workgroup supervisor will see to it that the distribution of the software
and the information related to the project is distributed correctly. This
workgroup might consist of only 1 member...



SUPPORT/PUBLIC RELATIONS WORKGROUP
==================================

This workgroup will handle all questions from users, give bug-reports to the
workgroup supervisor. This workgroup will maintain all kinds of information
sources (web-sites, etc.).

-----8<-----------------------------------------------------------------------

Bye!

__/ Data \______________________________
| Fido 2:291/1934                      |
|--------------------------------------|
| e-mail: apa@mail.dma.be              |
| WWW   : http://www.chbbs.home.ml.org |

And the most important is:
... You can't get out more than you put in

--- GoldED/386 2.50+
 * Origin: The Church bbs (+32-9-2213212) (2:291/1934)