I find it annoying when a #FOSS repo mentions that it's a #fork of another project, but doesn't actually say what it itself is/does...
I shouldn't have to go to the original repo in order to find out what a fork does.
Also, forks should really mention why they exist. E.g. why should I use this fork over the original?
BWPanda /
npub1d0…xwnjl
2024-02-26 22:11:20
Author Public Key
npub1d0fajf0juv6pnttjx8dys2tktjzmyc7ysjk0gcva3dsh56lvvm3q6xwnjlSeen on
wss://relay.nostr.bandPublished at
2024-02-26 22:11:20Event JSON
{
"id": "0e7cbce8855a67af4935ff2d88d3c72bd8cda37afc33939a8ca765dc496e295d",
"pubkey": "6bd3d925f2e33419ad7231da4829765c85b263c484acf4619d8b617a6bec66e2",
"created_at": 1708985480,
"kind": 1,
"tags": [
[
"t",
"foss"
],
[
"t",
"fork"
],
[
"proxy",
"https://fosstodon.org/users/BWPanda/statuses/112000072472323806",
"activitypub"
]
],
"content": "I find it annoying when a #FOSS repo mentions that it's a #fork of another project, but doesn't actually say what it itself is/does...\n\nI shouldn't have to go to the original repo in order to find out what a fork does.\n\nAlso, forks should really mention why they exist. E.g. why should I use this fork over the original?",
"sig": "c638f8ca770f046f4aae3e2a90e4ce853888e765e24c20528b685ca6510c8ecb272883d31268c6c69aa9b74e82561c07011ccb704f7b74a8e7ac7ecb4eb9947f"
}