ivabus/www
1
0
Fork 0
mirror of https://github.com/ivabus/www synced 2024-11-22 13:25:06 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

CHAI copy update

Browse source
This commit is contained in:
Thomas Smith 2023-03-28 17:29:41 -04:00
parent d55dddaca9
commit b21e8e37f0
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/layouts/index.html
View file

@ -771,8 +771,8 @@
</div> </div>
<div class="col-xl-8 col-lg-8 col-md-12 col-sm-12 col-12"> <div class="col-xl-8 col-lg-8 col-md-12 col-sm-12 col-12">
<h2 class="display-6 white chai-header">And we can't fix OSS with just any tea&hellip; we need some <span style="color:#ff8e00;">CHAI</span></h2> <h2 class="display-6 white chai-header">And we can't fix OSS with just any tea&hellip; we need some <span style="color:#ff8e00;">CHAI</span></h2>
<p>The open source package registry can be thought of a directed graph, with each package version representing a node and dependency relationships as edges. An on-chain graph could align incentives between open source maintainers and users for different projects. It can evaluate the impact of these projects based on their dependencies, and even proportionately reward them. It is difficult to design & implement such a network -- one that knows about every open source package & their depedencies -- but we believe the aligned incentives will yield much better outcomes for our open source maintainers.</p> <p>The open source package registry can be thought of as a directed graph, with each package version representing node and dependency relationships as edges. An on-chain graph could align incentives between open source maintainers and users across different projects. It can evaluate the impact of these projects based on their dependencies, and even proportionately reward them. It is difficult to design & implement such a network -- one that knows about every open source package & their dependencies -- but we believe the aligned incentives will yield much better outcomes for our open source maintainers.
<p class="mb-4">Chai_v1 is the system that collects all the nodes & edges across all package managers, and verifies the maintainers for each one. It will be prepopulated with packages from <code class="chai-code p-1">tea</code> (300 & counting), <code class="chai-code p-1">brew</code> (6k), <code class="chai-code p-1">crates</code> (104k), <code class="chai-code p-1">PyPI</code> (300k), and <code class="chai-code p-1">npm</code> (1.6M) as nodes, and all their relationships, and pagerank scores available. It will eventually enable users to formalize their project maintainer status with an additional commit message to the main branch of their repo.</p> <p>Chai_v1 is the system that collects all the nodes & edges across all package managers, and verifies the maintainers for each one. It will be pre-populated with packages from tea (300 & counting), brew (6k), crates (104k), PyPI (300k), and npm (1.6M) as nodes, and all their dependencies as edges to ascertain the impact of each one to open source. It will eventually enable users to formalize their project maintainer status with an additional commit message to the main branch of their repo.</p>
<a href="https://github.com/teaxyz/chai/tree/95c3b927556b8c51f72b922fe2e0222f5551fba4"> <a href="https://github.com/teaxyz/chai/tree/95c3b927556b8c51f72b922fe2e0222f5551fba4">
<button class="hbtn-light hb-light-fill-right github-click-secondary" id="chai-btn">Read more about CHAI</button> <button class="hbtn-light hb-light-fill-right github-click-secondary" id="chai-btn">Read more about CHAI</button>
</a> </a>