This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
developers:bugzilla:sponsored [2012/10/24 17:01] jonyo [Sponsored Feature Quote] |
developers:bugzilla:sponsored [2015/10/08 21:08] (current) geojames [Why Sponsored Features Included In Base Code] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Sponsored Features ====== | ====== Sponsored Features ====== | ||
- | Any client can sponsor a new feature, by paying the " | + | Any client can sponsor a new feature, by paying the " |
- | 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. If we have multiple sponsored features at once, we will work on them in the order that they were paid for. Once the feature is complete, we will make a beta version of the software available to you so that you can start using the new feature right away. You would also have the option of just waiting for the next feature release to come out if you did not want to use a beta version and you didn't need the feature right away. |
+ | |||
+ | 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/ | ||
+ | |||
+ | ===== Why Sponsored Features Included In Base Code ===== | ||
+ | |||
+ | 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. | ||
- | 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. | ||
===== How we Add Features ===== | ===== How we Add Features ===== | ||
Line 23: | Line 40: | ||
The quote process is a multi-step process, below is the general steps a quote request will go through: | The quote process is a multi-step process, below is the general steps a quote request will go through: | ||
- | - First, you send in the request to [email protected] with exactly what you would like to do. < | + | - First, you send in the request to [email protected] with exactly what you would like to do. **Note: |
- Follow-up questions: Sometimes we will need to ask questions about exactly what you need. We want to make sure we understand exactly what you want to have added. | - Follow-up questions: Sometimes we will need to ask questions about exactly what you need. We want to make sure we understand exactly what you want to have added. | ||
- Once we have a clear understanding of what you want to have added, if we already have a quote for that feature or a similar one we'll send the quote directly. | - Once we have a clear understanding of what you want to have added, if we already have a quote for that feature or a similar one we'll send the quote directly. | ||
Line 31: | Line 48: | ||
| Large Project | More than a week | $1,000 and up | | | Large Project | More than a week | $1,000 and up | | ||
**NOTE:** At this stage, the project size is **not guaranteed**, | **NOTE:** At this stage, the project size is **not guaranteed**, | ||
- | - When you verify that you are still interested after we give you the rough project size ballpark, we will create an accurate price quote. | + | - When you verify that you are still interested after we give you the rough project size ballpark, we will create an accurate price quote. |
- To generate the most accurate price quote possible, we typically follow these steps: | - To generate the most accurate price quote possible, we typically follow these steps: | ||
- We first add the feature inside Bugzilla, what we use for issue / feature tracking.< | - We first add the feature inside Bugzilla, what we use for issue / feature tracking.< | ||
Line 38: | Line 55: | ||
- Features that have been quoted this way, we will record the " | - Features that have been quoted this way, we will record the " | ||
< | < | ||
- | - We will send you the price quote, along with the detailed "task list" that was generated as part of the quote process. | + | - We will send you the price quote, along with the detailed "task list" that was generated as part of the quote process. |
- | Because of the process explained above, we are usually very accurate with the estimate, so once we quote adding a feature the price stands even if the " | + | Because of the process explained above, we are usually very accurate with the estimate, so once we quote adding a feature the price stands even if the " |
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 ===== | ||
- | One common misunderstanding when it comes to having a feature added, is the development cost for adding the feature. | + | One common misunderstanding when it comes to having a feature added, is the development cost for adding the feature. |
By sponsoring a feature, you are helping to cover the development cost, meaning the amount of time a Geodesic developer has to spend working on adding that feature that they might otherwise be spending on something else. | By sponsoring a feature, you are helping to cover the development cost, meaning the amount of time a Geodesic developer has to spend working on adding that feature that they might otherwise be spending on something else. |