Pay For Features

[tsiedsma]

I'm considering the switch to Blesta from WHMCS but am curious if the certain features that I may want coded can be purchased instead of submitting as a feature request, waiting for community feedback and the scheduled for a future release.

 

I have not made a list by any means but there are a few things that I would need in place before I could consider the switch. Simple example would be the ability to choose a server location when placing an order.  This is something I was able to code into WHMCS using their hooks system and changing the server group based on the selection of a Server Location configurable option for the hosting plan.

 

It works great for me and since I have servers in Europe and the US, my customers need to be able to choose where to have their hosting provisioned.

 

So, is it even an option to pay for custom dev work without having to hire a 3rd party or do it myself?

[Michael]

I know you can donate towards a feature, and also the devs also take on custom work for customers. Also there's a few guys here who are good at coding modules for Blesta I think would love to work with you. Good luck.

[Paul]

We are available for sponsored and custom development, email sales and we can discuss. If it's an extension it's a lot easier than a change to a core feature. For sponsored development, we only implement changes that we want to add to the product but can't do yet due to heavy demand of other features. For everything else it's custom development where we would make the change or build the feature just for you, and not include it in a future release.

[Ken]

We are available for sponsored and custom development, email sales and we can discuss. If it's an extension it's a lot easier than a change to a core feature. For sponsored development, we only implement changes that we want to add to the product but can't do yet due to heavy demand of other features. For everything else it's custom development where we would make the change or build the feature just for you, and not include it in a future release.

 

How can you do custom development in core without maintaining it on every release?  That sounds hectic.

[Paul]

How can you do custom development in core without maintaining it on every release?  That sounds hectic.

 

We don't recommend it, and will not maintain it.. but if someone really needs something, it's an option. An option we are likely to decline, but we've done it before in a couple cases. We recommend sticking to extensions because it doesn't eliminate an upgrade path.

[tsiedsma]

Do you have a roadmap of features scheduled for next and future releases?

Also, do you have more detailed developer docs regarding provisioning module development?  I was looking at the docs as well as the included logicboxes module, I want to extend the functionality of the logic boxes module to included hosting and vps provisioning.  I had written one for WHMCS, so i just need to port it over.

[Michael]

Do you have a roadmap of features scheduled for next and future releases?

Also, do you have more detailed developer docs regarding provisioning module development?  I was looking at the docs as well as the included logicboxes module, I want to extend the functionality of the logic boxes module to included hosting and vps provisioning.  I had written one for WHMCS, so i just need to port it over.

 

Not sure if your talking about these mate:

 

http://source-docs.blesta.com/class-Oath.html

 

http://source-docs.blesta.com/package-blesta.app.html

[tsiedsma]

I was referring to this:

http://docs.blesta.com/display/dev/Modules

 

And 

http://docs.blesta.com/display/user/Logicboxes

[Paul]

The documentation is coming together, albeit a little slower than we would like. All of the modules are open, and serve as excellent examples. If you take one apart, it should start to make pretty good sense. If you have any questions, we're available.

[tsiedsma]

What about my other question?

 

"Do you have a roadmap of features scheduled for next and future releases?"

[Paul]

What about my other question?

 

"Do you have a roadmap of features scheduled for next and future releases?"

 

We have a roadmap but it's not public. We're working towards making our project management public, but we have to work out some permissions issues with items that we don't necessarily want to be public before we can do that. Step 1: Upgrade the system is complete.