For a little bit more context, this is my first time submitting a package upstream. I noticed pekwm was scheduled for autoremoval due to Bug#1135925 -- a build error -- but also actively maintained by its developer, so I packaged the latest version, planning to just send patches to the maintainer, but as I see now that it is orphaned, so I would like to adopt it instead.
I do also have a couple of newbie questions: 1. Since the last release that Debian packaged, the upstream developer has accepted patches from several github users without publicly-known email addresses. Is there a preferred way for the copyright file to acknowledge their contribution? 2. The existing control file references a git repository on salsa.debian.org. Do I need to wait until my account creation there is approved to proceed, or will the sponsor also update salsa? Does it complicate things any that upstream pekwm no longer uses git as they have switched to fossil? 3. The first patch in the quilting series was still applicable in function but needed a near-total rewrite to fit current upstream. Is listing the original patch date and author but also adding to the description and inserting a Last-Update date the correct way to handle this? ---
