+Jelmer, who is the maintainer of the metadata specification > https://wiki.debian.org/UpstreamMetadata > > That's pretty much where we are now. This was done in the pre-Salsa time, and > if people get excited about the concept, I guess that Salsa offers new > opportunities to play with the concept!
This wiki page is partially outdated. I'd recommend reading https://dep-team.pages.debian.net/deps/dep12/ instead. However it is also pending to be polished and finalized by via https://salsa.debian.org/dep-team/deps/-/merge_requests/7 The `debian/upstream/metadata` field 'Repository' (e.g. `Repository: https://github.com/eradman/entr.git`) is already used by e.g. `gbp clone --add-upstreamvcs` to add the upstream git remote automatically. The `gbp.conf` field `upstream-vcs-tag` (e.g. `upstream-vcs-tag = v%(version%~%-)s`) could probably be added as a new upstream metadata field if Jelmer and Guido agree on what to call it and how to roll it out in a backwards compatible way. This is probably what you were referring to as in previous emails some people mentioned that they don't want this "generic upstream" information to be defined in a file that has the filename of a specific tool. The only other field that might be generic is `upstream-signatures` for telling if upstream tarballs are expected to have signatures or not. No other only field in `gbp.conf` that comes to my mind that could be generic. The rest of the `gbp.conf` configs seem very git-buildpackage-specific.
