This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
developers:bugzilla:sponsored [2013/06/10 20:22] jonyo [Sponsored Features] |
developers:bugzilla:sponsored [2015/10/08 21:08] geojames [Why Sponsored Features Included In Base Code] |
||
---|---|---|---|
Line 5: | Line 5: | ||
When you sponsor a feature, you are paying us to add a new feature to the software that might not have been added otherwise for a much longer time, or perhaps not added at all. Sponsored features get top priority. | When you sponsor a feature, you are paying us to add a new feature to the software that might not have been added otherwise for a much longer time, or perhaps not added at all. Sponsored features get top priority. | ||
- | But note that sponsoring a feature is **not obligatory** for a feature to get added, it is merely an option you have if you wish to take advantage of it to ensure a feature you want gets added right away. See the next section to read about how we decide on what features to add when they are not sponsored. | + | But note that sponsoring a feature is **not obligatory** for a feature to get added, it is merely an option you have if you wish to take advantage of it to ensure a feature you want gets added right away and customized to fit your specific business plan/ |
- | ====== Long-Term | + | ===== Why Sponsored |
+ | |||
+ | Many clients have approached with requests to develop a feature for them but that the client would own or control/ | ||
+ | |||
+ | Such requests require us to keep custom code separate from the base file set we work with. Managing different code bases in an active coding environment is time consuming, not cost efficient and eventually one branch of the code gets abandoned...and the code base abandoned is not the base Geo file set. The custom development work is the code abandoned to fall behind the base software. | ||
+ | |||
+ | Once a piece of code is separate from the base code set it quickly falls behind the base software. | ||
+ | |||
+ | Another reason is that the feature actually gets used. Once a feature is in the code base other clients eyes see it and can use it. We've seen many times where once a feature was released issues in the feature are quickly found and fixed because of other clients poking and testing the sponsored code. The feature gets " | ||
+ | |||
+ | We as a software company must keep our software competitive with other software in the industry. | ||
+ | |||
+ | We do not want to place limits where the software can go in the future and providing " | ||
+ | |||
+ | Please note also that the cost we give for adding a sponsored feature is not the whole cost of that feature. | ||
- | Between accepted sponsored features, and features that we plan to add without sponsorship, | ||
===== How we Add Features ===== | ===== How we Add Features ===== | ||
Line 47: | Line 60: | ||
Also be aware that depending on how complicated the feature is, the more time it would take to add the feature, the more the feature is going to cost. The **more complex** the feature is, the **longer it might take to generate the quote** for that feature. | Also be aware that depending on how complicated the feature is, the more time it would take to add the feature, the more the feature is going to cost. The **more complex** the feature is, the **longer it might take to generate the quote** for that feature. | ||
+ | |||
+ | ===== Long-Term Sponsored Feature Request Queue ===== | ||
+ | |||
+ | Between accepted sponsored features, and features that we plan to add without sponsorship, | ||
+ | |||
===== Development Cost VS. Retail Cost ===== | ===== Development Cost VS. Retail Cost ===== | ||