rucio/documentation

Developer Guidelines for Reviews, Testing Requirements

Open

#538 opened on Apr 3, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (67 forks)auto 404
developerhelp wanted

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

Review the discussion from the Rucio 37 retrospective - https://indico.cern.ch/event/1530158/

Contributor guidelines must be clarified/emphasized, Testing requirements for reviews needs to be decided and written.

cc: @bari12 @rdimaio

Contributor guide

Research direction
Review the retrospective meeting notes and existing contribution guidelines. Draft a proposal for clarified testing requirements and review guidelines.
Tech stack
None
Domain
documentationdeveloper experience
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitMarkdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65