Better public-facing project name about freddy HOT 24 CLOSED

QuickAndEasyJSON

from freddy.

Name it after a Transformer. Reflector, Perceptor

from freddy.

Or maybe use our "cowboy/ranch" motief.

http://ridesouthdakota.com/cowboy-slang-dictionary.html

FairShake

from freddy.

👍 for ranch theme, but the technique overall is not scalable (Android uses "Ranch Hand" as their dumping ground library, which is not en vogue with iOS.)

from freddy.

Greased Lightning - Anything very fast

from freddy.

@lyricsboy had a fun suggestion: Freddy (as in Freddy vs. JSON). Yuck yuck yuck. 😆

from freddy.

+1 on Freddy. We can have an anthropomorphic icon. Can nickname it “Fast
Freddy” (assuming it is fast - I haven’t been following close enough)

On Fri, May 29, 2015 at 5:04 PM, mdmathias [email protected] wrote:

@lyricsboy https://github.com/lyricsboy had a fun suggestion: Freddy
(as in Freddy vs. JSON). Yuck yuck yuck. [image: 😆]

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from freddy.

We will continue to make it faster in order to satisfy your naming desires. No other reason, just that one.

from freddy.

My work here is done.

On Friday, May 29, 2015, Zachary Waldowski [email protected] wrote:

We will continue to make it faster in order to satisfy your naming
desires. No other reason, just that one.

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from freddy.

So are we agreed on Freddy? If so, I bet we could get design to gin us up a fun logo. And we'll need to rename all the things...

from freddy.

I think it's a good name.

from freddy.

I'm taking this on. Here's my plan:

• Rename the xcode project
• Rename the targets/schemes
• update .travis.yml
• Find and replace all occurrences in text files
• Rename the repository

At some point it will be good to have an introduction/explainer for the name in the README, but I may task that on #18

from freddy.

Kar is working on a Freddy icon for us.

from freddy.

I realize that I am way late to the discussion ... but just wondering if this work has been started or has just been discussed here.

How are people feeling about the name "Freddy" after 5 months? Still like it?

My only concern with the name is that it doesn't sound professional. I realize that open source libraries are all about having fun names that only have some subtle, clever relationship to what it is that they do, but I wonder if we might get more traction with something stiff and boring and "professional sounding" or inclusive of our name or at least the term "JSON"? Part of the push to get BNR into the open source is to promote brand awareness. It's to get butts in seats. It's to remind companies that we do consulting work as well. There is nothing about the usage of "Freddy" that would remind me of BNR. Except for maybe the one time when I read the README, or really paid attention to the github URL, I would likely quickly forget who built it. Wouldn't it be nice if each time a developer copies their pod file from one project to the next, they are explicitly reminded of Big Nerd Ranch. Or if there is a discussion of what is the best JSON library to use, we get some name recognition.

I am not trying to be a Debbie Downer here, and I am happy to shut up if everyone still likes the name. I just wanted to put this out there.

So what kind of things might sound more "professional" yet less fun? Some things that came to mind were:

BNRJSON
NerdJSON
NerdyJSON
RanchJSON
BigNerdRanchJSON
BNRCoreJSON

Yeah ... totally uninspiring, I realize. Anyhow, just wanted to check in on this.

from freddy.

BNRJSON
CoreJSON

these are 2 that I think would work.

from freddy.

Something @davidahouse mentioned, which is worth recognizing is that if they use Carthage, the include looks like this:

github "BigNerdRanch/CoreJSON” and cocoapods `pod ‘BNRCoreJSON'

Perhaps something to keep in mind.

The point being that we might not have to include the branding in the project name, as it will be present when used. That being said, if it is just being discussed or written about, the branding wouldn't be included.

from freddy.

I still prefer Freddy. Having a fun icon and punny name will get attention. We will blog about it on our web site and it will be linked to us with Google juice.

"Core" is kind of meaningless in this context. Apple uses (used) it for their own frameworks, but it works there because apples have cores.

from freddy.

I can appreciate that Core isn't too useful, as it is really just an "extra word". I would likely be in favor of simply JSON. The thing about the branding has me concerned though as there are reviews like this one:

http://harlankellaway.com/blog/2015/07/05/swift-json-parsing-by-example/

There is nothing in here about the author of the libraries, which doesn't surprise me at all. We need to promote the BNR brand, and as more people talk about it, they need to be reminded of BNR, which has me leaning on BNRJSON.

Obviously, this is all just my opinion.

(This has me thinking about what would an extreme unbranded version look like. A fresh github account called unnamed with no reference to BNR. Nothing in the license or repo referring to BNR. Nobody would have any idea that we put it out. Then, I would ask ... what is the point for BNR spending the money on releasing anything in the open source. Perhaps only as an anonymous donation of sorts. This isn't bad or anything, but if we are trying to show off our core competency, anonymous doesn't seem like the best approach here. Anyhow, this leads me to think that it needs to be BNR branded.)

from freddy.

I agree with @lyricsboy on this completely. I think Freddy, or at least something unique and fun, has the best chance of success. People will still be exposed to BNR through our blog posts promoting Freddy, the GitHub page, the attribution at the top of every file, etc.

from freddy.

Do our files still have the default "All Rights Reserved" copyright claim in them, BTW? If so, we need a cleanup pass before public release that aligns that with the chosen license.

from freddy.

Here's my hypothetical conversation :)

Frank: "Hey Joe, which JSON library should I use?"
Joe: "Freddy"
Frank: "Cool"

vs.

Frank: "Hey Joe, which JSON library should I use?"
Joe: "BNRJSON"
Frank: "Cool. That's from Big Nerd Ranch, right?"
Joe: "Yep"
Frank: "You know they just released a new book last week? I wonder if we can convince our company to send us to training with them. Wouldn't that be cool? Those folks are sharp."
Joe: "Sure would be cool. Doesn't hurt to ask."
Frank: "On it."

from freddy.

We need to figure out how to agree on something here. So far, here is what I am seeing:

In favor of Freddy:
@lyricsboy
@cbkeur
@mdmathias
@markd2
@rcedwards

In favor of something less fun but more descriptive ala BNRJSON:
@hitsvilleusa
@davidahouse
@jeremy-w
@randomstep
@zorn

I certainly don't want to be speaking for anyone here, so if I got your vote wrong, let me know. Also, if this is not a democracy, that's fine too, just let me know.

I believe you can edit this comment to add your name in one of the camps

from freddy.

@jeremy-w: I'll take a license clause pass when we decide, since that also touches all the files.

from freddy.

Voting for Freddy!

from freddy.