Request for Change: Unterschied zwischen den Versionen

Aus WikiStar
Wechseln zu: Navigation, Suche
(REvisioning and description)
Zeile 1: Zeile 1:
 +
==Read me==
 +
===Why this?===
 +
Customers ask for features regularly. In the longer past some things were installed where they were needed. Then we changed to a policy wich aimed to keep all the servers set up the same way. Denial of requests happened more often. But the side effect was, that the same questions were investigated multiple times, as we lost track of the requests. So we will protocol them here from now on.
 +
===How it works===
 +
 +
====A new request====
 +
You have an incoming request that needs to be judged, copy both parts of the template source. Fill in the headlines and the link in the first part. Then fill the table with date, reason and contact address of the client.
 +
 +
Now inform the one that should decide about this entry.
 +
 +
====First decision====
 +
The decision taker will fill in the decision part of the entry and informs you that it is done.
 +
 +
====Client information====
 +
Time to tell the client what the decision is and why it was taken like this.
 +
 +
====It is asked again====
 +
(So it must have been denied or postponed until now.) Add an additional line to the table with your clients reasons to have it. Inform your client, about what was decided in the past.
 +
 +
====Escalate it again====
 +
You may escalate the request again if you feel that
 +
* your reason has changed the importance of the request (i.e. postfinance requires it to continue my payment processing module!)
 +
* there are more than 5 times the same reason given in a short period of time (ie. 1 request/month)
 +
* the reasons of denial are not valid anymore
 +
 +
 +
 +
 
==PHP==
 
==PHP==
 
===SSH2===
 
===SSH2===
Zeile 6: Zeile 34:
 
#* '''By:''' hja
 
#* '''By:''' hja
 
#* '''When:''' 23.09.2014
 
#* '''When:''' 23.09.2014
−
# '''Reason:''' security concerns (opening possible abusive ssh connections to other machines)
+
#* '''Reason:''' security concerns (opening possible abusive ssh connections to other machines)
 
# '''Workaround:''' [http://phpseclib.sourceforge.net/ phpseclib]  
 
# '''Workaround:''' [http://phpseclib.sourceforge.net/ phpseclib]  
  
Zeile 18: Zeile 46:
 
| 23.09.2014
 
| 23.09.2014
 
| [mailto:vincenzo.nicosia@hispeed.ch Vincenzo Nicosia]
 
| [mailto:vincenzo.nicosia@hispeed.ch Vincenzo Nicosia]
−
| own programming <br />(opening sftp connection to retrieve files twice per day with public key)
+
| own programming (opening sftp connection to retrieve files twice per day with public key)
 
| workaround looks good!
 
| workaround looks good!
 
|-
 
|-
Zeile 26: Zeile 54:
 
|}
 
|}
  
−
 
+
==Entry Template==
−
==Scope / Environment / Parent==
+
<pre>
 +
==Scope/Environment/Parent==
 
===Module Name===
 
===Module Name===
 
# '''Link:''' [http://google.com provide a link]
 
# '''Link:''' [http://google.com provide a link]
 
# '''Decision:'''  
 
# '''Decision:'''  
−
#* '''Result:''' coming with next Godmode update (ETA 05.2022)
+
#* '''Result:'''  
−
#* '''By:''' jre
+
#* '''By:'''  
−
#* '''When:''' 07.10.2014
+
#* '''When:'''  
−
# '''Reason:'''
+
#* '''Reason:'''
 
# '''Workaround:'''  
 
# '''Workaround:'''  
  
Zeile 42: Zeile 71:
 
! Customer Email
 
! Customer Email
 
! Motivation (why needed?)
 
! Motivation (why needed?)
 +
! Customer Feedback
 
|-
 
|-
 
|  
 
|  
 +
| [mailto:abc@def.xyz Customer Name]
 
|  
 
|  
 
|  
 
|  
 
|}
 
|}
 +
</pre>

Version vom 7. Oktober 2014, 15:10 Uhr

Read me

Why this?

Customers ask for features regularly. In the longer past some things were installed where they were needed. Then we changed to a policy wich aimed to keep all the servers set up the same way. Denial of requests happened more often. But the side effect was, that the same questions were investigated multiple times, as we lost track of the requests. So we will protocol them here from now on.

How it works

A new request

You have an incoming request that needs to be judged, copy both parts of the template source. Fill in the headlines and the link in the first part. Then fill the table with date, reason and contact address of the client.

Now inform the one that should decide about this entry.

First decision

The decision taker will fill in the decision part of the entry and informs you that it is done.

Client information

Time to tell the client what the decision is and why it was taken like this.

It is asked again

(So it must have been denied or postponed until now.) Add an additional line to the table with your clients reasons to have it. Inform your client, about what was decided in the past.

Escalate it again

You may escalate the request again if you feel that

  • your reason has changed the importance of the request (i.e. postfinance requires it to continue my payment processing module!)
  • there are more than 5 times the same reason given in a short period of time (ie. 1 request/month)
  • the reasons of denial are not valid anymore



PHP

SSH2

  1. Link: ssh2
  2. Decision:
    • Result: will not be installed
    • By: hja
    • When: 23.09.2014
    • Reason: security concerns (opening possible abusive ssh connections to other machines)
  3. Workaround: phpseclib
Request Date Customer Email Motivation (why needed?) Customer Feedback
23.09.2014 Vincenzo Nicosia own programming (opening sftp connection to retrieve files twice per day with public key) workaround looks good!

Entry Template

==Scope/Environment/Parent==
===Module Name===
# '''Link:''' [http://google.com provide a link]
# '''Decision:''' 
#* '''Result:''' 
#* '''By:''' 
#* '''When:''' 
#* '''Reason:'''
# '''Workaround:''' 

{| class="wikitable"
|-
! Request Date
! Customer Email
! Motivation (why needed?)
! Customer Feedback
|-
| 
| [mailto:abc@def.xyz Customer Name]
| 
| 
|}
Von „http://wiki.internet-license.net/index.php?title=Request_for_Change&oldid=314“