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

New OAuth login page #391

Open
wants to merge 37 commits into
base: master
Choose a base branch
from
Open

New OAuth login page #391

wants to merge 37 commits into from

Conversation

MonkeyDo
Copy link
Member

@MonkeyDo MonkeyDo commented Oct 6, 2022

This is just the presentational aspect so far, functionally it's going to be missing all the guts.

image

image

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

MonkeyDo added 4 commits May 11, 2023 18:10
 so that we can use the same styles for the signup (create account) page
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@amCap1712 amCap1712 changed the base branch from master to new-oauth May 17, 2023 15:05
@github-actions
Copy link

Unit Test Results

  1 files    1 suites   22s ⏱️
67 tests 67 ✔️ 0 💤 0 ❌

Results for commit 34af6be.


<div class="auth-card">
<h1 class="page-title text-center">{{ _('Create your account') }}</h1>
<div class="h4 text-center">access all MetaBrainz projects</div>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<div class="h4 text-center">access all MetaBrainz projects</div>
<div class="h4 text-center">to access all MetaBrainz projects</div>

?

Comment on lines 102 to 110
<p>Note that any contributions you make to MusicBrainz will be released into the Public Domain and/or licensed under a Creative Commons by-nc-sa license.
Furthermore, you give the MetaBrainz Foundation the right to license this data for commercial use.
<br/>Please read our <a>license page</a> for more details.
<p>MusicBrainz believes strongly in the privacy of its users. Any personal information you choose to provide will not be sold or shared with anyone else.
<br/>Please read our <a>privacy policy</a> for more details.</p>
<p>You may remove your personal information from our services anytime by deleting your account.
<br/>Please read our <a>GDPR compliance statement</a> for more details.</p>
<p>Creating an account on MetaBrainz will give you access to accounts on our other services, such as ListenBrainz, MusicBrainz, BookBrainz, and more.
<br/>We do not automatically create accounts for these services when you create a MetaBrainz account, but you will only be a few clicks away doing so.</p>
Copy link
Member

Choose a reason for hiding this comment

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

Is this text meant to be the actual one? It seems weird to have so much MB-specific data (what is the licensing for BB for example?) when we later say we won't anyway automatically create an MB account. We should probably have either a tiny bit on the licenses for each project, or just say we don't auto-create the sub-accounts and you can see each project's licensing stuff when creating those.

Comment on lines 111 to 113
<button class="btn btn-primary center-block" type="button" data-dismiss="modal">
Sounds good
</button>
Copy link
Member

Choose a reason for hiding this comment

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

Why have a separate button for this? If we do, shouldn't we have a second button for "I don't like this, get me out of here"? :D But honestly just "hide" seems better to me than "sounds good", in theory.

@amCap1712 amCap1712 changed the base branch from new-oauth to master December 5, 2024 05:57
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.

3 participants