Granting 3rd-party developer access

While a customer has an active Junari support contract, it is Junari's responsibility to keep their system up and running and error-free.

For this reason, we have to be careful not to allow code changes by 3rd parties to affect the stability of our customer's systems

Process for allowing 3rd party access to Junari Customer's code

Junari can provide individual, authorised external developers with direct, read-only access to our customer's GitHub repositories.
GitHub charge us a fee for doing this because they are private repositories, so we will add a £10 extra fee per month per external developer to your monthly support invoices to cover this.

We will also provide (with our customer's permission) a backup of the Test or Live Odoo database, so the 3rd party developer can set up their own copy of the system set up for developing with.

Process for accepting changes made by 3rd-party developers

The level of access mentioned above allows external developers to develop their changes on their own copy of the system, and then submit those changes back to us via a pull request (PR) to the staging branch.

When creating a pull request, the developer should provide:

• A summary of the purpose of the change, any reference numbers for tasks where applicable, and information on how to test it.

• Any necessary notes on applying the update (if any changes are needed besides updating the Odoo module(s) in the normal way)

Junari will then review the PR, and either feed back to the developer with any issues, or "merge" it (accept the changes into our codebase).

Once Junari has approved the changes, we will deploy them to the customer's Test system, for the customer to test and approve.

Once the customer is happy with the changes, Junari will deploy them to the customer's Live system.

Summary of the process:

1. External Developer creates a Pull Request into the staging branch of our codebase

2. Junari reviews the request, and either accepts it, or feeds back any required changes to the external developer

3. Junari merges the PR into our codebase and deploys it to the customer's test system

4. The customer tests and approves the change on their test system

5. Junari deploys the change to the customer's live system

Obviously the above actions require time from Junari. The time to review and deploy a PR obviously depends on the complexity of the change and whether any issues were encountered, etc.

For this reason, customers will need to purchase a Success Pack (pre-paid hours) to cover this time. Further information on our success packs can be found here: https://junari.com/pricing/

Access to Hosting (Junari or Odoo.sh hosting)

Junari is not able to provide direct, unmonitored access to our customer's hosting as this is too much of a risk to our ability to guarantee system uptime and correct functioning. If information or changes are needed in the hosting environment then Junari will do these using information provided by the external developer.

Summary of Fees

We charge £10 per month per external developer, to cover our GitHub user fees and admin relating to these

A customer is required to purchase a Success Pack to cover Junari's time reviewing and deploying the changes

Further conditions

Obviously if data or system issues occur as a result of changes made by 3rd party developers, Junari cannot be held responsible for fixing these as part of our support agreement, and we will need to charge separately for investigating and fixing these issues. We'll provide estimates and advanced notification if this is the case.

Keywords

third-party, third party, 3rd party developer, external developer, external access to customer code, DoDs, developers on demand