I did a very early initial release of #partisipate, the #Qt softphone client for a #Coventry/Apollo/Bordeaux phone system. This only does registration, that's it, and was done mostly just to setup packaging processing. Much that will come into partisipate will eventually come from the older #SipWitchQt client.

I think I need to introduce a #coventry specific collaborative #voip client, and if so, it would borrow a lot from the #sipwitchqt front end.

I did manage to get #sipwitchqt to be buildable and testable again last week on #codeberg. But I am not up to doing releases or other updates yet.

I am considering bringing #SipWitchQt back as an active project. This was a complete client and stand-alone server with integrated administration that was designed from the ground up to unify telephony and internet messaging for the end user, and do so over sip.

One of the interesting consequences from #SipWitchQt is the idea that all administrative functions locally can be performed in a sip protocol attached application or user agent rather than a huge intermediary stack of web servers, javascript front ends, browsers, and other crap, and this may well be the correct answer for #Coventry.

This was back when I was experimenting with #SipWitchQt. Yes, it had a very clean and simple look. It also was done purely with #Qt widgets.