Hi Ben!

I've sent two versions so far and I'm going to send the final version just now.

As for the checklists: hmm... Which steps do you have in mind?  The trick is
that the is little to repeat once the Git checkout has been set up.
Pjotr has a checklist however, let me know what you think:

From https://gitlab.com/pjotrp/guix-notes/blob/master/HACKING.org:

--8<---------------cut here---------------start------------->8---
Workflow for packaging

The general workflow for adding and maintaining packages is a bit
  complex. Everything goes via de guix-dev mailing list and includes a
  review process which can be discouraging and is more geared towards
  reviewers than towards newbies. This should not discourage you because
  GNU Guix is great. Note that the reviewers do this work voluntarily
  and most ‘rules’ have been agreed by the community. In the end your
  labours will get rewarded. So, how to start?

 1 - Work on a recent git checkout of guix
 2 - Use ‘guix import’ if you can (e.g. for python and R modules)
 3 - Build the package yourself
 4 - If tests are there, make sure they pass
 5 - Test your work with ‘guix lint’
 6 - Create a patch as described above
 7 - Send it to debbugs as described above
 8 - Submit one patch at a time and submit the next one when it goes in
 9 - Be patient, review can take a while - monitor debbugs
--8<---------------cut here---------------end--------------->8---

I'm not sure those are exactly steps, while some items actually belong the
manual's check list "(guix) Submitting Patches".

Opinions?

-- 
Pierre Neidhardt
https://ambrevar.xyz/