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

amendment: Split milestone 2 into 2 parts #2179

Closed
wants to merge 18 commits into from
Closed

amendment: Split milestone 2 into 2 parts #2179

wants to merge 18 commits into from

Conversation

katerinabc
Copy link
Contributor

Project Abstract

Previous pull request: #1482
Milestone 2 discussion: w3f/Grant-Milestone-Delivery#1047 (comment)

Brief description
Building a strong community requires metrics that measure the quality and stickiness of a community, and not just vanity metrics. We use behavioral and network science to create a community health dashboard for members and moderators to understand and get a bird's eye view of the health of their community.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • Payment details have been provided (bank details via email or Polkadot (USDC & USDT) address in the application).
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Copy link
Contributor

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment:


I have read and hereby sign the Contributor License Agreement.


You can retrigger this bot by commenting recheck in this Pull Request

@katerinabc
Copy link
Contributor Author

  1. I've signed the CLA with the original project submission. I'm requesting a change to milestone 2. Should I sign it again?
  2. Can you explain why 5 reviewers are requested?

@semuelle semuelle self-assigned this Jan 17, 2024
Copy link
Member

@semuelle semuelle left a comment

Choose a reason for hiding this comment

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

Hi @katerinabc. Unfortunately, Github doesn't allow conditional approval rules, so 5 approvals is the default as it's the maximum we need. Once you have three approvals, we merge it manually.

Regarding the CLA: it's possible that @takahser is the one who needs to sign it, as he appears as commit author.

But could you submit a PR from a more recent fork? You are trying to add the whole document again, which is already in our repo. It also makes it hard to see what has been changed.

@keeganquigley keeganquigley added amendment This PR proposes changes to an existing application. changes requested The team needs to clarify a few things first. labels Jan 19, 2024
Copy link
Collaborator

@takahser takahser left a comment

Choose a reason for hiding this comment

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

@katerinabc could you resolve the merge conflicts?

image

Or submit a fresh PR from a more recent fork, as @semuelle suggested.

@katerinabc
Copy link
Contributor Author

Ok, gonna close this pull request and submit the amendment using a more recent fork

@katerinabc katerinabc closed this Jan 29, 2024
@keeganquigley
Copy link
Contributor

Conversation has moved here: #2195

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amendment This PR proposes changes to an existing application. changes requested The team needs to clarify a few things first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants