ImranR98/apps.obtainium.imranr.dev

Proposal: Add a POLICY document for file structure and version conventions

Open

#1,568 opened on Jul 30, 2026

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)Astro (156 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (549 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I propose that we add a POLICY document to structure how files should look and standardize conventions for version numbers.

Example Proposal: Standardize Unofficial Version Numbers

Some apps use unofficial version numbers when stable release formats cannot be applied. For example, the Nightly releases of RetroArch currently use a plain date format (YYYY-MM-DD) because the official version number cannot be added to them (e.g, 1.22.2):

The versionExtractionRegEx\":\"\\\\d{4}-\\\\d{2}-\\\\d{2}\" in these configuration files handles this format:

Proposed Rule

Unofficial version numbers should be enclosed in square brackets. Under this policy, plain dates like YYYY-MM-DD would be formatted as [YYYY-MM-DD] (e.g., for RetroArch Nightly builds).

Contributor guide

Research direction
Inspect the repository structure and JSON configuration files, particularly the RetroArch examples. Understand the current version extraction regex and how unofficial version numbers are handled. Plan a POLICY document that defines the new bracket convention and identify all files that would need to be updated.
Tech stack
astro
Domain
datadocumentation
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.
1-3 hours
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.
Clear
Prerequisites
GitJSON
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80