So there are two entangled issues here that I would suggest disentangling:
How do you get your changes to mmsd into the upstream mmsd repository on kernel.org? There have been commits to mmsd upstream in 2019. My suggestion would be to CC more folks on your next patch submission, at minimum: the Linux netdev mailing list, the oFono list, everyone in the mmsd AUTHORS file and all the folks who are listed as a committer in any of the mmsd git commits.
How do you get mmsd into Debian? The usual procedure is to upload the package to the mentors site and file a request for sponsor bug report, XCCed to relevant people/lists, which in your case is probably the debian-mobile list, Debian oFono maintainers and any other Debian mobile related addresses (I guess Purism PureOS, Mobian etc). Of course, that doesn't guarantee that a Debian uploader will sponsor the package, but it is a good start.
Do both at the same time, if upstreaming the patches doesn't work out, you can add them to Debian while still figuring out a way to push them upstream.
The debian-on-mobile team is aware of it, but even they have been commenting that getting upstream mmsd will take time. One has suggested to change the bug for a request for sponsor. It sounds like I need to do that.
So the ITP (Intent to Package) and RFS (Request for Sponsor) are two separate things.
The ITP comes before you have started the packaging, it is a notice of intent rather than a request and functions as a way to prevent other folks from spending time on something someone else is spending time on, a place to discuss and document any issues that come up during packaging and a way to advertise the potential new package such that others can get involved and co-maintain the package if they want to. Since you didn't XCC the ITP to debian-devel as is customary (and what reportbug wnpp does), that part of the purpose of ITPs was reduced.
The RFS comes after you consider the packaging complete and ready to be in the Debian archive. It is only for people who aren't yet able to upload themselves. It should be sent once each time you want to upload. It should be directed at debian-mentors (done automatically when using reportbug) and XCCed to the relevant team mailing lists and any other potential sponsors.
and I want to say I did the XCC to the relevant sponsors? I know I included th Debian on Mobile mailing list (they are the ones to suggest how to submit debian packages).
Looks like they did get a copy, but FTR, XCC != CC. XCC is my abbreviation for X-Debbugs-CC, which means that the Debian bug tracker forwards your bug to additional folks. If you use XCC then they get the bug number but if you use CC then they don't, at least for the initial bug submission, obviously for post-submission bug mail you are CCing the bug number.
Gotcha. Unfortunately, I thought I manually added that, but either Evolution didn't understand it or my mailing service didn't like it (which is what I was afraid of and why I CC'ed as well).
How do you get your changes to mmsd into the upstream mmsd repository on kernel.org? There have been commits to mmsd upstream in 2019. My suggestion would be to CC more folks on your next patch submission, at minimum: the Linux netdev mailing list, the oFono list, everyone in the mmsd AUTHORS file and all the folks who are listed as a committer in any of the mmsd git commits.
https://git.kernel.org/pub/scm/network/ofono/mmsd.git
How do you get mmsd into Debian? The usual procedure is to upload the package to the mentors site and file a request for sponsor bug report, XCCed to relevant people/lists, which in your case is probably the debian-mobile list, Debian oFono maintainers and any other Debian mobile related addresses (I guess Purism PureOS, Mobian etc). Of course, that doesn't guarantee that a Debian uploader will sponsor the package, but it is a good start.
https://mentors.debian.net/intro-maintainers https://mentors.debian.net/sponsors/rfs-howto https://www.debian.org/Bugs/Reporting#xcc https://lists.debian.org/debian-mobile/
Do both at the same time, if upstreaming the patches doesn't work out, you can add them to Debian while still figuring out a way to push them upstream.