On Wednesday 10 May 2006 05:20, scsijon wrote:
Let us split our community away to handle tasks such as:- a) assist with small useage \ new idea packages and unexpected extension requirements to existing packages.
b) assist as we do now in "field" testing through the beta
program, but not only SuSE's but other packages that need larger variations of testers.
c) assist as we do now in the problem fix process. d) documentation, not only "how to use" types, but "using
this with these extensions this way allows you to do this" as well as "this plus this plus this and either this or this but not including this" makes a "qqqq" server. I, for example have decided to spend my available time this year in creating a "Mini-Command Useage" Manual that lists commands, what they are, their extensions plus a number of standard used matrixes (such as ls -la) and what they give you back. It will be able to be printed out as a mini-manual (a5/2 flip) or a cardfile format for pda's etc. But I will say more on this when I have my thoughts in propper order and under an appropriate subject header (of which this is not).
e) design and create the direction specifications of what we
think users will be wanting in the near future.
f) provide support to our communities across the world by
assisting with technical translation of ideas and "command formats"
g) marketing/promotion h) writing code/patches I like this idea of splitting things up - but I think we need some kind of formalized leadership/organization (call it what you want). I don't necessarily believe in "leaders manifesting themselves naturally". I think we need to form some kind of teams - with (elected) leads. And a wikipage where you can see who are members of a certain team and how to join - and what the tasks/responsibilities are, etc. Of course everyone who's not in a team would be free to contribute in any way he/she pleases. cb400f