Hi all, I am developing a web-based feeds reader--FeedUp! in my spare time. FeedUp! is based on RubyOnRails, and aims to create a multi-user web 2.0 app. Features included in current version: 1. Multi-user. 2. Drag and drop to sort feeds list 3. Periodically resync your feeds without reloading page. 4. Click to read, keep item new, email articles to friends, and tag articles. Features will be included in next version: 1. Tags cloud in home page. 2. Integrate to Technorati Tags. 3. And more... I need your suggestions now. And should I open source FeedUp! to the community or provide free service based on close source development? -- Regards. Yufan
Sorry, forget give you the link. http://feedup.ivanshi.com 2005/8/15, yufan shi <yufanshi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:> Hi all, > I am developing a web-based feeds reader--FeedUp! in my spare time. > FeedUp! is based on RubyOnRails, and aims to create a multi-user web > 2.0 app. > > Features included in current version: > 1. Multi-user. > 2. Drag and drop to sort feeds list > 3. Periodically resync your feeds without reloading page. > 4. Click to read, keep item new, email articles to friends, and tag articles. > > Features will be included in next version: > 1. Tags cloud in home page. > 2. Integrate to Technorati Tags. > 3. And more... > > I need your suggestions now. And should I open source FeedUp! to the > community or provide free service based on close source development? > -- > Regards. > > Yufan >-- Regards. Yufan
I''m always curious. How do coders who open up their code to the opensource community make money? Julian. On 15/08/2005, at 7:52 PM, yufan shi wrote:> Hi all, > I am developing a web-based feeds reader--FeedUp! in my spare time. > FeedUp! is based on RubyOnRails, and aims to create a multi-user web > 2.0 app. > > Features included in current version: > 1. Multi-user. > 2. Drag and drop to sort feeds list > 3. Periodically resync your feeds without reloading page. > 4. Click to read, keep item new, email articles to friends, and tag > articles. > > Features will be included in next version: > 1. Tags cloud in home page. > 2. Integrate to Technorati Tags. > 3. And more... > > I need your suggestions now. And should I open source FeedUp! to the > community or provide free service based on close source development? > -- > Regards. > > Yufan > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
It is always a difficult decision whether to release open source/free or as a commercial service. I think you need to decide a) what you would prefer and b) can you afford to make it free? You could do what many people do is offer a free, more restricted version, and also offer a paid version to get access to more..assuming it is a hosted service. Regards, David Mytton http://www.olate.co.uk yufan shi wrote:> Hi all, > I am developing a web-based feeds reader--FeedUp! in my spare time. > FeedUp! is based on RubyOnRails, and aims to create a multi-user web > 2.0 app. > > Features included in current version: > 1. Multi-user. > 2. Drag and drop to sort feeds list > 3. Periodically resync your feeds without reloading page. > 4. Click to read, keep item new, email articles to friends, and tag articles. > > Features will be included in next version: > 1. Tags cloud in home page. > 2. Integrate to Technorati Tags. > 3. And more... > > I need your suggestions now. And should I open source FeedUp! to the > community or provide free service based on close source development?
Julian Leviston wrote:> I''m always curious. > > How do coders who open up their code to the opensource community make > money?Typically I reckon that the only opensource projects that make any money are those that provide frameworks. Take for instance JBoss, which has an opensource J2EE container, but make their money (I believe) from technical support and training. Matt
Matthew Denner wrote:> Julian Leviston wrote: > >> I''m always curious. >> >> How do coders who open up their code to the opensource community >> make money? > > > Typically I reckon that the only opensource projects that make any > money are those that provide frameworks. Take for instance JBoss, > which has an opensource J2EE container, but make their money (I > believe) from technical support and training. > > Matt > _______________________________________________How I make money is simpler. I write in house applications. I borrow from open source to make me more productive so that I am worth more to my employer, and in turn, the improvements I make to the open source tools get released back. I benefit, my employer benefits, and the open source community benefits. Everyone makes more money.
Yes I understand how things from the point of view of the open source developer USING the released code are better for all, and I understand that the original releaser of the open source released code gains mindshare and increased improvement of his project, but what does he gain in terms of profit? I guess what you''re saying is that 37signals gains by their code being improved and therefore all of the programs that they develop that sit on top of it gets improved for free... (therefore their increased profitability is assured). That''s cool for frameworks (as matt said) - but for other programs it doesn''t appear to be a useful tool from a money point of view. Maybe businesses like Apple would disagree :-) Julian. On 15/08/2005, at 9:51 PM, Grant Johnson wrote:> Matthew Denner wrote: > > >> Julian Leviston wrote: >> >> >>> I''m always curious. >>> >>> How do coders who open up their code to the opensource community >>> make money? >>> >> >> >> Typically I reckon that the only opensource projects that make any >> money are those that provide frameworks. Take for instance JBoss, >> which has an opensource J2EE container, but make their money (I >> believe) from technical support and training. >> >> Matt >> _______________________________________________ >> > > How I make money is simpler. I write in house applications. I > borrow from open source to make me more productive so that I am > worth more to my employer, and in turn, the improvements I make to > the open source tools get released back. I benefit, my employer > benefits, and the open source community benefits. Everyone makes > more money. > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
> That''s cool for frameworks (as matt said) - but for other programs it> doesn''t appear to be a useful tool from a money point of view. My company has released, and still maintains, a free LGPL PHP download manager. This was an extremely good move for us because it is incredibly popular and as a result, users come to our website and see our other products and services. It is a useful promotional tool. Regards, David Mytton http://www.olate.co.uk Julian Leviston wrote:> Yes I understand how things from the point of view of the open source > developer USING the released code are better for all, > and I understand that the original releaser of the open source released > code gains mindshare and increased improvement of his project, but what > does he gain in terms of profit? > > I guess what you''re saying is that 37signals gains by their code being > improved and therefore all of the programs that they develop that sit > on top of it gets improved for free... (therefore their increased > profitability is assured). > > That''s cool for frameworks (as matt said) - but for other programs it > doesn''t appear to be a useful tool from a money point of view. > > Maybe businesses like Apple would disagree :-) > > Julian. > > On 15/08/2005, at 9:51 PM, Grant Johnson wrote: > >> Matthew Denner wrote: >> >> >>> Julian Leviston wrote: >>> >>> >>>> I''m always curious. >>>> >>>> How do coders who open up their code to the opensource community >>>> make money? >>>> >>> >>> >>> Typically I reckon that the only opensource projects that make any >>> money are those that provide frameworks. Take for instance JBoss, >>> which has an opensource J2EE container, but make their money (I >>> believe) from technical support and training. >>> >>> Matt >>> _______________________________________________ >>> >> >> How I make money is simpler. I write in house applications. I >> borrow from open source to make me more productive so that I am worth >> more to my employer, and in turn, the improvements I make to the open >> source tools get released back. I benefit, my employer benefits, >> and the open source community benefits. Everyone makes more money. >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Hi all, Thank you very much first! After read all the replies here, I understand that open source is a good way to spread your company''s brand and your personal fame , and make more and more people trust on your ability. But it seems it''s hard to create a reliable business model by open source business application(here I mean applications providing very high level and focused business features, opposite to frameworks) . For my application FeedUp!, I prefer free service. 2005/8/15, David Mytton <david-nkCc03+qR4SsTnJN9+BGXg@public.gmane.org>:> > That''s cool for frameworks (as matt said) - but for other programs it > > doesn''t appear to be a useful tool from a money point of view. > > My company has released, and still maintains, a free LGPL PHP download > manager. This was an extremely good move for us because it is incredibly > popular and as a result, users come to our website and see our other > products and services. It is a useful promotional tool. > > Regards, > > David Mytton > http://www.olate.co.uk > > > Julian Leviston wrote: > > Yes I understand how things from the point of view of the open source > > developer USING the released code are better for all, > > and I understand that the original releaser of the open source released > > code gains mindshare and increased improvement of his project, but what > > does he gain in terms of profit? > > > > I guess what you''re saying is that 37signals gains by their code being > > improved and therefore all of the programs that they develop that sit > > on top of it gets improved for free... (therefore their increased > > profitability is assured). > > > > That''s cool for frameworks (as matt said) - but for other programs it > > doesn''t appear to be a useful tool from a money point of view. > > > > Maybe businesses like Apple would disagree :-) > > > > Julian. > > > > On 15/08/2005, at 9:51 PM, Grant Johnson wrote: > > > >> Matthew Denner wrote: > >> > >> > >>> Julian Leviston wrote: > >>> > >>> > >>>> I''m always curious. > >>>> > >>>> How do coders who open up their code to the opensource community > >>>> make money? > >>>> > >>> > >>> > >>> Typically I reckon that the only opensource projects that make any > >>> money are those that provide frameworks. Take for instance JBoss, > >>> which has an opensource J2EE container, but make their money (I > >>> believe) from technical support and training. > >>> > >>> Matt > >>> _______________________________________________ > >>> > >> > >> How I make money is simpler. I write in house applications. I > >> borrow from open source to make me more productive so that I am worth > >> more to my employer, and in turn, the improvements I make to the open > >> source tools get released back. I benefit, my employer benefits, > >> and the open source community benefits. Everyone makes more money. > >> _______________________________________________ > >> Rails mailing list > >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > >> http://lists.rubyonrails.org/mailman/listinfo/rails > >> > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Regards. Yufan
On Mon, 2005-08-15 at 19:56 +1000, Julian Leviston wrote:> I''m always curious. > > How do coders who open up their code to the opensource community make > money?There is no one way this happens. Some have business models around selling support for those who don''t have time or expertise in a field. Others have hardware that is sold and the software is just a good way of promoting hardware sales. I''d say support is probably the biggest money maker for open source contributors. I make a salary out of holding together a mix of open source and proprietary applications. When I can I contribute back to those apps I use the most. Then again, there are apps I choose to play with and may modify that are hobbies to me. I am into ham radio, and some of the applications I would use in ham radio may get patches to make me happier. I also occasionally help others with their apps. Point here being that once my basic needs are met, there is still time available for me to scratch the mental itch of having a hard problem to solve. Not everything is about profit. -- Steven Critchfield <critch-wQLwMjUOumVBDgjK7y7TUQ@public.gmane.org>
Support isn''t really a direct money maker though, is it? It''s a by- product. You still have to put effort into it, and in the end you''re being paid for your supporting the product, and someone who does it better than you can be paid more - even though you''ve dreamed up and put forth the beginnings to your app and you manage it. Just interesting. Julian. On 16/08/2005, at 7:50 AM, Steven Critchfield wrote:> On Mon, 2005-08-15 at 19:56 +1000, Julian Leviston wrote: > >> I''m always curious. >> >> How do coders who open up their code to the opensource community make >> money? >> > > There is no one way this happens. Some have business models around > selling support for those who don''t have time or expertise in a field. > Others have hardware that is sold and the software is just a good > way of > promoting hardware sales. > > I''d say support is probably the biggest money maker for open source > contributors. I make a salary out of holding together a mix of open > source and proprietary applications. When I can I contribute back to > those apps I use the most. > > Then again, there are apps I choose to play with and may modify > that are > hobbies to me. I am into ham radio, and some of the applications I > would > use in ham radio may get patches to make me happier. I also > occasionally > help others with their apps. Point here being that once my basic needs > are met, there is still time available for me to scratch the mental > itch > of having a hard problem to solve. > > Not everything is about profit. > -- > Steven Critchfield <critch-wQLwMjUOumVBDgjK7y7TUQ@public.gmane.org> > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
On Tue, 2005-08-16 at 22:13 +1000, Julian Leviston wrote:> Support isn''t really a direct money maker though, is it? It''s a by- > product. You still have to put effort into it, and in the end you''re > being paid for your supporting the product, and someone who does it > better than you can be paid more - even though you''ve dreamed up and > put forth the beginnings to your app and you manage it.It may not be direct payment for the original effort, but the original effort is what created the market for which you are then competing in. I would venture a guess that most new markets work similarly. The initial research and development isn''t directly paid for but rather is paid for by services or more likely later sales. So I would say that carving out a niche in a larger market and then positioning yourself as a primary resource leads to a pretty good chance of making money.> On 16/08/2005, at 7:50 AM, Steven Critchfield wrote: > > > On Mon, 2005-08-15 at 19:56 +1000, Julian Leviston wrote: > > > >> I''m always curious. > >> > >> How do coders who open up their code to the opensource community make > >> money? > >> > > > > There is no one way this happens. Some have business models around > > selling support for those who don''t have time or expertise in a field. > > Others have hardware that is sold and the software is just a good > > way of > > promoting hardware sales. > > > > I''d say support is probably the biggest money maker for open source > > contributors. I make a salary out of holding together a mix of open > > source and proprietary applications. When I can I contribute back to > > those apps I use the most. > > > > Then again, there are apps I choose to play with and may modify > > that are > > hobbies to me. I am into ham radio, and some of the applications I > > would > > use in ham radio may get patches to make me happier. I also > > occasionally > > help others with their apps. Point here being that once my basic needs > > are met, there is still time available for me to scratch the mental > > itch > > of having a hard problem to solve. > > > > Not everything is about profit. > > -- > > Steven Critchfield <critch-wQLwMjUOumVBDgjK7y7TUQ@public.gmane.org> > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails-- Steven Critchfield critch-wQLwMjUOumVBDgjK7y7TUQ@public.gmane.org KI4KTY
We''ve recently decided to open source our main software application, which we were originally going to keep closed. Here are some of the reasons: 1. The market was saturated with proprietary solutions whose products were sub-par. 2. Open sourcing provides us with the leverage of the open source community cutting down substantially on development costs and time to market. 3. The open source community provides maximum adaptability and evolution of our product due to the nature of community participants and reflection. Competing vendors with a handful of paid developers cannot compete with the potentially large and diverse group of developers. 4. We saw this as a stepping stone to other possible products and solutions. By open sourcing our flagship product, we encourage and gather branding in the market. 5. A tremendous amount of positive PR can be generated from the community which would otherwise be a burdening cost in the form of marketing campaigns. 6. There was no guarentee that a closed source solution would in fact demonstrate profitability given the current market conditions. 7. The nature of our market allows for greater cooperation with government, non-profits, and international organizations with an open source product. I''m sure there are more reasons, but I can''t think of them at the moment. When we do announce the release (which we will on this list since the product is being developed with RoR) I will post an article explaining our rational a little more clearly from a business model and cashflow perspective. -dave -- ~~~~~~~~~~~~~~~~~~~ D''Andrew Thompson http://dathompson.blogspot.com
On Aug 15, 2005, at 5:56 AM, Julian Leviston wrote:> I''m always curious. > > How do coders who open up their code to the opensource community > make money?Lots of ways -- though my personal brand is best described as commons based peer production. Easiest way to figure that out is google for "Commons Based Peer Production" and read some =) -Brian> > Julian. > > > On 15/08/2005, at 7:52 PM, yufan shi wrote: > > >> Hi all, >> I am developing a web-based feeds reader--FeedUp! in my spare time. >> FeedUp! is based on RubyOnRails, and aims to create a multi-user web >> 2.0 app. >> >> Features included in current version: >> 1. Multi-user. >> 2. Drag and drop to sort feeds list >> 3. Periodically resync your feeds without reloading page. >> 4. Click to read, keep item new, email articles to friends, and >> tag articles. >> >> Features will be included in next version: >> 1. Tags cloud in home page. >> 2. Integrate to Technorati Tags. >> 3. And more... >> >> I need your suggestions now. And should I open source FeedUp! to the >> community or provide free service based on close source development? >> -- >> Regards. >> >> Yufan >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > >