open source contributor incentive initiative

0xstride commented 9 months ago

🔍 Search Terms

incentive, reward

✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Description

The purpose of this suggestion is to create a reward/incentive for developers who contribute to the tslib project.

This is achieved by registering the project with the tea protocol, a newly created initiative to offer incentives to developers of registered open source projects.

This would require the creation a registration file named tea.yaml and stored in the root project directory. The registration file enables the project to start earning incentives for future contributors.

# tea.yaml
# https://tea.xyz/what-is-this-file
---
version: 1.0.0
codeOwners:
  - '0x2F9CbfcE3197F881D2b6F8abF46cdbeB6eFf88A3'
quorum: 1

Additional context

The tea protocol distributes intrinsic incentives to opensource projects, based on the value they bring to the open source ecosystem. It also distributes donated incentives to a project and its downstream components, so those downstream components get appropriate recognition for the value they contribute.

Early adopters to the tea protocol earn greater incentive rewards, as rewards only start accruing from the point the project is registered. The full background to the tea initiative is explained here https://tea.xyz/what-is-this-file

The tea protocol scans github for the tea.yaml file, as a basis to start accruing incentives

I am a tea protocol community member tasked to find and propose high value projects to receive incentives. I do not receive the incentives that stream to this project, these are earned by the project and its contributors.

I do receive a 1 off recognition for finding and registering worthy projects. This project was one of my 1st thoughts to propose, as it is a common dependency in project I've developed

📃 Motivating Example

Motivation

Over the past 80 years, open-source software has shifted from a niche hobby to the foundation of all innovation. However, these developers often receive limited tangible rewards for their significant contributions.

For example, Max Howell created Homebrew (“Brew”) in 2009 – one of the fastest growing and most used open-source projects of all time. Brew achieved similar scale and reach as other notable open-source projects such as Java, Python and Linux. Despite the success and widespread adoption of Homebrew, Max could only afford to maintain the OS project as a “hobby” while working as a developer to pay the bills. Max’s story is common amongst OS developers.

Why is this a problem worth solving? Why Now?

To safeguard the sustainability and ongoing expansion of the open-source software ecosystem, it is crucial to recognize and reward the contributions of open-source developers.

Solution

tea’s decentralized protocol aims to improve the sustainability and integrity of open-source software. It allows developers to benefit from their work in a trustless way, thanks to an impact metric, reputation and incentives. It provides rewards for open-source work via an independent and autonomous system for recognizing impact and a way for community members to share their discoveries and constructive opinions on a project or a developer's work.

💻 Use Cases

What do you want to use this for? Motivating and recognising opensource contributions
What shortcomings exist with current approaches? Opensource development lacks the correct incentive mechanisms
What workarounds are you using in the meantime? n/a

MartinJohns commented 9 months ago

Oh, look, another one.

Alt-account of this one maybe: #57476. I can see this spammed in numerous repos already.

RyanCavanaugh commented 9 months ago

No thanks

microsoft / TypeScript