Source Code Access Agreement

i. in the case of a written notification due to a substantial breach of this agreement and/or other agreement between the parties, unless it is corrected as part of these [O;” or Atomikos Source Code Access Agreeement (“Licence”) regulates access to any Atomikos source code you have received, including (but not limited): you cannot change the source code of Atomikos beyond the rights mentioned above. You cannot create additional copies of Atomikos` source code that go beyond what is allowed above. You must not remove or modify references to intellectual property rights such as copyrights, patents, trademarks or other rights. You cannot distribute or disseminate The source code of Atomikos to other legal parties outside of you. You may not use a code that can be executed directly or indirectly from The Source Code of Atomikos, for purposes other than what is expressly authorized above. You cannot transmit, sell, lend, distribute or transfer an executable code from Atomikos` source code to others. I. “source code” refers to the software code from which the object code is compiled. The source code contains the commented source code and design documentation of the software in question and other related materials in a machine-readable and readable form (e.g.B. including, but not limited to, electronically readable relevant source documentation, design documents, support media, and any reasonably necessary information or program to compile the source code into a fully functional object code. The source code made available by LICENSEE for licensed materials is included in Appendix C of this SCAA.

As a solution to this conflict of interest, the escrow source code ensures that the licensee has access to the source code only if the maintenance of the software cannot be provided otherwise, as defined in the contractual terms. [2] A. The initial term (“start date”) of the agreement begins on the SCAA date and is valid for a period of five (5) years, unless it is terminated earlier due to injury under Section 10B. Regardless of the above, LICENSEE is required to pay the basic annual fee and cancellation fee covered by Schedule A, in addition to the minimum licensing payments under a software license agreement, which may be concluded later or simultaneously between the parties for the remaining term of the agreement, unless the MAI violates license non-application provisions of LICENSEE. After the initial maturity, LICENSEE may automatically extend the term for one consecutive year or for a period of one consecutive year (an extension period), provided that the renewal fee (as defined in Schedule A) continues to have access to the AMI technology, provided that the payment of the LICENCE renewal fee is paid to the MAI no later than the expiry of the previous period. In the event of early termination by LICENSEE [ . . .

The duration of this agreement may be indeterminate, but this agreement may be terminated immediately if the terms of this agreement are not met. In some situations (e.g.B. when it is expensive to purchase and implement licensed software, for which the customer is not simply or quickly replaced or essential to day-to-day activity), a customer may not rely entirely on the software provider to provide the necessary maintenance services. Instead, the customer could request a complementary self-help measure – a right to access and use the source code to manage the licensed software if the provider does not want or is unable to do so – provided by a trust agreement for the source code.

Print Friendly, PDF & Email
Please follow and like us: