Explore Incentivization and Aging of work

[rceleste125]

Steering: Proposal Summary

Used to propose a change or addition to Steering. This is for the Steering work START approval step. Discuss the proposed work or change. #

Steering: Publication Summary

Used to present completed work to Steering for approval to publish. Discuss the work that was completed in reference to the above proposal. Include any differences from the proposal and why. use [GitHub Preview](https://htmlpreview.github.io/) to show final state of documents along with pull requests (if needed). #

---

Detailed Description:

This Issue seeks to address the backlog of work.

1. Incentivization: Some Open-Source projects assign some sort of incentive for contributors to take on a backlogged item, resolve it and provide documentation (presentation) back to the project. The incentive could be a "Bounty" of real value or an award of contribution. 2. Issue Aging: Should we revert Issues that have sat in the Backlog back to the Author after a period of time for reconsideration? We do now have an Aging report.

---

Triage:

• [x] Is Issue appropriate for OCI Architecture
• [x] Assign Size
• [x] Assign Priority
• [x] Assign Label (include Type of change and Steering "Review" or "FYI")
• [x] OCI affected Artifacts Identified
• [ ] Assign Triage - Artifact Version Target (v x.x.x Milestone)
• [ ] Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
• [ ] Create sub-project (if needed)

Affected Parties (help determine Sunrise/Sunset):

• [ ] Trading Partners
• [ ] Issuers
• [ ] Wallet Solutions
• [ ] PI Verification Solutions

Affected OCI Artifact

• [ ] Schema Document
• [ ] Identity Schema
• [ ] ATP Schema
• [ ] Issuer Conformance Criteria
• [ ] Wallet Conformance Criteria
• [ ] VRS Solution Conformance Criteria
• [ ] Wallet API Specification
• [x] Governance Document
• [ ] Conformance Program
• [ ] OCI Website
• [ ] Internal Process

Change Category (Guides Steering Review)

- Steering/Industry Review

Needs Steering Consensus

• [ ] Business-Level (May affect business operations)
• [x] OCI Governance, Policy or website feature

- Steering/Industry Notification

Does not need Steering Consensus (Steering may require a Consensus decision or futher clarification prior to issue being resolved by P&A

• [ ] Technical-Level (Does not affect business operations)
• [ ] OCI Internal Process or Infrastructure

Communication

• [x] Website
• [x] Newsletter
• [ ] email
• [ ] None
• [ ] Other:

[rceleste125]

How do open-source projects incentivize work on the project

Open-source projects incentivize contributions from individuals in various ways, even though these incentives might not always be monetary. The open-source ethos is built on collaboration, passion, and a desire to create valuable software for the community. Here are some common ways open-source projects incentivize work:

1. Recognition and Reputation: Open-source contributors often value recognition within the community. Their work is visible to others, and they can build a strong reputation as skilled developers, which can lead to job opportunities, speaking engagements, and other professional benefits.

2. Skill Development: Contributing to open-source projects allows developers to hone their skills by working on real-world projects, collaborating with experienced developers, and gaining insights into various technologies and methodologies.

3. Personal Satisfaction: Many contributors find personal satisfaction in solving problems, helping others, and making a positive impact on a project that they care about.

4. Resume Building: Open-source contributions are a great addition to a developer's resume, showcasing practical experience, collaboration skills, and a commitment to community-driven projects.

5. Networking: Participating in open-source communities provides opportunities to connect with like-minded developers, potential mentors, and industry professionals.

6. Learning Opportunities: Open-source projects often involve diverse challenges and technologies. Contributors can learn new programming languages, frameworks, and best practices while working on these projects.

7. Contributor Guidelines and Documentation: Clear contributor guidelines and well-maintained documentation make it easier for newcomers to understand the project, its goals, and how they can contribute. Projects that facilitate the onboarding process tend to attract and retain more contributors.

8. Hackathons and Contests: Some open-source projects organize hackathons, coding contests, or other events where participants can win prizes, swag, or recognition for their contributions.

9. Mentorship Programs: Mentorship programs within open-source communities can help new contributors navigate the project, receive guidance, and become more comfortable with the contribution process.

10. Bug Bounties: Some projects offer bug bounty programs where contributors are rewarded for finding and fixing security vulnerabilities or other critical issues.

11. Sponsorship and Grants: While not as common, some open-source projects receive funding from companies, organizations, or grants. This funding might be used to support core contributors, organize events, or improve the project infrastructure.

12. Community Bonding: Building a strong, inclusive, and supportive community can itself be a strong incentive. The sense of belonging and camaraderie motivates contributors to keep participating.

13. Impact on Personal Projects: Contributors might work on open-source projects that align with their personal interests or projects, leading to improvements and enhancements in their own work.

14. Long-Term Vision: Some contributors are drawn to the long-term vision of a project, where they can contribute to something that will have a lasting impact on a particular technology, field, or community.

In summary, open-source projects incentivize work through a combination of personal, professional, and community-oriented rewards. It's the combination of these factors that fosters a vibrant ecosystem of collaboration and innovation within the open-source community.