New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 762845 link

Starred by 1 user
Status: Fixed
Owner:
█ adolimpio@google.com
Email to this user bounced
Closed: Sep 2017
Cc:
█ amineer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Chromium Dash Feedback - Optimize login workflow

Project Member Reported by hablich@chromium.org, Sep 7 2017 
In the old Chromiumdash there was a clear call to action that a login is required in order to make the page work correctly. In them migrated version this is no longer the case and it is not obvious to users that a login would be a good idea in order to:

- Show commits in commits/ per default
- Make the API calls using CORS work

I know, technically a login is not required because we are behind Googleplex for now. What is the plan when this is not the case anymore? Can we make login mandatory?

Comment 1 by amineer@chromium.org, Sep 7 2017 

No, we are not making login mandatory - the plan is for all of this to be publicly accessible where possible.  There are many different use cases I'd like to support for people that have no formal connection to Chromium / Chrome at all, e.g. seeing fixes in a given release, looking up our schedule, seeing a list of recent releases & current percent deployment for stable pushes, etc.  Requiring login prevents them from doing that, which cuts loads of value out of this whole thing.

- Show commits in commits/ per default
With the search feature in place, this should be much more natural.  For non-logged in users we have other bugs requesting we just send a blank search, and show the most recent 30 commits in the Chromium repo by default.  I think between these two users should never see a blank page and can easily get where they need to go, but let me know 

- Make the API calls using CORS work
This is a bug - we shouldn't be firing requests we know won't be completed successfully, much like we don't try to make a call to Monorail when a user isn't authenticated.  For views / specific chunks of data that absolutely require login, we should come up with some language the highlight the need and benefit of logging in, and display that to the user.  We should talk about what this will look like.

Comment 2 by hablich@chromium.org, Sep 13 2017 

For second point I just created https://bugs.chromium.org/p/chromium/issues/detail?id=764628

Comment 3 by adolimpio@google.com, Sep 19 2017

Owner: adolimpio@google.com
Status: Started (was: Unassigned)
For the first point there is a bug now: https://bugs.chromium.org/p/chromium/issues/detail?id=766214 

(Assigning to me since I'm working on both bugs)
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 20 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/cb3e4bc9b796b70a99156f5468458d30de9a3120

commit cb3e4bc9b796b70a99156f5468458d30de9a3120
Author: Andrea D'Olimpio <adolimpio@google.com>
Date: Wed Sep 20 08:56:57 2017
►

Sign in to add a comment