Conversation
|
This is a very convenient feature. |
@SiriusXT , yup, we got an open-source deal with them to get some premium features. When the key expires we just need to renew it. If you keep a version for more than 3 months without update, I'll need to make it fall back to not using premium features. Not sure why the expiration date is only 3 months but it is what it is. |
|
While I do understand the wish for this feature (I have it myself), is it really in the best interest of the project to build on something that requires the good-will of a company to renew their key and forces continuous updates just not to degrade? Once the flood door is broken, it feels more and more functionality might be built on such premium features and suddenly falling back to "just disable it once the license runs out" is not so feasible any more? |
|
@capi , I understand the concern. Although I have my concerns regarding the expiration of the license, we have to understand that those are add-on features.
Indeed, that would be problematic if some core features were part of this premium scheme. In our case, it's only a few (we didn't get full premium but only a subset of them known as the productivity pack) and it's not going to increase. Regardless, we would be doing continuous updates for dependencies, so it's only a slight hiccup in terms of maintenance. Users should also periodically update, regardless of whether they want premium features or not. I'll try to see if the expiration date of these license keys can be extended.
We don't actually build on top of premium features, we just enable them. In our case, it's going to be slash commands and templates/snippets. |
|
@eliandoran Thanks for taking the time to address my feedback. I'm actually looking forward to the feature, so fingers crossed everything works out in the long-term :-) |
No description provided.