Hi Samuel,
> I believe the manpage update should be made in form of a PR on the
> project's github page, and because it's not practical to wait for another
> release, we can patch the new manpage with quilt until we get a new release.
I agree. Let's patch the manpage in our Debian release and submit the diff
to the upstream.
Concerning signed releases, opening an issue on GitHub will be enough. This
document[0] explains very well how to proceed to create signed releases, so
it may be interesting to mention it.
> I would be glad to have someone more experienced co-maintaining the
> package, you're more than welcome.
>
> I'm already a member of the team and have my ssh keys ready, i will create
> the package's repository and then we can work there, please feel free to
> contact me.
>
> From what i see, we have to update the manpage and then we're ready to
> release, we also have to ask for signed releases but this is a non-block
> issue.
Nice ! Well, drop me an e-mail when you're done with the repository and
I'll do a last review before building & uploading the package.
Cheers,
Hugo
[0] https://wiki.debian.org/Creating%20signed%20GitHub%20releases
--
Hugo Lefeuvre (hle) | www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
Attachment:
signature.asc
Description: PGP signature