repo metadata

Open
#77 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
infrastructure

Research direction

Start by reviewing the repository's existing infrastructure configuration and determine which proposed metadata fields are in scope. Agree on the format and required fields before implementing anything; done means the chosen repository metadata is documented in separate files and covers the agreed information.

Written by the indexing model from the issue text.

Description

hi there! :)

i think it could be nice to add some meta to the repositories, like last sync, location, owner, contact, custom packages, missing packages, supported architectures, clibs, and what not.. :D (plz ignore if i just said anything redundant)

in case of interest, i think single files for each would be the most universal format

(nothing urgent or anything, just some braindump before i forget to come up with the idea :D )

Dominant language
HCL
Stars
79
Forks
31
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from void-linux/void-infrastructure

All issues in void-linux/void-infrastructure

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.