I always wanted this as a cook & hacker. Not spend too much time writing a recipe from scratch. More importantly DRY.
EDIT: title was changed to make this clear.
Great site & concept though. I'll be sure to bookmark it and look around later. I'm curious to see how you applied the forking (I like the pun) concept on recepes for people that aren't familiar with software version control systems.
But here’s a peep. http://d.pr/i/DB3L
When you try to write a recipe, we figure out if the recipe exists and suggests a “Write a variation”.
The variation is essentially a fork http://d.pr/i/fG09 that allows you to delete ingredients, change prep methods etc.
You can manually "fork" a recipe too.
I assume you are working on design? Design will be really important. Having fun factor in the design combined with the social aspect of forking recipes could really do well, but you gots some work to do!
That's pretty slick.
Well done! (Only immediate thought is that you should make the "Write a Variation" more prominent the way Forking is more prominent on GitHub.)
The name bit is a bit surprising to me. As an Indian the name struck with everyone. But when I came over to the US, the feedback for the name from the average user was – I’d say not so great.
We are a team of 4 people in 3 continents, none of whom have seen each other http://www.cucumbertown.com/humans and all through our dev process this never struck us. Guess we are the angels on earth.
There is a story behind the name Cucumbertown. http://www.cucumbertown.com/faq/#whatupwithname
I realized the name issue during my first dialogue at Sand Hill. The conversations went pretty well until there was a pause towards the end. A partner chalked in words together and politely asked me if I was open to changing the name. That’s when it struck. But then we have a reason for it…
The site is in beta state and we approve people along the way.
I’ve approved on HN folks in queue now. I didn’t see Tucker there.
We just launched http://tcrn.ch/REN2RU our public beta.