I am loth to put my fat foot into the puddle developing about the question of
who does what.
However, if I understand correctly, Shachar fears that by undertaking to
manage the server he lays himself open to unending micro-management and
feeping creaturism directed by sundry members of the kommite... errr... vaad,
with rapidly rising costs, etc. I can well understand and identify with
Schachar's fears and concerns.
On the other hand, The Vaadc (I will not number them all, but you know who you
are), reasonably wants to have a say in what is or is not on the machine,
what subsystems are put in place and which are rejected, etc. This too, is
both reasonable and normal.
Now - unless someone wants to volunteer his time and effort to manage the
server (something I do NOT see happening, but if it does, I suspect it will
be both short-lived and very frustrating to the poor victi... volunteer, that
is) - this better be done by a competent company, chargin money for the
service. Shachar sent in a tender. Well, it was not a tender tender, but a
harsh tender. Some people (Nadav, inter alia) think that the wording is
derogatory, that Shachar is an abrasive bogeyman, and a martinet to boot.
They are probably right, but it is neither here nor there.
Here is my tender. Mind - it is NOT a tender to manage the server (since I
understand nothing in Linux or system management or anything of the kind).
And, to prevent any misunderstandings, Swiftouch (which also knows very
little about Unix/Linux/System/etc) will not accept or respond to an RFQ or
anything similar relating to this matter:
1. Ramp Up
1. A company shall be selected to _manage_ a existing server.
2. Said company shall be allotted a _TO BE DECIDED_ amount of
pre-paid hours of work to become acquainted with the system
3. A PO shall be issued by Hamakor to cover paragraph 1.2.
2. Ongoing/Steady-State
1. The company shall provide ongoing maintenance of a server
(currently, beak) for _TBD_ hours of work per month at a
rate
not to exceed US$_TBD_/hour.
2. A quarterly PO shall be issued by Hamakor for activities
covered
by paragraph 2.1
3. Should a need arise to exceed the pre-agreed amount of
maintenance work, a separate PO shall be issued by Hamakor
at its sole discretion.
3. Features
1. Additional features/functions shall be developed or added
only at
the express request of Hamakor and only upon the issuance of
RFP/Q by Hamakor.
2. The company undertakes to develop/add contracted functions
or subsystems for the Hamakor server only upon the explicit
issue of a PO by Hamakor, based on its P/PQ.
4. Arnie-clause
1. Termination as needed (I am not really interested in writing
legalese).
--
---MAV
Marc A. Volovic
Linguists do it cunningly
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
