Hello,
On 07/30/2004 06:32 PM, Rubem Pechansky wrote:
On the other hand you can always open the source of the library and develop closed source extensions or tools that make the development of your library more powerful and useful so it will be an advantage for people to buy those extensions and tools from you instead of developing themselves.
This is exactly what I have in mind. If I want this tool to be useful and popular, I know I can't make people pay for it, at least for non-commercial use (thanks, Hayden). But for that to happen I must first find a partner company who wants to invest a little bit and then add it to their portfolio. I think this is the best way to make it free.
Right, but before you release anything it is going to be hard to demonstrate to any partner/investor that what you have is interesting and has business potential because besides yourself you do not have any user base to show or even poll for potential business case.
If I were you, I would probably develop some tools to address specific needs of some clients that would pay so you can justify dedicating full time development of your library and tools. Releasing your library to the public would either provide you a user base to test it and suggest improvement as well a potential client base to provide you hints on possible products or services they would be willing to pay.
--
Regards, Manuel Lemos
PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/
PHP Reviews - Reviews of PHP books and other products http://www.phpclasses.org/reviews/
Metastorage - Data object relational mapping layer generator http://www.meta-language.net/metastorage.html
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
