Separate from the high level discovery, this is focused on prototyping out the bounty concept. The outcome should establish how it can / can't work and what a working v1 prototype could look like.
Ronald Coase, in "The Nature of the Firm" (1937), raised the question of why economic activities are sometimes organized within firms rather than conducted through the market. Today, especially in the realm of software development and beyond, we are witnessing a trend that suggests the decentralized market may be a more favorable environment for labor, both for the employer and the employee.
Moreover, the historical preference for full-time employment by firms has been driven by transaction costs such as hiring, onboarding, and acquiring system knowledge. However, this dynamic is also experiencing significant change. A trend that has persisted for decades is the inclination to hire ready-made employees, meaning that previously firms were willing to train employees for specific tasks. Nowadays, knowledge workers are often expected to be job-ready from day one without requiring additional training.
A "bounty" refers to a reward or payment offered for the completion of a specific task. This concept has a long history of use in various domains. In law enforcement, bounties have been used to apprehend wanted criminals or fugitives. Sales and finance industries offer bounties in the form of commissions for agents or brokers, as well as referral rewards. In wildlife conservation, bounties have been employed to protect livestock by incentivizing the removal of invasive species. Moreover, bounties play a significant role in modern software development, particularly in the detection of bugs and security vulnerabilities, with platforms like HackerOne leading the way.
Problem to Solve
Labor gap: many organizations and projects have tasks to be completed and funding available (if not could be Crowdfunded); they lack the required labor to carry out these tasks effectively. This labor gap may be due to resource constraints, or a shortage of skilled workers in their jurisdiction.
Full time work inefficient: in cases where orgs have less funding available, hiring full time is not an option and too costly. A theme in more recent times is the opposite of Coase observation, there is a flippening where cost for full time trending higher than cost for freelance model.
Variability in compensation: different organizations may offer varying compensation for the same tasks or projects. This variability in pay creates a disparity in the traditional marketplace and can impact the availability and willingness of talent to participate. However, in a more free and/or global marketplace, these varying compensations can let the markets competition open up better options for both parties (contractor and org).
Flexible work arrangements / trends: The marketplace includes participants willing to work in different ways, such as full-time freelancers, part-time contractors, or project-based contributors. This diversity in work arrangements adds complexity to the process of connecting talent with suitable opportunities in the current ecosystem.
Solution ideation
Login to Repo Provider (Infuse bounty capability in common/existing workflow)
This provider's client with org/repo/issues data (GitHub/GitLab). With this, the developer can assign bounties in familiar workflow.
While this centers around leveraging repo providers and related workflows, the strategy of infusing into common workflows extends beyond this context. Such as: Facebook (groups), Basecamp (projects), Atlassian, and social media communities, that offer opportunities for a similar integration; enabled by OAuth and/or API. Also, having the structure of org/project/issue without being connected to another platform allows a space for someone to organize and crowdfund as they see fit in that framework. Focusing on developer communities is prioritized as it feels like they are widely the early adopters for these protocols/workflows.
Repo Provider Permissions
Who should be able to create a bounty?
Repo maintainer and owners by default (members if granted permission?) + wallet connection (?)
This layer of verification helps mitigate investor and/or bounty applicant concerns
However, there is a use case for outside collaborators. In this scenario, an outside collaborator could request a bounty or express interest in one. While this is an interesting workflow, it's probably not of interest this early, but worth noting.
Who should be able to apply for a bounty?
Verified/authorized user per repo provider + wallet connection (?)
Handling Private Repositories Posting Bounties
Preliminary, based on API capabilities, it appears that the authorized 3rd-party client can show this data (if granted permission by maintainer or owner). The interaction here would need to be "published as public" to the marketplace. OR instead of granting issue permission to display, the issue could be created directly on Line. Then if the application is accepted, the user could be invited as an outside collaborator.
Bounty Creation
Verified maintainer/owner of the repo may assign a bounty to 1) an existing issue, or 2) a new issue, or 3) an issue unrelated to the repo provider (?). Here is what's needed to be created:
Verified user + wallet
Bounty amount (secured in contract)
Bounty description (linked to GH issue)
Experience and skills required
Timeline expectations for work
How long to post the bounty
Once the bounty is created, it's posted to the marketplace
The creator of the bounty can both edit and delete the bounty (?)
Visibility
Update issue with bounty creation
Seen as a comment which can update (edit) or post new once completed
Open bounty label
Repo badge update links to bounties count / anchor to the marketplace
Line page active for distribution
Application Process
Once the bounty is created, it's posted to the marketplace
The creator of the bounty can both edit and delete the bounty (?)
Update issue with bounty creation
Seen as a comment which can update (edit) or post new once completed
Open bounty tag
Repo badge update links to bounties related to
Line page active for distribution
Bounty in Marketplace
Where do potential candidates view the bounties?
In the marketplace page / or linked in the issue itself / or distribution channels
What is required of an applicant to be able to apply?
Verified user by repo provider + wallet connection (?)
What is needed for an applicant to apply?
Application consent
Description outlining qualifications + experience
Ability to add a note to bounty creator
Links to related websites or work
Any questions
Application submitted
Updates both repo issue (only updates comment) and Line issue (separate section or in feed or both?)
Applications visible to all on issue
If timeline is applied and now applicants selected, the bounty is closed
How does the bounty creator and applicant mutually agree to move forward?
The bounty creator makes a selection indicating they'd like to move forward
The applicant is open to agree (within X days)
Once mutual parties agree, the contract is initiated
Bounty In-Progress to Completion
How is completion of the bounty contract complete?
Both parties must mutually consent to completion. If both parties do not consent to contract conclusion, the work is withheld, and the financial transaction is locked. There is a scenario here in the development workflow that has asymmetric downside for the applicant; for example, the applicant submitted what they believe is a suitable PR and it was merged, but the bounty creator does not mutually agree to work. In this case, the review process should and will reflect this and, therefore, penalizes the bounty creator (more on this in dispute resolution + rating).
Dispute Resolution
In cases where there is a dispute, both parties must agree to a resolution, which would be an addendum. Example: to end the bounty and pay 30% of the initial bounty; both parties agree, and it closes the contract.
Bounty Completed, Post Mortem and Mutual Party Review
Separate or at the same time of mutual consent, each party submits a rating on the other.
review notes
Feedback from Jonny via 📽️ [video](https://www.loom.com/share/9b00ad97a46a47e591a3e6eb7b476532):
**Bounty walkthrough**
- missing the minting NFT piece
- @kylemann ToDo
- what is the ask though?
- we are working on other things, but interested in bounties
- but let's put it in the Fabric design framework
- @kylemann ToDo (@jnymck could invite to Figma design system)
**Crowdfunding**
- Feeling a bit unsure around this, specifically the crowdfunding of issue
- Brainstorming the crowdfund vs bounty concept
- is the crowdfund (for org) the stick and the bounty the (carrot)
- from the developer point of view, they could crowdfund an issue, is that part of the thinking? (k: yes)
- if yes, the criticism is it's less of a crowdfund and more a bid `ask`
- k: 💯 didn't think about it in those terms, but yes, that's right and more clear
- k: the part missing is the org / repo level crowdfunding opportunity
Briefing
Separate from the high level discovery, this is focused on prototyping out the bounty concept. The outcome should establish how it can / can't work and what a working v1 prototype could look like.
Ronald Coase, in "The Nature of the Firm" (1937), raised the question of why economic activities are sometimes organized within firms rather than conducted through the market. Today, especially in the realm of software development and beyond, we are witnessing a trend that suggests the decentralized market may be a more favorable environment for labor, both for the employer and the employee.
Moreover, the historical preference for full-time employment by firms has been driven by transaction costs such as hiring, onboarding, and acquiring system knowledge. However, this dynamic is also experiencing significant change. A trend that has persisted for decades is the inclination to hire ready-made employees, meaning that previously firms were willing to train employees for specific tasks. Nowadays, knowledge workers are often expected to be job-ready from day one without requiring additional training.
A "bounty" refers to a reward or payment offered for the completion of a specific task. This concept has a long history of use in various domains. In law enforcement, bounties have been used to apprehend wanted criminals or fugitives. Sales and finance industries offer bounties in the form of commissions for agents or brokers, as well as referral rewards. In wildlife conservation, bounties have been employed to protect livestock by incentivizing the removal of invasive species. Moreover, bounties play a significant role in modern software development, particularly in the detection of bugs and security vulnerabilities, with platforms like HackerOne leading the way.
Problem to Solve
Solution ideation
Login to Repo Provider (Infuse bounty capability in common/existing workflow)
Repo Provider Permissions
Handling Private Repositories Posting Bounties
Bounty Creation
Application Process
Bounty in Marketplace
Bounty In-Progress to Completion
Dispute Resolution
Bounty Completed, Post Mortem and Mutual Party Review
🎥 view video walkthrough
review notes
Feedback from Jonny via 📽️ [video](https://www.loom.com/share/9b00ad97a46a47e591a3e6eb7b476532): **Bounty walkthrough** - missing the minting NFT piece - @kylemann ToDo - what is the ask though? - we are working on other things, but interested in bounties - but let's put it in the Fabric design framework - @kylemann ToDo (@jnymck could invite to Figma design system) **Crowdfunding** - Feeling a bit unsure around this, specifically the crowdfunding of issue - Brainstorming the crowdfund vs bounty concept - is the crowdfund (for org) the stick and the bounty the (carrot) - from the developer point of view, they could crowdfund an issue, is that part of the thinking? (k: yes) - if yes, the criticism is it's less of a crowdfund and more a bid `ask` - k: 💯 didn't think about it in those terms, but yes, that's right and more clear - k: the part missing is the org / repo level crowdfunding opportunity