New name for git.creek.fm
Introduction
Rather than git.creek.fm
this website should have a name that's more friendly, and less git
.
Why?
We're going to use this GitLab as a project management area for both developers and non-developers.
User groups
- Group 1: Stations, station managers, DJs: for their own website design projects, and possibly some various studio fix-it tasks.
- ... so it should have a name that's descriptive to non-developers.
- Group 2: Creek's core development: both the open-source, and closed source projects.
- ... so it should still respect developer terminology and mindset, rather than cover it up with a silly non-technical euphemism. This would introduce a subtle "ugh, they don't get it" in the minds of developers whenever they interact with this area.
Domain name ideas
rank #1
develop.creek.fm - - The safe one. This would work.
- It's an action in itself, if you say the domain name out loud: "develop Creek."
- But it's less "radio people" friendly -- but we are not ultimately aiming at radio anyway.
- Names:
- Developer Center
- Development Area
- ...these names are a bit long.
- Unlike "Studio" (below) it would not collide with future (hypothetical) projects, ones that probably ought to be called a "Studio".
dev.creek.fm
- Might work.
- Like, you get to make the dev area... or something.
- It's a bit confusing for developers: "Uh, is this a development version... of the development area?"
developers.creek.fm
- This is ok, but it's just three extra letters, versus simply "develop.creek.fm"
rank #2
studio.creek.fm - - Sounds good for radio people. Gives it a definite name of its own. "Creek Studio"
- For developers, it sort of resonates because of Visual Studio Code, and other studio words.
- ...and there are a lot of developer-musicians and developer-DJs that will use this area. So "Studio" still resonates well.
- Name: Creek Studio
- Sounds short and cool.
- But it just seems weird to "clone a repo" or connect
git
with a domain like:git://studio.creek.fm/open/integration
- ...oh wait, the URL will have git in it anyway, because of
git://
? -- Unless they usehttps://
...
- ...oh wait, the URL will have git in it anyway, because of
- Name may collide with something else if we call it the Studio.
- Like, the Control Panel itself -- the main area where DJs create stuff -- would make a lot of sense to be called the Studio.
- In the future, we might even make the Creek Control Panel into more of a Studio tool, with audio editing stuff. So...
- Like, the Control Panel itself -- the main area where DJs create stuff -- would make a lot of sense to be called the Studio.
build.creek.fm
- I like this because it's a catchy phrase on its own.
- And I like "building things".
- ...but it does not result in a good name: "Creek Build" or "Creek Building Area" -- nope.
source.creek.fm
- Evokes both source code, and water.
- "View Source"
- The source of a flowing body of water, from which the water originates.
- Names, in real-world usage:
- Creek Source.
- "Please go to the Creek Source to see the website discussion area for your station."
- Creek Source.
projects.creek.fm
- This is interesting. But projects are going to be a primary object on the main Creek website.
community.creek.fm
-
This is not as much a community -- the "community" would probably be something else in the future. Like, the Creek website itself -- or the whole thing, everything is a community.
-
Does not result in a very descriptive name.
create.creek.fm
- Matches the new Listen/Create tabs idea.
- Create sounds too much like creek though.
workplace.creek.fm
- Sounds too HP Enterprise-y.
craft.creek.fm
- I never liked the word "craft" since it's a bit elevated, arrogant, hipster. And then there's Kraft cheese. But, yes, it is also nautical (craft = boat) as in, water-related, creek-related. Though it would be a pretty big creek if it had a craft on it. More like a river at that point.
lab.creek.fm
- Short.
- But not very "radio" or "music".
- Refers to Git Lab.
- It means a workplace.
- Looks funny though?
- Potential trademark issue with GitLab? Probably... not.
git.creek.fm
- Keep this, since it will be developers mostly anyway?
- Most people will just be using the projects area that's in progress now.
Top names, with real world usage examples:
Developer Center
You can find your billing information in the Creek HQ, and your station's design project is in your Developer Center account, at http://develop.creek.fm
Clone the repo from http://develop.creek.fm/open/integration
Studio
You can find your billing information in the Creek HQ, and your station's design project is in your Studio account, at http://studio.creek.fm
Ok, then create an account at the Creek Studio, where we'll be working on your station website.
You can find your billing information in the Creek HQ, and your station's design project is in your Studio account, at http://studio.creek.fm