gitcoinbot
commented
2 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 1 week, 4 days from now. Please review their action plans below:
1) prashanth004 has applied to start work _(Funders only: approve worker | reject worker)_.
I like the idea. I always wanted to build my own read-later extension. I have a lot of experience in building chrome extensions and also working with the smart contract and the graph.
I have built V0 of Gosats extension ( like Loli ). Few extensions like explain, collekt and others.
A description about my technical profile https://www.notion.so/Profile-5b1e574c6dd347aab5947e2702afea8c 2) boyin0x has been approved to start work.
Hi, I have experience in developing Chrome Extensions, it will be great to make it using the FDP Storage JS library. I'll make it within 3 weeks after approval, as you required. 3) tms1337 has applied to start work _(Funders only: approve worker | reject worker)_.
Who will work on a project
We are a team and a consulting company consisting of people with 5+ years working in the crypto industry.
We are all full-stack and smart contract developers (at least the core team). We can of course extend team and add additional frontend and backend people as needed, since we have a good personal network of developers.
We also have a lot of both developer and business experience. We usually do consulting, specifically in the domains of crypto, software architecture, and financial risk management. But we also like to build our products or do the outsourcing of the fun ones.
As a side-note we also are in the field of education where we make bootcamps and courses for coding (including smart contracts).
Steps
Here are the steps that we plan to undertake (in chronological order):
- make the prototype that does dummy actions and tests the OS specific APIs that need to be used
- do the design and analysis, output of which are end-to-end tests and mocks that are used as documentation and communcation tool
- plan the architecture, setup the collaboration tools and workflow
- implement end-to-end tests (fail first), so that we know we are done when all the tests are passing
- make website with dummy connectors
- write connectors library/SDK
- connect website to real connectors
- do additional manual testing
- (if possible based on architecture) try to prove some properties of the system
Learn more on the Gitcoin Issue Details page.
boyin0x
crtahlin
Motivation / background / user story:
Humans can be nostalgic beings and as such, sometimes a person would like to reflect upon web pages from days past. Additionally and more importantly censorship plays a large part in the internet and ultimately we want to empower users to have access to snapshots of web pages that can be saved in their personal data store. In Web2 this tool comes in the form of products like Wayback Machine but in Web3 we're missing a similar tool.
As a User, I would like to access snapshots of some webpages saved with all it's contents in my personal store, so that I can always access webpages I find valuable.
Tasks
Approving criteria
Timeline
This bounty is estimated to take no longer than 40 hours.
Deadline: 3 calendar weeks after approval.
Compensation: In BZZ tokens in amount of 1500 DAI at the date of payment (as of the price of BZZ / DAI on the day of the payout as determined by Fair Data Society).
Bounty process
One team will be selected and approved to work on the project. Upon completion, the bounty will be awarded to the chosen team, if the approving criteria is met. If the approving criteria is not met, another team will be selected and approved. Consequentially the deadline will be extended. If no project matches all the approving criteria, no bounty will be awarded.
References Use the Fair Data Society Discord for more information and support.
Mind the Fair Data Society Principles in your tasks.