Rex-Server (Rex-Overlord)

Description

Contributor guide

Tech stack

None

Domain

devopsinfrastructure

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

5

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

over 1 week

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

unclear

Prerequisites

None

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

5

Research direction

The issue is a placeholder for discussing the Rex Server and Agent architecture, but the actual content was moved to the wiki (https://github.com/RexOps/Rex/wiki/Rex Server & Agent (Overlord & Drone)). First time contributors should read the wiki to understand the proposed design and then review the existing comments to identify any concrete tasks or unresolved questions. Since the issue has been stale since 2015, contributing would require re initiating the discussion with maintainers to clarify current priorities.