Originally published on: 12/6/2006 5:53:35 AM
So, that's the pain point and a set of requirements. Then there's the fact that I've been itching to use Symfony on something. I feel like a kid with a new labelmaker, running through the house looking for stuff to label. However, rather than just slapping "large saucepan" labels onto all of the pots in the cabinet, I'd like to use it on something useful.
So far, we've got a mild development storm brewing (a problem and a solution), but it's not yet ready to explode into the perfect storm.
What's that? Shelly's starting a new class in her MBA program? Crap. I think I hear thunder in the distance. With Shelly studying, I've got uninterrupted leisure time (the time we carve out to not be accountable to anyone for it) available. In December, January and February. In Minnesota.
So, I've got time, a problem and a solution I want to implement. I think this storm is nigh unto inevitable.
On Sunday, I started sketching out data models, etc. and have been digging into the symfony docs pretty heavily. However, the problem I keep running into is the naming of things which are clearly looking for the name of the project. See, I don't know what to call it.
It's an app to dig through RSS-sourced information. It's a content research desktop. It's an RSS reader. But, it's nameless. Any suggestions?
I need whatever name I pick to be available as a .com domain name for future distribution and public availability. I also don't want a name that screams "Web 2.0" or has anything spelled wrong. I am pretty much certain that many of the current "trendy" names are going to sound just as cringe-worthy as "cyber" does as a prefix today.