1. It lacks a manual (I don't believe this is very important butIt looks like `lintian` treats this as a warning. I can write a manual but the `escargs` utility doesn't have any options or environment variables that it reads, so I am not sure if it is worth the effort.still pointed out by lintian).
Maybe not then.
Because your RFS is now a year old: 4. It is a version behind upstreamThe RFS/ITP are only four months old (April 2020) and the latest version I see on upstream is v1.2.2 (https://github.com/alessio/shellescape/releases/tag/v1.2.2). Therehave been some commits since then, but none of them are functional changes (https://github.com/alessio/shellescape/compare/v1.2.2...master).
My mistake, I had a couple of shellescape packages open at the time and might've looked at the wrong one for that.
I do not have permission to write the shellescape repo owned by theNot sure if this matters: 5. Salsa repository isn't part of go-teamgo-team. I have been pushing my code to a personal repo on Salsa(https://salsa.debian.org/bradfordboyle/shellescape). I thought I requested access to the go-team repo through the GitLab CI but is thisnot the preferred way of requesting access?
If they still haven't given you access then its probably worth sending an email on the mailing list, mine got accepted within about 20 minutes of applying.
Thanks for improving this, hopefully it encourages a prospective sponsor :^).
-- Thanks, Jai