RE: [suse-linux-uk-schools] OSE Discussion structure - moving forward
Would it not be sensible to organise another event pretty soon with an action plan and get some lead names against those actions ?
The reason I am pushing the use of sourceforge to manage the project, is that we can get the core people (who want to take an active role) listed. Once we are at this stage, we can start assigning tasks to people and then each 'job' has an owner. These tasks would not (in the first instance) be programming/writing, but things like 'sort out who is to host it', 'sort out the domain name', 'formulate a list of aims for OSIE', etc. Once a task has an owner to coordinate it, it is likely to be discussed and resolved, without the discussions just 'drifting off'. The problem with free-for-all mailing lists, is (as you say) it is too easy for the detail to be lost, and often (in my experience on lists in the past) subjects 'drop out' of favour, without being resolved ... So - when sourceforge is up and running, I suggest all key people who are prepared to spend a little time doing something, get on the mailing list, and we start to discuss the structure of the project. We would first (I guess) start by trying to list appropriate sub-project areas, so that tasks can be allocated. This would be the key functions, required - I don't really want to start discussions here (but I will ?), but this could include things like the server (hosting, web technology, etc), web site itself (structure/content), PR, policy, etc. This way, people have something to own and work towards, and the thing moves forward. Kevin.
I would say do both i.e. get the sourceforge thing up and running but also have another face-to-face before very long. But the basic points that Kevin makes here are absolutely right for any collectively run project of this kind. On Wed, 21 Mar 2001 kevin.taylor@powerconv.alstom.com wrote:
Would it not be sensible to organise another event pretty soon with an action plan and get some lead names against those actions ?
The reason I am pushing the use of sourceforge to manage the project, is that we can get the core people (who want to take an active role) listed.
Once we are at this stage, we can start assigning tasks to people and then each 'job' has an owner. These tasks would not (in the first instance) be programming/writing, but things like 'sort out who is to host it', 'sort out the domain name', 'formulate a list of aims for OSIE', etc. Once a task has an owner to coordinate it, it is likely to be discussed and resolved, without the discussions just 'drifting off'.
The problem with free-for-all mailing lists, is (as you say) it is too easy for the detail to be lost, and often (in my experience on lists in the past) subjects 'drop out' of favour, without being resolved ...
So - when sourceforge is up and running, I suggest all key people who are prepared to spend a little time doing something, get on the mailing list, and we start to discuss the structure of the project.
We would first (I guess) start by trying to list appropriate sub-project areas, so that tasks can be allocated.
This would be the key functions, required - I don't really want to start discussions here (but I will ?), but this could include things like the server (hosting, web technology, etc), web site itself (structure/content), PR, policy, etc.
This way, people have something to own and work towards, and the thing moves forward.
Kevin.
-- Roger Whittaker SuSE Linux Ltd The Kinetic Centre Theobald Street Borehamwood Herts WD6 4PJ ---------------------- 020 8387 1482 ---------------------- roger@suse-linux.co.uk ----------------------
participants (2)
-
kevin.taylor@powerconv.alstom.com
-
Roger Whittaker