Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

Need a new name #26

Open
stephaniehobson opened this issue Jun 24, 2015 · 8 comments
Open

Need a new name #26

stephaniehobson opened this issue Jun 24, 2015 · 8 comments

Comments

@stephaniehobson
Copy link
Contributor

Alternative suggestions:

  • codenosis
  • codealyzer
  • more better-er
@peterbe
Copy link
Contributor

peterbe commented Jun 26, 2015

  • bettercode
  • codealytics
  • codalyzer

@peterbe
Copy link
Contributor

peterbe commented Jun 26, 2015

Or, we call it webalyzer on the project/variable/etc level but the overarching name can be "MDN Pro Services".

Kinda like webalyzer===zamboni, zamboni!~= Mozilla Add-ons

@stephaniehobson
Copy link
Contributor Author

How about codalyzer on the project/variable level. If we're hugely successful we don't want to be using a product with a polluted name space and it'll be easier to change it now.

@groovecoder
Copy link
Contributor

👍 codalyzer now.

@peterbe
Copy link
Contributor

peterbe commented Jun 30, 2015

codealyzer > webalyzer. It's about the code, not the web.
That's a great incremental step! I'll all for it.

@peterbe
Copy link
Contributor

peterbe commented Jun 30, 2015

@peterbe
Copy link
Contributor

peterbe commented Jun 30, 2015

To whoever knows about trademarks and helps us here, note that https://github.com/laka/Codalyzer hasn't been touched for 5 years and doesn't even seem to be a "product" and its purpose seems more a script to support people who play Call of Duty which is very different from what we intend to do.

@groovecoder
Copy link
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants