## ***Role Nº 1***

**Main Objective**: Serve the current validator set on daily operations;

**Main tasks**:

1. Handle help requests from the validator set regarding their daily technical operations. This includes handle help requests made in the Validators Discord channels;

2. Give technical support for new validators;

3. Maintain, improve and create new technical documentation related to Validators Operations;

## ***Role Nº 2***

**Main objective**: Ensure both Juno environments (Test and Production) liveness and ensure a minimum coordination between the various players operating on those environments;

**Main tasks**:

1. Coordination of upgrades on Test and Production environment;

2. Ensure enough VP is available and ready to go on upgrades;

3. Coordinate with SDK developers and provide all the necessary information and guidance to the validator set, in order to ensure a successful and quick upgrade; (bridge between SDK developers and Validator set)

4. Handle help support requests from the validator set on both environments;

5. Define check lists and action plans for each new upgrade in coordination with the various stakeholders;

7. Ensure that all Applications and Middleware software owners, that interact with Juno Network, or are directly deployed on Juno VM, have the necessary information regarding upgrades, giving them sufficient time to make the necessary adjustments (infra or code) that may be required, due to the upgrade (breaking changes);

## ***Role Nº 3***
**Main objective:** App owners, developers and “builders” support

**Main tasks:**

1. Handle app owners, developers and “bulders” help requests, namely ensuring questions, doubts and help requests on developers Discord channels are handled or routed to the appropriate responsible;

2. Collect App owners, developers and “builders” feedback on the current set of tools available in the development Juno landscape;

3. Collect App owners, developers and “builders” requests on SDK new functionality, namely modules or features available in the broader SDK ecosystem that would be possible to integrate into Juno, if decided;

4. Provide technical guidance (or route it to an appropriate source of information) to new projects that want to deploy on Juno, or use Juno infrastructure for their activity.

5. Handle the feedback received from the Development Department Form, which is openly available to the wide Juno community, and incorporate it into the existing feedback collection system. If the feedback requires action, route it to the appropriate person for resolution.

6. Maintain, improve and create new technical documentation whenever necessary on Cosmwasm related developers’ activity.

## ***Role Nº 4***

**Main objective:** Relayers activity support

**Main tasks:**

1. Keep a close monitoring of the IBC channels activity, ensuring they work correctly to all supported connections;

2. Handle technical help requests from the relayers operators;

3. In case of technical problems, ensure the people responsible for handling users requests (comms department) have updated information, so they can inform users when such problems exist;

4. Handle technical support and guidance for new operators, new channels or completely new connections;

5. Maintain, improve and create new technical documentation whenever necessary on relayers operations activity.

6. Identify new possible connections and keep departments updated so they can evaluate potential connections that might need incentivization, in case they define it as priority for Juno interests;

## ***Compensation & Potential Candidates***

Most of these roles can potentially be filled by our Validator and Apps community.

Selection Process:

**Alternative 1** - A scoped RFP for each role, targeting specifically these two communities and closed to everyone else.
**Alternative 2** - A general RFP for each role, open to the wider market.
**Alternative 3** - Direct collaboration with the 1337 society.
**Alternative 4** - A hybrid solution that incorporates all three previous alternatives, defining the method per role.

## ***Next steps (until 12-03-2024 meeting)***
1. Share the proposed roles with the broader community;
2. Gather feedback and incorporate it;
3. Collect historical data (such as the number of help requests from developers and validators, number of test net upgrades, etc.) to help establish the baseline for SLA between the parties;
4. Make a decision on the selection process and create a working group with the Operations department to operationalize the selection process;