You could attempt to by posting to the asterisk-dev mailing list, but the code is not being maintained by Sangoma and does not wish to be maintained by the community and the developer community would like to see it removed.
Well, speaking as a developer, I would not like to see it removed.
You may literally be the only individual interested in it or using it.
I don’t doubt that it’s probably one of the lesser used features, but I’m sure there are at least a few. Probably more people than using AlarmReceiver() at least, I’d bet. There are a lot of people out there using Asterisk who don’t participate in the Asterisk community forums and lists. I’ve been using it for years in the telecom sphere but only recently became more involved with the Asterisk community.
If it were removed, you would need to maintain a patch set to add it back in.
Right - if it was just app_adsiprog being removed and nothing else, it might not be a big deal, but if there are many references in other files, with a changing codebase over time, it seems that this might grow to be more and more complex over time.
I already have a few custom patches that I apply, since I haven’t gotten around to adding options to the application yet (such as ConfBridge), but this is more involved.
I should also add that in a frozen state it’s something we still have to maintain. If further GCC versions find issues with it, we then have to figure out the issue and resolve them. It’s not zero ultimately.
I’m totally fine with Sangoma not maintaining it, I don’t think anyone expects them to, it would just be really nice if it were kept “as is, with no support”, rather than removed. Doesn’t need to be enhanced and maybe bugs can be ignored, but what’s already there is better than nothing. I didn’t know about the Parking and so in the future I’ll see if I can patch that back, at least myself. I just haven’t added parking to my system yet.
I could try to support the module myself, on a best effort basis, at least for myself and anyone else using it if that is helpful.