Name

[Sammidysam]

We should definitely come up with a name eventually. We can keep our ideas here, but definitely do not sit thinking of a name when you could be doing better work instead.

[rye]

I know that we suggested "scoutify" before, and I like the idea of using that name for this new project. I think longer or more keypres-intensive names like "scout3000" are disadvantageous because it's harder to type and it doesn't roll off the hands, so to say.

[Sammidysam]

I thought that we already threw scout3000 out of the list of options. I think something new outside of scoutify would probably be nice. Anything that mixes FRC/FIRST and scouting in a name would be fantastic.

[vmai]

I agree with @Sammidysam. Since "scoutify" was already used for an old project I wouldn't want to reuse it. I believe something like "FIRScouT" was something that we mentioned.

[Sammidysam]

Also there was "FReCon" which sounded kind of nice.

[rye]

I know @fishyfish235 and @tigerh's system ("FRCdev") uses that strategy, but appending "dev" to one of [ "FRC", "FIRST" ] seems a bit too generic. Something like FIRScouT would be good, but since this application will only really apply to FRC competitions something that uses FRC as a root would be more specific.

[vmai]

We just appended "dev" because it contained a lot of other development stuff that our team created.

[rye]

To me, even something like "FRCScout" sounds good. It's short, to-the-point, and rather easy to type out.

[rye]

FRsCout? That's a little awkward to type.

[rye]

FRCScout or FRCscout are my preferences for names. Anyone else?

[Sammidysam]

I like FReCon (frecon) and FRCscout (frc-scout).

On Jul 11, 2014, at 9:00 PM, Kristofer Rye notifications@github.com wrote:

FRCScout or FRCscout are my preferences for names. Anyone else?

— Reply to this email directly or view it on GitHub.

[rye]

I like FReCon as well. Really I just want something that is not as generic as "scouting-project"; if we have to change it again that's fine.

[Sammidysam]

Another option to throw in: FseaRCh (fsearch). Thoughts?

[Sammidysam]

Ehh, it's not very original. Who here is against frecon?

[rye]

Here are the options I consider to be the most popular, in order of my preference, as well as some supporting arguments for them:

• FReCon (Gem name "frecon")

  • Original.
  • Short.
  • Fast to say.
  • Derives its naming from the truncation of the word "reconnaissance" ("recon"), which is a cool-sounding way to describe what we're doing at competitions:

  "exploring beyond the area occupied by friendly forces to gain vital information about enemy forces or features of the environment for later analysis" -- From Wikipedia, the free encyclopedia

• FRCScout (Gem name "frcscout")
  • Makes a lot of sense.
  • Does not mix "FRC" and anything related to scouting.

---

FReCon would require some explanation if people were curious as to how we named it, and they might think it's a silly name.

FRCScout seems unoriginal; it's slapping the name of an activity on the name of a competition. Plus it's not really an official API, so we might get into trademarking issues. It's also slow to say.

---

Personally, I prefer FReCon. I haven't heard a movement against it.

[vmai]

I'm learning more towards FReCon now. If no one is against that, I'd say let's go for that.

[Sammidysam]

So I'd like to hear from @tigerh, @samercier, @cg505, and @btgeek on the matter of how they feel about FReCon (frecon).

[braddoeswebdev]

Works for me.

[claire271]

I'm fine with it.

[rye]

I don't think @cg505 or @samercier are even reading their notifications at this point, so I'm pretty sure our decision is FReCon.

[samontea]

@krye you were a hundred percent right about me though it was kind of to be expected considering I was debating or thinking about debate 10-14 hours a day so you know. With eating and sleeping there wasn't that much time for notification reading. I really don't care though. This name seems fine enough.

[Sammidysam]

@cg505 is out-of-town, so I think we can conduct the name change. We have enough of a supermajority. We need to change the name of the organization and this repository.

On Jul 13, 2014, at 1:41 AM, Samuel Mercier notifications@github.com wrote:

@krye you were a hundred percent right about me though it was kind of to be expected considering I was debating or thinking about debate 10-14 hours a day so you know. With eating and sleeping there wasn't that much time for notification reading. I really don't care though. This name seems fine enough.

— Reply to this email directly or view it on GitHub.

[cg505]

Go ahead. On Jul 13, 2014 12:47 AM, "Sam Craig" notifications@github.com wrote:

@cg505 is out-of-town, so I think we can conduct the name change. We have enough of a supermajority. We need to change the name of the organization and this repository.

On Jul 13, 2014, at 1:41 AM, Samuel Mercier notifications@github.com wrote:

@krye you were a hundred percent right about me though it was kind of to be expected considering I was debating or thinking about debate 10-14 hours a day so you know. With eating and sleeping there wasn't that much time for notification reading. I really don't care though. This name seems fine enough.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/scouting-project/scouting-project/issues/9#issuecomment-48832607 .

[Sammidysam]

The account frecon is taken. What to do now?

[rye]

project-FReCon is available. We could use that.

[Sammidysam]

Or we could make the account frc-frecon and then have the repository be frecon. That could possibly associate us too closely to FRC, but I doubt it. I like frc-frecon better than project-FReCon.

[rye]

Or just frc-recon

[Sammidysam]

That might dissociate us from frecon too much. What do you think?

[rye]

True. I guess frc-frecon works.

[Sammidysam]

Any complaints from others about naming our organization frc-frecon and our repository frecon?

[vmai]

Nope, works for me.

[Sammidysam]

Conducting the name change now.

[Sammidysam]

Name change conducted.