Hi, thanks for the very swift and verbose response. :) I figured previously that it probably wouldn't be included in groff upstream at the time of this writing, but if there is a possibly of inclusion I am more than delighted to hand over copyright to maintainers (Which I believe is the FSF). I would also be okay with it being GPL or any license that would be best. Sometimes I like zlib in addition to the GPL, so it really depends on strategy as outlined by the FSF licensing recommendations.
I wanted to make a package for the intention behind screenwriting. For a script to make a movie or TV show episode for instance. It be a bit tricky to pull off things like page or scene locking, but I do believe that it can be done with a bit of creativity. Already mom exists (So there is a chance this could be included as well) for writing novels and mm/ms could be done for novels as well. But outside of fountain markdown and a LaTeX class I cannot really right off the top of my head think of anything screenwriting specific. What muddled it a bit for me was that I was going to peek into mm and ms to see how it ticks, using the macro code in similar way to how it works, and that's what got me wondering about the GPL licensing. Should I decide to complete a macro package for inclusion (Which I don't want to count my chickens before they hatch), how should I prepare? Well comment on everything in the macro package and maybe on the side make some documentation? Not really sure. I hope this message formats properly because my reply to all button quoted your message, I had to remove it because email provided thought I was trying to or intending to put an attachment.
