Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dbkr/rebrand #2285

Merged
merged 6 commits into from
Sep 19, 2016
Merged

Dbkr/rebrand #2285

merged 6 commits into from
Sep 19, 2016

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Sep 19, 2016

No description provided.

@dbkr dbkr merged commit 0f2c41d into develop Sep 19, 2016
@notslang
Copy link

what is the name change for?

@ara4n
Copy link
Member

ara4n commented Sep 25, 2016

@slang800 Vector is a bit bland and boring, whereas Riot is rather more catchy and descriptive for an app which aims to tear down the walls of the walled gardens. https://medium.com/@RiotChat/lets-riot-f5b0aa99dc8e#.kabkbcujg has more details :)

@4nd3r
Copy link
Contributor

4nd3r commented Sep 25, 2016

sorry for spam, but Vector felt more professional, Riot looks like bad marketing people won the argument.

but in the end it's just a name :>

@notslang
Copy link

I'm fine with the name change. I'd agree with @4nd3r that vector was more professional (and had a very obvious connection to "matrix"), but so long as you can quickly rename everything before it becomes a well-known project (the point at which a name change is likely to confuse people) I think it'll be fine.

I just asked since there wasn't any documentation on why the change was happening or what it signifies (whether it was a rebranding, or an issue with an existing trademark, or a distinction between the hosted vector client & the project itself). So far, the readme doesn't even mention that it happened.

@t3chguy t3chguy deleted the dbkr/rebrand branch May 12, 2022 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants