Open KyrneDev opened 6 years ago
I've been thinking about this as well. From the get-go we will show a button on the extension page in case the composer.json file has any of the set "support" attributes we will render it. Email and board might make sense for most?
https://getcomposer.org/doc/04-schema.md#support
For the long term I'd like to allow developer teams to add a unique code, eg the one from Freshdesk or Zendesk by which the site will show a support modal. Alternatively we could create a simple chat/issue solution using pusher.
I think a zendesk option would be better than chat, most developers are either 1 person or a few people, and they probably won't be on chat all the time.
If you're up for investigating what support desk solution works for you, I'll see to it to get it in asap ;)
Pricing between these tools vary extremely, especially with multiple agents involved. With your foss packages you might want to check up on some of these parties for open source plans.
I'm liking the look of Ngdesk.com it's free and has just enough features. What do you think?
Just came upon this issue again. Maybe the best course of action would be to just allow developers to add a link to their support, that is added in the 3 dots menu.
Composer also added a new link "chat" in 1.8.0. I'll make sure to add that one too. This would be perfect for discord, when having that next to a forum.
Since extensions are paid they should have first class support. I think there should be an option on the 3 dots menu of a paid extensions that opens a link set in the composer.json (maybe a "support" option under flagrow's subsection)