@fungus: reading the project page link in your signature, it looks like vuu-do comes with PM, so mayhaps I'll look into that as well.  I did notice that the devs are cool with redistribution so long as the binary in the public OS is unaltered: doesn't include 3rd-party addons, custom settings, etc.

If you just pass on the opportunity to your natural product with your name on it, you would be thankful, I think!  I think vuu-do came with palemoon, I don't know if it still does.  I use it everyday.

You should be more concerned about Palemoon's licensing than Devuan's.  Though MX may have taken care of that for you.

Now see...when I look at stuff like this, I want to have a nervous jerkdown.  

http://www.palemoon.org/redist.shtml

This was my original thought.  However, I've observed that several other distros use, for instance, the analogous debian repositories in sources.list.d, so their public releases aren't completely debian-independent.  In addition, I also observed other distros that seem to "clone" the bulk of debian packages, making small (if any) changes to the version.  Those distros' repos seemed, essentially, to be debian ones.
This led me to speculate on how far a project can stray from its mothership (in my case, devuan) without aggravating any labeling, branding, or licensing issue.
All of that actually leads into my answer to your next question.

Thank you for asking this.  My idea was to utilize devuan as the main repository, and any of my modifications in a separate one.  If this were legal, it would seem to me the easiest way to maintain a small, one-man-army derivative, since I'm not flying by RHEL's ambitions.

Are you making a mirror repository of your own?  If no, and you are using devuan then it is devuan.  If whoever installs your system wants an update of your own scripts and modifications, how would they get them?  See miyo-linux discussions and vuu-do here, there is probably many relevant points.

There is also a thread made by the admin of the forum of a list of forks and derivatives based on devuan.

I have a project system that my friends keep encouraging me to release publicly (eg, on a sourceforge link).  I never really thought to release it, but lately the thought has been on my mind.  I'm using 99% devuan packages; the only exceptions are palemoon (pulled from MX) and linux-libre kernel. 

My only concern is with licensing or credit/citation of any sorts (not that I wouldn't give devuan credit, but maybe there would be more than just saying, "built on devuan" or something of that ilk).  I've read that, since everything is under an open-source license, it should be free to redistribute.  However, I'm wondering if there's more to the story -- or, more that I need to read.  It would be agonizing to produce a derivative that gets me fined.

I was wondering how much truth is in the claim that a custom-built devuan can experience mostly-trivial modifications and still be branded as a project of its own.  I'm also curious if any user has ever found him/herself in a predicament due to this: what happened, how was it resolved, etc.