botbuilder-community-js
botbuilder-community-js copied to clipboard
BotBuilderCommunity
tyntec WhatsApp adapter
Hello, we have created a tyntec WhatsApp adapter. It does basically the same as Twilio WhatsApp adapter but uses tyntec API instead of Twilio.
I've published it as a standalone package botbuilder-adapter-tyntec-whatsapp so that our customers can use it immediately but we would be very happy if it could be added to this community repo. If it happens, I would deprecate the standalone package.
I did not find any contributors guidelines so I tried to do my best to make it as similar as possible to the Twilio adapter.
Thanks for your contribution, @yet-another-radek! I will try to have a look in the coming week. As you noticed, the CI/CD is a bit broken here, so I will have a look at that as well.
@jamesemann / @szul / @stephanbisser, is any of you still involved with this repo and/or interested to see if we can get it a bit more up to date and with Composer support perhaps. It seems that most interest if going to C#, so I am not sure if there is any interest in JS community contributions. :-)
@iMicknl I am no longer involved. Supporting this repo ought to be a part of a full time job, IMO, and I can’t work my own full time job and then spend my spare time on Microsoft projects.
@iMicknl I am no longer involved. Supporting this repo ought to be a part of a full time job, IMO, and I can’t work my own full time job and then spend my spare time on Microsoft projects.
Fully understandable and thanks again for your awesome work on this project. 💗
I've just pushed a couple of features that we have recently released in the downstream project. @iMicknl, would you have time to continue with the review?
I've just pushed a couple of features that we have recently released in the downstream project. @iMicknl, would you have time to continue with the review?
@radekholy24 sorry for the late reply. I am still a bit in doubt about what should happen with this repository. It seems that there is no one taking ownership of this community repository anymore, and I won't have the time to bring everything up to current standards.
Perhaps you would be better off for now by just having your adapter in your own repository. What would be your reason to have the adapter in this repository?
The reason is mainly the better discoverability of the adapter. And to provide an alternative to the Twilio Adapter. Also, we hoped for help with the maintenance of the adapter.