Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
As a Gitcoin contributor, I want better and updated data fixtures, so that QAing my changes and getting started is easier.
### Why Is this Needed
There are currently some fixtures which help bootstrap the process of creating test data when running Gitcoin locally. These fixtures are automatically added when you run Gitcoin via docker, and include things like creating users and adding tokens. Adding fixtures to include newer features like Grants, and updating the current fixtures will make developers' lives easier.
More info: https://docs.djangoproject.com/en/2.2/howto/initial-data/
### Current Behavior
Booting the Gitcoin app via docker for the first time adds some initial data.
### Expected Behavior
Booting the Gitcoin app via docker should add more data to cover the new features that have been integrated into the app.
### Definition of Done
Additional fixtures are present when booting the app for the first time. Every feature in the app contains a variety of data on a fresh build, including Bounties. For each feature, there should be different model instances that demonstrate the variations of models we see in the production app. For example: in Grants, there should be grants that are set to various funding levels, which grant contributions already in place from various test users. For Bounties, there should be a combination of both public and private bounties, a demonstration Hackathon event set up, etc. For users, there should be a variety of test users already set up that have initiated various activities, such as applying to work on bounties, setting up their profile, sending Kudos, etc. These are just examples and are in no way comprehensive. All test data should be on the Rinkeby testnet if applicable.
### Data Requirements
The success of the new fixture data can be measured in how many more community contributions we receive, as well as decreasing the amount of bugs in PRs and deploy regressions.