[166] in Kakapo Windows Team
Making changes to the container request form, access request
daemon@ATHENA.MIT.EDU (Joseph Calzaretta)
Thu Oct 30 11:59:31 2003
Message-Id: <5.1.0.14.2.20031030111155.02d6dd38@hesiod>
Date: Thu, 30 Oct 2003 11:59:26 -0500
To: windows-server-www@mit.edu, kakapo@mit.edu
From: Joseph Calzaretta <saltine@MIT.EDU>
Cc: pismere-ops@mit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Dear Windows Server Web Masters (and Kakapo),
I'd like to request that the pismere-ops list (or, if not, then just
container-request) have write access to the specific files in
/mit/windows/server which directly pertain to the Win.Mit.Edu domain. This
way if we have the need to make quick changes, we can do so. There are
parts of these pages which change from time to time, -especially- the email
that gets generated and sent to container-request. While we wouldn't mess
with the front end without submitting a request, the behind-the-scenes
stuff with cgiemail needs to accessible to us more directly.
As we move our official documentation from the pismere locker to the
windows locker, this kind of access will become more important. For
example, when we roll out changes to the domain, such as new functionality
or deployments, we need to update the on-line documentation in a
synchronized fashion. While the form of the "before" and "after" documents
should be completely up to you, the timing and content needs to be at our
disposal as well. This becomes more vital when we are forced to deploy an
emergency hotfix to the domain (like we did with MS03-026 and MS03-039)
where the decision is made quickly.
I think we could all agree that unless we (pismere-ops) were altering
something only we care about (like the text of the auto-generated email to
container-request), or making a synchronized update of both functionality
and documentation, we would not exercise the access and instead just submit
a request. And whenever we do make changes we would immediately inform
windows-server-www so that nothing changes out from under anyone.
If it's decided that we can't have this level of access, then we could
really use a well-documented process for requesting changes and a
commitment that, in emergencies, these changes could be made at a moment's
notice.
In the particular case of the container request form, there is a
compromise. You could point cr/2c.html at our email .txt document.
That is, in 2c.html, change this line:
<form method="post"
action="http://web.mit.edu/bin/cgiemail/afs/athena/org/i/is/help/windows/server/cr/2c.txt">
to
<form method="post"
action="http://web.mit.edu/bin/cgiemail/afs/athena/project/pismere/support/cont-req/2c.txt">
This way we could change the text of the auto-generated email without
touching the /mit/windows/server directory.
-----
As an aside, I'd like to ask that whoever does maintain the pages read
through the html and make sure that all references to Oliver's afs home
directory are changed properly.
(e.g., in 2c.html
<input type="hidden" name="success"
value="http://web.mit.edu/othomas/www/win/3c.html">
to
<input type="hidden" name="success"
value="http://web.mit.edu/windows/server/cr/3c.html">)
------
Anyway, thanks to all for your time (long email, isn't it) and assistance
in this matter. Have a good day.
Yours,
Joe Calzaretta
