liku
New Member
- Joined
- Apr 29, 2008
- Messages
- 6
- Reaction score
- 0
questions and proposals =)
Ok, i am sorry but i still havent well understood what it will be done. I have many concerns and questions:
As i understood SUSHI is currently free but will be priced in the future for 30$/year.
People who bought it will be able to run update-source, update-fixe and update-script. Other people will have to burn a new iso right?
What will be the plus offered by SUSHI?
[off topic] will we get a way to shutdown/schedule shutdown of the server in the gui, or the use of webmin or ssh are the only envisaged solution [/off topic] ?
I think it's a good idea to keep it low and stable. For 30$ i will make a duty to ensure it is being paid for commercial use. As low as 30$ i will also paid it for home use without hesitation.
Keeping it low priced and and stable will make more casual/home user subscribe to it
Afterall, you got more than 40k downloads, let's say that half of them are a real system and then half of them pay for it: that’s about a starting potential of 300k$/year. As the community grows, this amount will also grow. To pay 3 developers 150k$ a year is way too low, but as a starting point I think it’s a good perspective considering the enormous growing potential.
For commercial, I thinking doing the same approach those telephony companies have done is not the good way to go: one of the selling point is that there is no resctriction about users/system than the hardware can take, not the same way that telcos goes like billing for slice of 1-2 user then 5-10 and so on.
but something has to be done to still stay fair, 30$ for large business is rediculous, maybe some writting in one EULA would be a good thing.
I migrated from Swisscom [swiss telco] 23 small company this year, just because they were paying a 150.- Chf monthly fee [almost 180$ with the current change rate] for supporting their old pbx. They were getting nothing from these money paid and liked the idea to have their own open telephon system financed by this fee they stopped to pay.
I also think that for commercial use, copying in some sort Microsoft update server/service but in pull, can be a good guideline: Just think than bigger organisation's policy will restrict them to update their server like they restrict them to being updated from M$ update server. They use their own WSUS server locally. I think it's a good idea to kept that in mind. Currently i only work with little to micro enterprises[from 5 to 30 computer and 15 to 160 worker] but i am in touch with way bigger for witch i sell consulting, some of my customers for consulting have more 45 Wsus Server. Bigger company are currently evaluating some alternative to Microsoft product concerning voip and they multiply the mandates with me requesting more stats and data about my current base of installed products.
Licence Donate Fee: 120$ per installed system and also proposed for a year basis, can be soustracted from the taxe here. And will be parted this way: Asterisk 30 Freepbx 45 Piaf 45, I have had many dilema as where to go, how to collect it, where to give, witch project need contribution in order to stay alive and so on, then I concluded that I could not spend so many time following all project needed in the software that I use. I have betted on you and freepbx, assuming that you will make the good choice for me. All I do is collecting the found, waiting the end of the year then sending them. As I use all of your forum but do not participate/contribute as I wanted, I just created some little association, who will collect the found and paid them, this way I gave my time in the way I could be more productive.
I knew that would be a little of topic, I wanted to say that SUSHI and LDF [contributing and donating to the project/community] are TWO DIFFERENT thing and must be dealt separately.
If I may have appeared offencive, I apologize, the same for my very bad English.
Cheer
Best regards
liku
Ok, i am sorry but i still havent well understood what it will be done. I have many concerns and questions:
As i understood SUSHI is currently free but will be priced in the future for 30$/year.
People who bought it will be able to run update-source, update-fixe and update-script. Other people will have to burn a new iso right?
What will be the plus offered by SUSHI?
[off topic] will we get a way to shutdown/schedule shutdown of the server in the gui, or the use of webmin or ssh are the only envisaged solution [/off topic] ?
About the price:
I think it's a good idea to keep it low and stable. For 30$ i will make a duty to ensure it is being paid for commercial use. As low as 30$ i will also paid it for home use without hesitation.
Keeping it low priced and and stable will make more casual/home user subscribe to it
Afterall, you got more than 40k downloads, let's say that half of them are a real system and then half of them pay for it: that’s about a starting potential of 300k$/year. As the community grows, this amount will also grow. To pay 3 developers 150k$ a year is way too low, but as a starting point I think it’s a good perspective considering the enormous growing potential.
For commercial, I thinking doing the same approach those telephony companies have done is not the good way to go: one of the selling point is that there is no resctriction about users/system than the hardware can take, not the same way that telcos goes like billing for slice of 1-2 user then 5-10 and so on.
but something has to be done to still stay fair, 30$ for large business is rediculous, maybe some writting in one EULA would be a good thing.
I migrated from Swisscom [swiss telco] 23 small company this year, just because they were paying a 150.- Chf monthly fee [almost 180$ with the current change rate] for supporting their old pbx. They were getting nothing from these money paid and liked the idea to have their own open telephon system financed by this fee they stopped to pay.
I also think that for commercial use, copying in some sort Microsoft update server/service but in pull, can be a good guideline: Just think than bigger organisation's policy will restrict them to update their server like they restrict them to being updated from M$ update server. They use their own WSUS server locally. I think it's a good idea to kept that in mind. Currently i only work with little to micro enterprises[from 5 to 30 computer and 15 to 160 worker] but i am in touch with way bigger for witch i sell consulting, some of my customers for consulting have more 45 Wsus Server. Bigger company are currently evaluating some alternative to Microsoft product concerning voip and they multiply the mandates with me requesting more stats and data about my current base of installed products.
LDF proposal
Another proposal is the LDF that I am trying to make my customer pay, it does not replace SUSHI, and I think goes well wit it: It’s a small optional fee I am trying to collect:Licence Donate Fee: 120$ per installed system and also proposed for a year basis, can be soustracted from the taxe here. And will be parted this way: Asterisk 30 Freepbx 45 Piaf 45, I have had many dilema as where to go, how to collect it, where to give, witch project need contribution in order to stay alive and so on, then I concluded that I could not spend so many time following all project needed in the software that I use. I have betted on you and freepbx, assuming that you will make the good choice for me. All I do is collecting the found, waiting the end of the year then sending them. As I use all of your forum but do not participate/contribute as I wanted, I just created some little association, who will collect the found and paid them, this way I gave my time in the way I could be more productive.
I knew that would be a little of topic, I wanted to say that SUSHI and LDF [contributing and donating to the project/community] are TWO DIFFERENT thing and must be dealt separately.
If I may have appeared offencive, I apologize, the same for my very bad English.
Cheer
Best regards
liku
Phone System 