I hate to sound all gatekeeper-y, and I am really excited that you're excited, but I don't think we're quite there yet, because we don't know what direction the project is going in. I can see how figuring that out might sound like a dev job, but in this case it's starting out as a community team project.
I also have an application called "Magic", because people kept telling me that the reports that used to take them days to run now only take seconds. "It's like magic!"
Moral of the story: Don't let me name applications
That also explains the names: "SEAFOAM", "OOPS", "IRVING"
I'm most proud of "OOPS". I called it "Other Order Processing System", because we already had an old one and this was to be the new, faster, better, more flexible one. I never called it "OOPS" during product meetings or discussions about development. Even after it was released, I never acronymed it. One of my users did it in a presentation and didn't realize it until it was on a power point slide and projecting to the audience.
All I got was "You did this on purpose, didn't you?"
Yes. Yes I did. :)
@Pops Seafoam was the result of "I'm going to pick a random name and hope you hate it so that we can come up with something else."
"bummer"? :P At some point, I don't really think attempting to catch all gibberish is worth the effort - it's not as high priority as spam/offensive posts.
