Thanks, Jim. I think we all have clients like that. In that case, I would generally prefer they use Event Espresso to run their events and be successful at their mission, than not use Event Espresso.

However, I think Event Espresso has the potential to help them be more successful so they can afford you and a support license.

Thanks, Jim. I think we all have clients like that. In that case, I would generally prefer they use Event Espresso to run their events and be successful at their mission, than not use Event Espresso.

However, I think Event Espresso has the potential to help them be more successful so they can afford you and a support license.

To date, I have not installed any plugins from GitHub manually. If I was to do so, I would discuss this with the client first, and suggest that they pay for the license if they are thrilled with the software.

If the software is made free/open source on GitHub, and the client cannot afford it, I would keep it updated as long as the software remained free, and the client keeps me contracted to maintain/update their site.

More background, so you understand where I am coming from. At the moment, I have one client (I am not a big company), and they are behind in payments. In good faith, I keep their site updated and spam-free, to keep the server safe, and their users happy. Since they aren’t paying their support fees for my services, I suspect that suggesting an investment in a license would fall on deaf ears (or an empty budget). Since they are a church, I am giving them a lot of grace on this.

I hope this helps explain my situation, which I suspect is different from most potential Event Espresso clients.

To date, I have not installed any plugins from GitHub manually. If I was to do so, I would discuss this with the client first, and suggest that they pay for the license if they are thrilled with the software.

If the software is made free/open source on GitHub, and the client cannot afford it, I would keep it updated as long as the software remained free, and the client keeps me contracted to maintain/update their site.

More background, so you understand where I am coming from. At the moment, I have one client (I am not a big company), and they are behind in payments. In good faith, I keep their site updated and spam-free, to keep the server safe, and their users happy. Since they aren’t paying their support fees for my services, I suspect that suggesting an investment in a license would fall on deaf ears (or an empty budget). Since they are a church, I am giving them a lot of grace on this.

I hope this helps explain my situation, which I suspect is different from most potential Event Espresso clients.

I understand.

We’d prefer people to buy a support license knowing its what they want. That they want access to our support staff, and access to one-click updates, etc. But some people will just take the files and be done, never worry about updates, etc.

Let me ask this then. As the developer for clients, how many times do you have to update a plugin manually (after getting the files from GitHub) before you recommend to a client that they buy a license so the client can get one-click updates?