mitchellh

vouch

A community trust management system based on explicit vouches to participate.

by mitchellh

Nushell

Nushell98.5%
Nix0.8%
Shell0.7%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

3 of 6 standards met

Community profile →
57
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Active · 3 in progress · Last activity 1mo ago
See all on GitHub →
binyamin

The term "vouch" sounds very vague to me. When I vouch for an individual or profile, what exactly am I saying? Am I saying: they are in fact who they say they are? they are human and not a bot? they're a good programmer? they contribute to open-source in "good faith"? I enjoy interacting with them online? The readme seems to mention vouching in reference to code contributions. But it's not clear to me _when_ to vouch for someone and _why_.

binyamin · 1w ago
pavelzw

closes #103 this moves the link to the originating comment into the vouch CLI instead of the action. it also fixes the link for github discussions, see https://github.com/mitchellh/vouch/issues/103#issuecomment-6559677048

pavelzw · 2w ago
pavelzw

We are now using vouch in https://github.com/prefix-dev/pixi and let people create "Vouch Requests" through GitHub discussions (see here). I noticed, though, that doesn't add a GitHub discussion link back. https://github.com/prefix-dev/vouched/commit/2d75a03bda4f6d1ecf04749183e598378f80b67d was created through a GitHub discussion (https://github.com/prefix-dev/pixi/discussions/7418#discussioncomment-19333562) while https://github.com/prefix-dev/vouched/commit/7649369e10c67d2599cda07fae1a4265f318f868 was created through a GitHub PR / issue comment (https://github.com/conda/rattler/pull/2959#issuecomment-6292506495). I think adding the discussion link like in the PR / issue comment would make sense as well.

pavelzw · 2w ago
evrardjp

Related: https://github.com/mitchellh/vouch/issues/21 Disclaimer: Maybe I am using vouch incorrectly. You tell me. What I want to do: I want to track people who did not follow the rules of a project and prevent them to contribute in some kind of ladder: "First warning" -> "Temporary ban" -> "Permanent ban". For that, I intended to use vouch, and use the denounce feature: "First warning" gets a commented out line "Temporary ban" gets the actual line "Permanent ban" is In my example, would at least look like a link pointing to the violation warning; would at least look like two links, would at least look like 3 links. I would like to track dates of those events uncorrelated from the git commits who introduced the ban. In other words, regardless whether: I am busy and forgot to put the temp ban in my vouch file I got a policy in place but did not use vouch yet .. I would like to start to use vouch and reference to past or future dates. I know it is possible to see (with ) when the temporary ban was issued. Technically, it would be possible to automate when to unban from the git blame (by periodically checking the line and appending ). And I know I could create n commits (one for each event) and manipulate their date, but it seems convoluted. However, decorrelating from git makes practical sense to me. I know it's also possible to use the comment field (as it is free text) for storing that date. However, if we are to introduce the feature of _adding a date_ as top level citizen, it would become a standard (before or after the comment?), so multiple projects behave it the same way, and project don't have to remember the syntax to use for their comments ("was it date before link or the other way around? Oh damn I have to check first" syndrome). This date could be present on all command calls by default for example. This still gives the freedom to the projects to see how they will use the date. In my case, it would be the declared date, but it could as well mean an expiry date. Happy to pick your brain on the global relevance of introducing dates as first level citizen.

evrardjp · 2mo ago
Structured data for AI agents

Repository: mitchellh/vouch. Description: A community trust management system based on explicit vouches to participate. Stars: 5180, Forks: 91. Primary language: Nushell. Languages: Nushell (98.5%), Nix (0.8%), Shell (0.7%). License: MIT. Latest release: v1.5.0 (4mo ago). Open PRs: 3, open issues: 16. Last activity: 1mo ago. Community health: 57%. Top contributors: mitchellh, github-actions[bot], alexhraber, dependabot[bot], faukah, trag1c, pavelzw, vancluever, freepicheep, doprz and others.