TYPO3 ELTS Terms and Conditions

1 Scope

This document describes the deliverables for an extended support agreement for TYPO3 CMS 6.2.

It defines the terms of service for extended support in order to provide customers with more time to plan or fulfill a migration to TYPO3 CMS 7.6 or TYPO3 CMS 8.

The initial timeframe is planned to extend the support for an additional 2 years, ending respectively on March, 31st 2018 and March, 31st 2019. The extended support might be extended beyond that point, although this is neither planned nor wanted at this point.

1.1 Customer commitment

  • The customer gains read-access to a private repository that can be accessed either via a Web Interface using Username and Password or via command line by providing a public SSH key.
  • The customer commits to using the provided source code only within the limits of the package subscribed to.
  • The customer commits to not disclosing and/or exploiting issues known by having access to the private repository.

Violating these rules will end the agreement.

1.2 Support Team commitment

  • The team commits to supply fixes as outlined below a.s.a.p.
  • The team commits to informing all subscribers a.s.a.p. via email to allow proper planning of rollouts
  • The team commits to using the generated funds for supporting TYPO3 6.2 and excess funds for further TYPO3 CMS development

1.3 Security Patches

Security issues that have been reported or fixed in the currently maintained TYPO3 CMS versions (7.6 and 8) will be backported towards TYPO3 CMS 4.5 and made available in the private repository.
See Notification for more detail.

This service is included in the agreement.

1.4 Browser Compatibility

Each major release of the following browsers will be tested against the latest TYPO3 version using a mixture of automated tests and manual tests:

  • Microsoft Internet Explorer 9+
  • Mozilla Firefox 34+
  • Google Chrome 41+ incl. Google for Businesses
  • Apple Safari 5+ (Mac Only)
  • Opera 11+

The team ensures these browsers are supported by the Backend of TYPO3 CMS 6.2.

This service is included in the agreement.

1.5 3rd Party extension support

Priority support for 3rd party code can be requested by a customer and the workload will be estimated by the team.

All subscribers to the agreement will be informed about the expected workload and the problem with the 3rd party extension. This way the investment can be split up for customers interested in fixing the issue.

All customers sponsoring the fix will get access to a separate private repository hosting the respective 3d party extension.

A list of all adopted 3rd party extensions will be available to all customers. If a customer requests access to a repository he/she did not have access to earlier, the cost will be split up and refunded to the other customers accordingly.

This refund can be acquired by one of the following ways:

  • Refund to bank account by end of the agreement (respectively March 31st, 2018 or March, 31st 2019).
  • Refund can be used in case another sponsoring is requested. Same rules as above apply.
  • Refund can be used to sponsor the development of TYPO3 CMS 8+

This service is not included in the support plan.

2 Notification

All customers and/or their respective TYPO3 agencies will be notified on the following occasions:

  • A security incident has been reported or was found.
    This report may contain a timeframe for resolving the problem.
  • A security incident has been fixed and a new packaged release is available.
  • Browser incompatibilities have been fixed and a new packaged release is available.
  • The team has received a 3rd party sponsor request and informs all customers about a sponsoring opportunity.
  • The team has changed parts of its infrastructure and customers need to be informed.
  • The agreement timeframe has run out / will run out soon (respectively March 31st, 2018 or March, 31st 2019).

3 Maintenance Scripts

Under certain conditions it is necessary to apply changes to settings within TYPO3 CMS in order to fix a security issue.

The team will provide automated updating and migration scripts where possible or meaningful together with solid instructions what needs to be changed and why.

Feedback