Request for Change

Aus WikiStar
Wechseln zu: Navigation, Suche

Why this?[Bearbeiten]

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 and decided multiple times, as we lost track of the requests. So we will protocol them here from now on.

With the information gathered we can now see

  • what clients want
  • popularity of a request
  • why the clients need it
  • which information was available at the time of the decision
  • why the decision was taken like this
  • if reconsidering is needed


Apache[Bearbeiten]

PUT method[Bearbeiten]

  1. Link: Configuring your WWW server with the PUT method
  2. Decision:
    • Result: will not be installed
    • By: hja
    • When: 07.2014
    • Reason: we have no security layer for PUT as we have for GET and POST, so it would be a major change
  3. Workaround: FTP protocol offers the same methods. Programmers should use this protocol instead.
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
19.07.2014 dna older request, source is unknown WebDAV related

PHP[Bearbeiten]

.htaccess: Allow Options and php_flag[Bearbeiten]

  1. Link: .htaccess Dos&Don'ts
  2. Decision:
    • Result: Cannot be done
    • By: SL
    • When: 10.03.2015
    • Reason: This security related restriction was first introduced after the BIG INCIDENT (Summer 2013). These settings definitely overwrite server settings.
  3. Workaround: Fix it manually.
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
10.03.2015 Support Staff - Ease of updates triggerd from different sotwares backend (i.e. ownCloud, Joomla!) Staff is sad.

PCRE - outdated versions of Perl Compatible Regular Expressions[Bearbeiten]

  1. Link: [1]
  2. Decision:
    • Result: Will be redecided if given workaround does not work
    • By: jre
    • When: 10.10.2014
    • Reason: PCRE updates need a PHP recompilation. With the setup of PHP 5.4 and 5.5 a mistake happend to use there oudated versions (7.2 as of 2007).
  3. Workaround: Use PHP 5.3 (PCRE 8.32 2012) or PHP 5.6 (PCRE 8.34 2013)
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
14.07.2014 sjo Omar De-Giuli Requirement for TheBugGenie3 (Answer was: Use another groupware as TBG is not updated ~1 year and appears to be dead.)

SSH2[Bearbeiten]

  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 Staff Customer Email Motivation (why needed?) Customer Feedback
23.09.2014 jre Vincenzo Nicosia own programming (opening sftp connection to retrieve files twice per day with public key) workaround looks good!

PHP gmp (PHP Extension)[Bearbeiten]

  1. Link: gmp
  2. Decision:
    • Result: not investigated properly
    • By: hja
    • When: 29.10.2014
    • Reason: Already comes with PHP 5.5 & 5.6, search for "GNU GMP support" in phpinfo()
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
28.10.2014 sjo Arthur Oppliger Is required for the installation of the password manager TeamPass

PHP APC (PHP Extension)[Bearbeiten]

  1. Link: APC
  2. Decision:
  3. Workaround: Use php 5.6 who have opcache enabled
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
18.11.2014 sve Adriano Sibilia to activate cache
31.03.2015 jre Frank Kollbrunner to upgrade shopware software will cancel subscription and move to another hoster

PHP Xcache (PHP Extension)[Bearbeiten]

  1. Link: Xcache
  2. Decision:
  3. Workaround: Use php 5.6 who have opcache enabled
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
18.11.2014 sve Adriano Sibilia to activate cache

pdftotext and xpdfrc[Bearbeiten]

  1. Link: provide a link
  2. Decision:
    • Result: No
    • By: HJA
    • When: 21.11.2014
    • Reason: No need to install this package
  3. Workaround: Use Ghostscript
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
11.11.2014 shu Christian Friehs "Index PDF-Files via JiFile" NO, the customer can use Ghostscript instead of these two modules.

id3 (PECL extension)[Bearbeiten]

  1. Link: http://pecl.php.net/package/id3
  2. Decision:
    • Result: NO
    • By: HJA/JRE
    • When: 26.01.2015
    • Reason: Retrieving id3 tags from files stored on the server has a very close relation to music streaming (AGB!). No support from our side to do so.
  3. Workaround: http://getid3.sourceforge.net/
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
26.01.2015 jre Ruedi Kumli Retrieving all tags from mp3 files

Sourceguardian-loader[Bearbeiten]

  1. Link: Offical website of sourceguardian
  2. Decision:
    • Result: No change
    • By: HJA
    • When: 09.04.2015
    • Reason: Existing PHP versions not checked properly
  3. Workaround: Source Guardian is already installed in PHP 5.6
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
09.04.2015 SHU Massimo Della Monica Used for special CMS (XT-CMS) LINK  ?

cURL[Bearbeiten]

  1. Link: http://curl.haxx.se/docs/releases.html]
  2. Decision: Not yet decided
    • Result:
    • By:
    • When:
    • Reason:
  3. Workaround:
  4. Info from sysad: rpm -qR curl-7.16.4-16.6

rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libcrypto.so.0.9.8()(64bit) libcurl.so.4()(64bit) libdl.so.2()(64bit) libidn.so.11()(64bit) libssl.so.0.9.8()(64bit) libz.so.1()(64bit) rpmlib(PayloadIsBzip2) <= 3.0.5-1

Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
26.05.2015 nky stefano.klett@gmail.com Google Analytics Fulfill reporting of Google Analytics

Frameworks[Bearbeiten]

node.js[Bearbeiten]

  1. Link: node.js
  2. Decision:
    • Result: not possible
    • By: jre
    • When: 08.10.2014
    • Reason: needs ssh access to the web account
  3. Workaround: -
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
08.10.2014 jre Angie Garz (EN) Needed for Ghost blogging platform

Phalcon[Bearbeiten]

  1. Link: PHP Framework
  2. Decision:
    • Result: will not be installed
    • By: hja
    • When: 07.10.2014
    • Reason: The efforts to install are far to high for a single client (setup, compilation, etc.). It is of no use for other clients, as it needs an own language
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
01.10.2014 jre Michael Krummenerl Fastest PHP Framework ever with built-in code generator that enables fast webapp creation.

phpMyAdmin[Bearbeiten]

Import charset utf8mb4[Bearbeiten]

  1. Link: mysql: the utf8mb4 upgrade
  2. Decision:
    • Result:
    • By:
    • When:
    • Reason:
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
26.05.2015 jre Urs Albisser to be able to import 4byte utf8 encoded dumps (extended special characters)

Software[Bearbeiten]

MySQL upgrade to higher than 5.5.40[Bearbeiten]

  1. Link: note first listed bug here
  2. Decision: No time to do the update for a single request.
    • Result:
    • By: HJA
    • When:
    • Reason: All the platform should be changed
  3. Workaround: He can disable the MySQL version check
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
04.09.2015 jre Frommenwiler Willi His software dolibarr refuses to upgrade because of 50% data loss in all test cases, see http://www.dolibarr.org/87-news/announces/181-why-dolibarr-3-7-was-not-released-in-january

Original error message is: Die Version Ihres Datenbankmanager ist 5.5.40. Dies ist einen kritischer Bug welcher zu Datenverlust führen kann, wenn Sie die Struktur der Datenbank wie vom Migrationsprozess erforderlich ändern. Aus diesem Grund, ist die Migration nicht erlaubt bevor der Datenbankmanager auf eine später Version aktualisiert wurde (Liste betroffer Versionen 5.5.40 )

MySQL 5.6.x[Bearbeiten]

  1. Link: 5.6 release notes
  2. Decision: Not yet completely decided
    • Result: No (for the moment)
    • By: HJA
    • When: 02.02.2015
    • Reason: We'll not update. We have more important things to care than to update a mysql version (H2 project, Security issue with Libc, ...)
  3. Workaround: Use the actual version.
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
30.01.2015 shu Sven Wedemeyer Latest Magento version needs it requirements
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
27.07.2016 dna Daniel Schneider Several Wordpress Plugins

Pagekit[Bearbeiten]

  1. Link: [2]
  2. Decision:
    • Result: Will not run on our servers
    • By: jre
    • When: 22.10.2014
    • Reason: Pagekit makes use of Symfony Components which is Python based. Additionally the components themselves might not suit our security setup (chrooted invironment would be far better)
  3. Workaround: Use another CMS
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
22.10.2014 sve Pascal Tourneur Pagekit is better than Wordpress and Joomla together!

FFmpeg[Bearbeiten]

  1. Link: FFmpeg
  2. Decision:
    • Result: will not be installed
    • By: twi
    • When: 04.11.14
    • Reason: Use to much Ressources
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
03.11.14 yha Tobias Strub Useful for Customers to convert Videos in the new HTML5 format

Bigbluebutton[Bearbeiten]

  1. Link: Bigbluebutton
  2. Decision:
    • Result: No
    • By: HJA
    • When: 25.11.2014
    • Reason: This software can't be used as a Webpage. It's a huge software with alot of dependencies.
  3. Workaround: The only way to have it is to own a virtual machine or a real machine (as requirements state: "Port 80 is not used by another application")
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
19.11.14 sve Stephan Romer He want to install a on-line learning for share stuffs like documents etc.

Python[Bearbeiten]

  1. Link: Python >= 2.6.6
  2. Decision:
    • Result:
    • By:
    • When:
    • Reason: Client tested in advance and has seen a really outdated version.
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
04.01.2015 jre Andreas Spreiter python based web application

LESS Server-Side Compiling[Bearbeiten]

  1. Link: [3]
  2. Link: [4]
  3. Decision:
    • Result:
    • By:
    • When:
    • Reason:
  4. Workaround:
16.02.16 DNA Customer Email Inovation, Future Customer Feedback
16.02.16 DNA Joel Studer Inovation, Future Yes

Email[Bearbeiten]

DKIM[Bearbeiten]

  1. Link: http://opendkim.org/
  2. Decision:
    • Result:
    • By:
    • When:
    • Reason:
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
08.12.2014 dna Stefan Kohler Why not?

XLIST for IMAP[Bearbeiten]

  1. Link: Outlook 2013+ issue RFC6154
  2. Decision:
    • Result:
    • By:
    • When:
    • Reason:
  3. Workaround:
Request Date Staff Customer Email Motivation (why needed?) Customer Feedback
10.11.2015 sjo sjo, Please inform me due several support requests Outlook 2013 and 2016 can't detect automatically the correct folder for sent, drafts etc. A manual option to assign the right folder was cancelled. -

How it works[Bearbeiten]

A new request[Bearbeiten]

You have an incoming request that needs to be judged, copy both parts of the template source. Fill in the headline(s) and the link in the first part of the template. If the scope (i.e. "PHP") is already listet, skip it. Then fill a table row with date, reason and contact address of the client.

Now inform the one that should decide about this entry.

First decision[Bearbeiten]

The decision taker will fill in the decision part of the entry and inform you that it's done.

Workaround[Bearbeiten]

Find a workaround if possible and not given yet by the decision taker and leave it there.

Client information[Bearbeiten]

Time to tell the client what the decision is and why it was taken like this. If you get feedback, add it to the table row of your client.

It is asked again[Bearbeiten]

(So it must have been denied or postponed until now.)

Add an additional line to the table like before with your clients reasons to have it. Inform your client about what was decided in the past. And note his feedback as soon as it arrives.

Escalate it again[Bearbeiten]

You may escalate the request again, if you feel that:

  • your new 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 or postponing are not valid anymore

Entry Template[Bearbeiten]

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

{| class="wikitable"
|-
! Request Date
! Staff
! 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=443“