Skip to content

docs(README): remove the "2" from Angular #2542

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

Closed
wants to merge 1 commit into from

Conversation

juristr
Copy link

@juristr juristr commented Jan 5, 2017

I wanted to support Igor's mission to remove the "2" from Angular on the web. Also the repo description would have to be adjusted. 😊

I wanted to support Igor's mission to remove the "2" from Angular on the web 😃. Also the repo description would have to be adjusted.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 5, 2017
@Splaktar
Copy link
Contributor

Splaktar commented Jan 6, 2017

There is already widespread confusion about angular-material for Angular 1.x and @angular/material/material2/angular-material2 for Angular 2+.

This spreads across StackOverflow and Google Groups where questions about "Angular Material for Angular 2+" keep getting posted in the angular-material for Angular 1.x forum. Then tags in StackOverflow keep getting posted with just angular-material when the question is about angular-material2 and Angular 2+ and not angular-material for Angular 1.x.

@jelbourn clarified that the 2 in the repo name isn't going away.

It seems like this PR does some to balance this by leaving the "for Angular version 2 onwards" text. But it seems like more needs to be done to disambiguate these repositories in the README.

[![npm version](https://badge.fury.io/js/%40angular%2Fmaterial.svg)](https://www.npmjs.com/package/%40angular%2Fmaterial)
[![Build Status](https://travis-ci.org/angular/material2.svg?branch=master)](https://travis-ci.org/angular/material2)
[![Gitter](https://badges.gitter.im/angular/material2.svg)](https://gitter.im/angular/material2?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)

This is the home for the Angular team's Material Design components built on top of Angular 2.
This is the home for the Angular team's Material Design components built for **Angular version 2 onwards**.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about just "for Angular v2.0.0+" ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understood them properly, @IgorMinar as well as @StephenFluin said to me one should mention "version 2" and not just "v2" to make it more explicit. More correct even, "Angular" and "version" should not be in the same sentence. So it should maybe be "for version 2+". I just thought that would create confusion with material 1 & 2...

@IgorMinar
Copy link
Contributor

I spoke with @jelbourn about the branding issue in the light of the #itsjustangular effort.

Unrelated to this PR, @juleskremer and I called for a meeting with Angular Devrel team to create a set of naming / branding guidelines for all things Angular. This will include how to deal with Angular 1 naming and branding (including angularjs.org) and other things like Angular Material.

This meeting will happen early next week when everyone is back in the office. Until then, let's hold any work on this until we get these guidelines. Otherwise we will likely need to redo this again in a few days. Sounds good?

@juristr
Copy link
Author

juristr commented Jan 6, 2017

👍 of course 😃

@andrewseguin
Copy link
Contributor

This change is a duplicate of the merged #2805

@Splaktar
Copy link
Contributor

Splaktar commented Mar 3, 2017

This has been causing quite a bit of confusion with my clients. They keep searching for Angular Material and finding material.angularjs.org and lots of references to AngularJS Material instead of Angular Material(2). A number of them have raised concerns about the library not working or wanting to consider another UI library because of these frustrations. So far I have been able to explain things, but it has certainly come at a cost of time and frustrated clients.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants