Yes, I finally decided to go with the BSD license, since I'd like to enable people to benefit from this, which might mean being able to add new tests without revealing the model answer :)
While building Texts.com, my CTO and I learned a ton by studying the path of GetchaBooks. They had shut down and decided to open source their code (http://getchabooks.com/open-source.html), which is a generous and noble thing to do.
I see it as good coding karma; and you never know the contacts you might make (I initially wanted to hire one of the creators; but I settled for buying him a few beers since he had just accepted another offer).
Hi Frank, I wrote most of the backend for GetchaBooks. Glad you got some value out of the source.
Even though I invested a fair amount of time in continuous refactoring while actively developing it, refactoring and documenting to a point where I wasn't embarrassed to make it public and could realistically say that someone else would be able to use (which ended up happening with tuftstext.com) and perhaps modify or extend it was a significant learning experience.
IIRC I spent a few weeks on that, but I think it was worth it. Instead of setting aside the project with a vague idea of the right way to do some things, I ended up actually having done them the right way, so now when I encounter a similar problem I know how to do it the right way the first time.
This is basically the same situation you would face if you were handing off code when leaving a company. This experience is one reason why I think it's important to develop and document your project to open source quality standards throughout the lifetime of the project.
And what better way to do that than to open source your code even for an active company? Usually you're probably not competing on tech, and I bet any community contribution you'd get is greater than the likelihood that someone will actually manage to maintain an instance of your code.
The books-by-course space is a perfect example of this. So many "startups" have duplicated so much work building these sites, when what you actually need to succeed is marketing. (The thing we took away from it, I think, is that you need per-school branded sites.) They should start sharing resources more.
What do you know, here's the college bookstore part of GetchaBooks extracted into an HTTP API, now with parallel scraping, that I just made public on Github: https://github.com/mwhite/bookstore-api Maybe it wouldn't be too hard to get working. But expect to get sued.
It is very cool to open source your software. That being said, I'd recommend you work with a native English speaker on your marketing if you plan to pursue another startup. The copy writing on the marketing site is bad enough that your code never mattered.
I feel bad your startup failed, but I'm grateful you decided to open source the project. I wish more people did the same since there are plenty of lessons to be learned. Plenty of public bulletins and blog posts discuss -- sometimes at length -- over what part management difficulties and other obstacles have played, but very few actually release technical details. Even more rare to see the source released.
Hope you fare better in your next venture. If you haven't started, you should.
That's the idea. The plan is to move anyone who wants to keep data onto private Azure instances, and then to close up shop. Maybe if anyone is interested in developing a customized version of the code, then I'll work on that in the future.
I thought I was the only person who attempted at creating startups with asp.net/azure before I switched to RoR. It looks like I was not alone! Kudos to the OP for open sourcing it.
[+] [-] neur0mancer|12 years ago|reply
Btw, could you clarify exactly which type of licence you are using (https://github.com/paf31/initialround/blob/master/LICENSE). Is it something like BSD?
[+] [-] paf31|12 years ago|reply
[+] [-] pkfrank|12 years ago|reply
I see it as good coding karma; and you never know the contacts you might make (I initially wanted to hire one of the creators; but I settled for buying him a few beers since he had just accepted another offer).
[+] [-] mwhite|12 years ago|reply
Even though I invested a fair amount of time in continuous refactoring while actively developing it, refactoring and documenting to a point where I wasn't embarrassed to make it public and could realistically say that someone else would be able to use (which ended up happening with tuftstext.com) and perhaps modify or extend it was a significant learning experience.
IIRC I spent a few weeks on that, but I think it was worth it. Instead of setting aside the project with a vague idea of the right way to do some things, I ended up actually having done them the right way, so now when I encounter a similar problem I know how to do it the right way the first time.
This is basically the same situation you would face if you were handing off code when leaving a company. This experience is one reason why I think it's important to develop and document your project to open source quality standards throughout the lifetime of the project.
And what better way to do that than to open source your code even for an active company? Usually you're probably not competing on tech, and I bet any community contribution you'd get is greater than the likelihood that someone will actually manage to maintain an instance of your code.
The books-by-course space is a perfect example of this. So many "startups" have duplicated so much work building these sites, when what you actually need to succeed is marketing. (The thing we took away from it, I think, is that you need per-school branded sites.) They should start sharing resources more.
What do you know, here's the college bookstore part of GetchaBooks extracted into an HTTP API, now with parallel scraping, that I just made public on Github: https://github.com/mwhite/bookstore-api Maybe it wouldn't be too hard to get working. But expect to get sued.
[+] [-] jcampbell1|12 years ago|reply
[+] [-] paf31|12 years ago|reply
[+] [-] eksith|12 years ago|reply
Hope you fare better in your next venture. If you haven't started, you should.
Good luck!
[+] [-] evolve2k|12 years ago|reply
[+] [-] paf31|12 years ago|reply
[+] [-] sourc3|12 years ago|reply
[+] [-] cfontes|12 years ago|reply
[+] [-] paf31|12 years ago|reply
[+] [-] dodyg|12 years ago|reply
[+] [-] chatman|12 years ago|reply
[+] [-] Sovietaced|12 years ago|reply
[+] [-] kalagan|12 years ago|reply