Commit Graph

16 Commits

Author SHA1 Message Date
38e27c698c
Precise in README.md alternative method when having contributed to the repository of someone else to prove authenticity of own commits 2023-02-01 17:47:45 +01:00
b6b5454bc6
Add gitlab.com/gitlab-org/omnibus-gitlab 2023-02-01 01:53:48 +01:00
f04e95cfae
Add a description to VERIFIED_ONLY_OWN_COMMITS status flag in README.md template
Note that here I talk about commits and not git state. I don't even know
if talking about global commits diff like a git state diff make sense as
commits happening between the first and last known to date verifier can contain commits from other users.
2023-02-01 01:48:20 +01:00
de77294a7a
Add codeberg.org/Benjamin_Loison/YouTube_captions_search_engine 2023-02-01 01:42:20 +01:00
25780762cf
Add gitlab.com/Benjamin_Loison/password-generator 2023-02-01 01:39:55 +01:00
e6d5cd9523
Add github.com/BenjaminLoison/bitcoin-developer-preview 2023-02-01 01:36:46 +01:00
7d9b6e3924
Add VERIFIED_ONLY_OWN_COMMITS status flag in README.md template 2023-02-01 01:35:41 +01:00
a2bac0f426
Add gitlab.lemnoslife.com/Benjamin_Loison/dofus-retro-server 2023-02-01 01:21:39 +01:00
8f8056ded4
Add default template to README.md introducing status and comment optional fields 2023-02-01 01:20:48 +01:00
a563507bf3
Add github.com/Benjamin-Loison/YouTube-operational-API 2023-02-01 00:54:58 +01:00
f7448055b9
Add gitea.lemnoslife.com/Benjamin_Loison/Gitea_instance.json 2023-02-01 00:51:09 +01:00
cddf020b21
Remove unused comment field of gitea.lemnoslife.com/Benjamin_Loison/LemnosLife_Rust
It's a real debate whether or not to include the field with empty string
to equivalently mean that there isn't any specific comment that the
author wanted to share. To minimize file sizes and improve readability
let's proceed by not specifying default values to fields.
2023-02-01 00:49:01 +01:00
66b7e574fb
Precise the notion of repository state in README.md 2023-02-01 00:44:53 +01:00
753bbb8e3f
Add gitea.lemnoslife.com/Benjamin_Loison/LemnosLife_Rust 2023-02-01 00:42:14 +01:00
32263625f5
Precise the current trust level target in README.md
I thought about adding the following convention:

> Current convention is such that if a folder exists but just contains `.gitkeep`, it means that everything that could fall into this folder and isn't existing is considered as verified.

This would be useful for personal git users, but it's an edge case and
would anyway need to precise an overwhole git user gits hash to confirm
a statement at a given gits state.
So let's keep the same convention for every git.
2023-02-01 00:38:24 +01:00
fd7ad7a93d
Add README.md 2023-01-31 23:43:23 +01:00