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

CLDR-16499 require a CLA for contributions #3653

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

srl295
Copy link
Member

@srl295 srl295 commented Apr 23, 2024

CLDR-16499

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

- new claSigned bit must be true to allow writing
- store CLAs as JSON blobs in user prefs
- API to read/update/revoke CLA
- static list of signatory orgs
- new menu item for CLA

Other improvements/
- store JSON in the user settings data
- load .md file via webpack
- display markdown using marked (same as the error/wikimedia abstracts)
- fix the client so that it doesn't hit the OpenAPI spec multiple times
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@srl295
Copy link
Member Author

srl295 commented Apr 26, 2024

@btangmu I'll fix this so that the unit tests don't need to sign a CLA !

I'm just wondering if for local testing we want a switch that auto-signs the CLA? But then again, if you create a vetter in a signing org such as Apple Google Microsoft then it won't ask for a CLA.

@srl295 srl295 self-assigned this Apr 26, 2024
@srl295 srl295 requested a review from btangmu April 26, 2024 15:31
@srl295
Copy link
Member Author

srl295 commented Apr 26, 2024

@btangmu i think this could get any feedback from you if you want to provide it, knowing we still need to review the text and the overall process. But let me know if you see any structural issues.

Copy link
Member

@btangmu btangmu left a comment

Choose a reason for hiding this comment

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

remove the commented-out code change for MainMenu.vue?

I made a couple other nit-picky comments (which I don't insist on), otherwise, it all looks great

@@ -8,6 +8,7 @@
<li>
<ul>
<li><a href="#account///">Account Settings</a></li>
<!-- <li><a href="#cla///">Sign CLA</a></li> -->
Copy link
Member

Choose a reason for hiding this comment

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

what's this? better not to add commented-out code?

<script setup>
import * as cldrStatus from "../esm/cldrStatus.mjs";
import * as cldrClient from "../esm/cldrClient.mjs";
import * as cldrNotify from "../esm/cldrNotify.mjs";
Copy link
Member

Choose a reason for hiding this comment

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

these imports should be alphabetized, better than random order

display: "flex",
};

async function loadData() {
Copy link
Member

Choose a reason for hiding this comment

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

for separation of concerns, my preference is that Vue components shouldn't include client/server code

I realize you may not agree with that, and I don't know if I could persuade you, so I won't insist on it :-)

Copy link
Member Author

Choose a reason for hiding this comment

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

This is a draft PR for the purpose of a UX / legal review. I appreciate the comments and will do them to refactor before merge. I do plan to merge with everything switched off so we can un mothball it later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants