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

Treasury Tracker - Level 2 Request #2063

Closed
wants to merge 4 commits into from
Closed

Treasury Tracker - Level 2 Request #2063

wants to merge 4 commits into from

Conversation

senseless
Copy link
Contributor

Project Abstract

Stake Plus Inc is developing TreasuryTracker, a platform aimed at enhancing transparency and engagement in the Polkadot and Kusama ecosystems by offering in-depth analytics on treasury funding and governance. Built on NodeJS, CakePHP, and MySQL/MariaDB, the project focuses on data visualization, comprehensive analytics, and real-time chain statuses. The team seeks a Level 2 Web3 Foundation grant to transition from a proof of concept to a fully-realized, market-ready product.

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) or BTC address in the application).
  • 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: @stakeplus:matrix.org (change the homeserver if you use a different one)

@github-actions
Copy link
Contributor

github-actions bot commented Oct 20, 2023

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@senseless
Copy link
Contributor Author

I have read and hereby sign the Contributor License Agreement.

@keeganquigley keeganquigley self-assigned this Oct 24, 2023
Copy link
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

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

Thanks for the application @senseless have you looked into going for treasury funding for this? In my opinion the treasury should be funding its budgeting tools. But based on your previous work I wouldn't be opposed to funding milestone 1 to help bootstrap the project, but milestone 2 seems like mostly maintenance work that could be funded by the community/users. Would you consider reducing the scope?

@senseless
Copy link
Contributor Author

Thanks for the application @senseless have you looked into going for treasury funding for this? In my opinion the treasury should be funding its budgeting tools. But based on your previous work I wouldn't be opposed to funding milestone 1 to help bootstrap the project, but milestone 2 seems like mostly maintenance work that could be funded by the community/users. Would you consider reducing the scope?

I would be ok with that. The governance 1 part and importing the historical data (as well as supporting all paras still operating gov1) is a big thing that I'd like to have done prior to going to treasury. I'm a bit concerned by Ivy due to comments left on the recent OpenSquare proposal. Ivy seems to be picking winners. But if we put in some effort on revamping design prior and putting in a lower ask, we may be able to find support in treasury.

@keeganquigley
Copy link
Contributor

Thanks @senseless for your response, and yes I know there are currently some issues with trying to get funds from the treasury so that's also why I'm willing to support a reduced scope. Sounds good, feel free to ping me once changes are made and I will have another look.

@senseless
Copy link
Contributor Author

Thanks @senseless for your response, and yes I know there are currently some issues with trying to get funds from the treasury so that's also why I'm willing to support a reduced scope. Sounds good, feel free to ping me once changes are made and I will have another look.

I have removed the second milestone and left the first milestone in-tact.

Copy link
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

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

Thanks @senseless looks good except for it looks like the Overview section is missing above the milestone. Could you add it in per this example? Thanks!

@senseless
Copy link
Contributor Author

Thanks @senseless looks good except for it looks like the Overview section is missing above the milestone. Could you add it in per this example? Thanks!

I have added an Overview section under the Milestones section

Copy link
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

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

Thanks for the changes @senseless you can always apply for a follow-up grant for M2 in the future if treasury funding doesn't work out. Happy to go forward with it, and I will mark it as ready for review so the rest of the committee can take a look.

@keeganquigley keeganquigley added the ready for review The project is ready to be reviewed by the committee members. label Oct 25, 2023
@senseless
Copy link
Contributor Author

Thanks for the changes @senseless you can always apply for a follow-up grant for M2 in the future if treasury funding doesn't work out. Happy to go forward with it, and I will mark it as ready for review so the rest of the committee can take a look.

It appears as if this application is marked for 5 approvals instead of the normal 3 for level 2. Is that intended? Thanks

@keeganquigley
Copy link
Contributor

Thanks @senseless yes that's normal, it will be manually merged after 3 approvals.

@Noc2 Noc2 added the discussion private Discussion of application happens in private. label Oct 26, 2023
@github-actions
Copy link
Contributor

The applicant has requested the discussion of the application to happen in a private chat room.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

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

I added a comment in the private channel.

@senseless
Copy link
Contributor Author

Closing this PR for now. We will proceed to a Treasury request and see how things go.

Thanks!

@senseless senseless closed this Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion private Discussion of application happens in private. ready for review The project is ready to be reviewed by the committee members.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants