e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
68 lines
3.3 KiB
ReStructuredText
68 lines
3.3 KiB
ReStructuredText
.. _terms_of_sale:
|
|
|
|
=====================
|
|
General Terms of Sale
|
|
=====================
|
|
|
|
.. note:: Last revision: May 5, 2017.
|
|
|
|
These General Terms of Sale govern the sale of products and services by
|
|
Odoo S.A. and its affiliates (collectively, "Odoo S.A.") to the client.
|
|
Additional terms may apply for services provided by Odoo S.A. (for example, the
|
|
Enterprise Subscription Agreement). If these additional terms are inconsistent
|
|
with the General Terms of Sale, the additional terms will prevail over these
|
|
General Terms of Sale.
|
|
|
|
Please read these terms carefully before placing an order with Odoo S.A. By
|
|
accepting an order with Odoo S.A., the client marks his acceptance with these
|
|
terms.
|
|
|
|
The client explicitly waives its own standard terms and conditions, even if
|
|
these were drawn up after these standard terms and conditions of sale. In
|
|
order to be valid, any derogation must be expressly agreed to in advance in
|
|
writing.
|
|
|
|
Our invoices are payable within 21 working days, unless another payment
|
|
timeframe is indicated on either the invoice or the order. In the event of
|
|
non-payment by the due date, Odoo S.A. reserves the right to request a fixed
|
|
interest payment amounting to 15% of the sum remaining due. Odoo S.A. will be
|
|
authorised to suspend any provision of services without prior warning in the
|
|
event of late payment.
|
|
|
|
If a payment is still outstanding more than sixty (60) days after the due
|
|
payment date, Odoo S.A. reserves the right to call on the services of a debt
|
|
recovery company. All legal expenses will be payable by the client.
|
|
|
|
Certain countries apply withholding at source on the amount of invoices, in
|
|
accordance with their internal legislation. Any withholding at source will be
|
|
paid by the client to the tax authorities. Under no circumstances can Odoo S.A.
|
|
become involved in costs related to a country's legislation. The amount of the
|
|
invoice will therefore be due to Odoo S.A. in its entirety and does not include
|
|
any costs relating to the legislation of the country in which the client is
|
|
located.
|
|
|
|
Odoo S.A. undertakes to do its best to supply services in due time in accordance
|
|
with the agreed timeframes. However, none of its obligations can be considered
|
|
as being an obligation to achieve results. Odoo S.A. cannot, under any
|
|
circumstances, be required by the client to appear as a third party in the
|
|
context of any claim for damages filed against the client by an end consumer.
|
|
|
|
In order for it to be admissible, Odoo S.A. must be notified of any claim by
|
|
means of a letter sent by recorded delivery to its registered office within 8
|
|
days of the delivery of the goods or the provision of the services.
|
|
|
|
To the maximum extent permitted by law, the aggregate liability of each party
|
|
together with its affiliates arising will not exceed 50% of the total amount
|
|
paid by the Customer under these terms during the 12 months immediately
|
|
preceding the date of the event giving rise to such claim. Multiple claims shall
|
|
not enlarge this limitation.
|
|
|
|
Odoo S.A. reserves the right to modify these terms at any time without prior
|
|
notice. The client will be subject to the terms in force at the time of
|
|
acceptation of those terms.
|
|
|
|
All our contractual relations will be governed exclusively by Belgian law.
|
|
Moreover, any dispute that may arise will be subject exclusively to the
|
|
jurisdiction of the courts of the Nivelles arrondissement (Belgium).
|
|
|