[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SEUL: Task assignments

   Delivered-To: jfm@sidney.remcomp.fr
   Date: Thu, 26 Jun 1997 17:40:22 -0400
   From: Greg Bell <winston@atlantic.net>
   X-Mailer: Mozilla 4.01 [en] (WinNT; I)
   MIME-Version: 1.0
   X-Priority: 3 (Normal)
   References: <33B2C0A6.1D2C@convex.hp.com>
   Content-Transfer-Encoding: 7bit
   Content-Type: text/plain; charset=us-ascii
   X-UIDL: ec4aff283249402e25e7c4441a004efc

   Michael Peck wrote:

   > 1) Coding
   >         This one doesn't require a lot of explanation.

   > 2) Oversight/decision-making
   >         Someone has to be responsible for stopping the buck. There will always
   > be some disagreement over everything. Who will close the margin?

     This is the function of the steering committee.  The listees will make
   suggestions/debate/disagree and the steering committee will be seeing
   all this when the debate stales by repeating the same things over and
   over in different words the committee will take a vote amoung themself
   with one member of the committee being designated as the vote breaker
   (in case of even votes).  The results will then be presented to the list
   in the form of guidance.

   > 3) Debate/discussion
   >         This will always be necessary. I don't propose that SEUL be a
   > committee-decided project, but ideas and opinions should at least be
   > aired continually.
   > 4) Information gathering
   >         This includes reviewing products, contacting vendors and authors,
   > researching technical data (possibly on the behalf of coders), etc.
   > 5) Information dissemination
   >         This is a critical task, as we've already discussed. It includes
   > running the web page, maintaining the mailing list, responding to
   > inquiries, and eventually will involve technical support.
     To this end a web page is currently being set up by Juhan Siren at

     and according to Juhan it should be up and working on Monday other
   than that once there is a working version of SEUL available (maybe
   beforehand?) or at least some ground rules laid out announcement will be
   place in alt.linux.announcements and perhaps alt.linux.development

   > 6) Testing  

   >         This will be more important after a preliminary release. It can be
   > discussed more at a later date.
   >         I'm sure I've missed as many things as I've mentioned. I would like to
   > simply present some categories so people can begin to think of
   > themselves as having a task and belonging to a particular group (or
   > several). In this way, we (at least, I) can focus our efforts instead of
   > allowing ourselves to be distracted.
   >         The inital-adoption phase is almost over. Can we put pour some
   > organizational concrete? It's going to be essential eventually, and
   > hopefully if it's done sooner it will accelerate the development
   > process.
   > PS I'm not talking about assigning offices or engaging in politics. I'm
   > using 'organization' in a fundamental fashion to describe coordination
   > of efforts. I also know that I'm not the first to suggest this; I'm just
   > lending the weight of my voice to it.

    Excellantly put and this is one reason that the steering committe was
   establish each of the steering committee will be the control point, if
   you will, for the various areas that need to be considered (members may
   be added as needed).


There is a seventh task: propaganda.  Seul MUST be on CD if we want to
reach our target, to interest a CD editor we need to have people
waiting for SEUL so we must make SEUL known.

			Jean Francois Martinez

==================== The Linux.  Use the Linux, Luke! =======================

Simple End User Linux Mailing list
To be removed from this mailing list send a message to majordomo@txcc.net
with the line
unsubscribe seul-project
in the body of the letter.