DevPool by Ubiquity

[0x4007]

Project Abstract

DevPool is a crypto-native platform that organically sits on top of GitHub to optimally match developers with open tasks and get paid in crypto while automating management for distributed organizations and repository maintainers.

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 BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) 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: @_______:matrix.org (change the homeserver if you use a different one)

[CLAassistant]

All committers have signed the CLA.

[keeganquigley]

Thanks for the application @pavlovcik a couple of initial comments/questions:

• Regarding the milestones, the mandatory deliverables look good (0a. - 0d.) but delivery table descriptions 1 - 6 seem to still be the template boilerplate text. Can you replace this with the concrete technical deliverables that you would produce?
• We only fund software that doesn't exist yet, and it seems that some of the DevPool tools have already been built, such as ubiquibot. Can you specify in the application what you would be building as part of the grant? The more technical details the better.
• For any front-end focused milestones, we typically ask for mockups to be presented in the application.
• Please also note that we typically only fund ink! smart contracts, as we aren't Solidity experts.

[github-actions]

Thank you for submitting a grant application.

We've assessed your submission and have found that it requires a higher level of technical detail in order to be considered for review. We encourage you to expand on it by providing a more precise specification/technical details. The section on project details in the application template is a good reference as to what type of information we expect applicants to provide, and these category-specific requirements contain more precise guidelines depending on what type of software you're building.

An area of the application that we often find to be insufficiently elaborated are the milestone deliverables. At a minimum, please indicate what languages/technologies you will be using to implement each deliverable, and provide a technical summary of its expected functionality. Note that deliverables should be tangible, reusable by other teams and in most cases not already present in the ecosystem. If they are, you will need to provide a comparison to existing implementations and explain why it makes sense to fund your approach. Also see our FAQ for a breakdown of what we fund and what we don't.

Let us know as soon as you're done with your changes, and we'll give your application another look!

[0x4007]

I understand that these submissions are expected to be delivered in a single commit. It makes more sense to me that we append changes to this same pull request, possibly after converting it to a draft pull request, and to keep the context of the conversation.

Otherwise, please confirm if you want me to close this pull request, and open another when we complete our changes.

[keeganquigley]

Thanks @pavlovcik yep no worries, you can make the changes on the current PR, no need to open a new one. We will squash the commits anyway.

[Noc2]

I wanted to let you know that I'm closing this because of inactivity. Let me know if I should reopen it.