index.html 5.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. <!doctype html>
  2. <html class="default light">
  3. <head>
  4. <meta charset="UTF-8" />
  5. <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  6. <title></title>
  7. <link rel="stylesheet" type="text/css" href="/theme.css" />
  8. </head>
  9. <body class="body">
  10. <header class="header">
  11. <h1 class="header-title">
  12. <a class="header-title__link" href="/">
  13. <img src="/logo-with-name.svg" alt="ForgeFed" title="ForgeFed" />
  14. </a>
  15. </h1>
  16. <nav class="nav">
  17. <a class="nav__link"
  18. href="/forgefed.html">🗲 behavior</a>
  19. <a class="nav__link"
  20. href="/forgefed-vocabulary.html">📓 vocabulary</a>
  21. <a class="nav__link"
  22. href="https://notabug.org/peers/forgefed/issues">🐞 issues</a>
  23. <a class="nav__link"
  24. href="https://talk.feneas.org/c/forgefed">🗪 forum</a>
  25. <a class="nav__link"
  26. href="/index/dark.html">🌑</a>
  27. </nav>
  28. </header>
  29. <main class="main">
  30. <h1 class="main-title"></h1>
  31. <p>ForgeFed is a federation protocol for enabling interoperability between version control services. It's built as an extension to the <a href="https://www.w3.org/TR/activitypub/">ActivityPub</a> protocol, allowing users of any ForgeFed-compliant service to interact with the repositories hosted on other instances.</p>
  32. <p>The goal of the project is to support all of the major activities connected to project management, including bug reports, merge requests, and notifications across instances.</p>
  33. <p>This website serves as the authoritative source for finding up to date information about the project.</p>
  34. <h1 id="why-forgefed">Why ForgeFed?</h1>
  35. <p>The current state of code collaboration is dominated by centralized, proprietary platforms. Free alternatives to these platforms exist (for example <a href="https://notabug.org">NotABug</a> and <a href="https://pagure.io">Pagure</a>) but they do not solve the problem of centralization.</p>
  36. <p>This project tries to address exactly this problem. Our wish is to devise a free and standardized mechanism for enabling collaboration across any version control platform.</p>
  37. <h1 id="project-status">Project status</h1>
  38. <p>The specification and software produced by this working group is still in the early stages, and there is still much work to do and ample design-space for discussion and contributions.</p>
  39. <p>So far the protocol supports:</p>
  40. <ul>
  41. <li>repository following</li>
  42. <li>repository push notifications to followers</li>
  43. <li>new issue creation</li>
  44. </ul>
  45. <h1 id="work-group">Work group</h1>
  46. <p>Community and development discussions are conducted on the <a href="https://talk.feneas.org/c/forgefed">ForgeFed Forum</a>, with informal, real-time collaboration often taking place on the #peers IRC channel on freenode. In order to be most widely adopted, we strive to assemble the most diverse and representative group including: users, implementers, and various domain experts. Anyone who is experienced with working on existing forges or federated &quot;social&quot; services, and anyone with experience in writing technical specification documents is encouraged to join the working group.</p>
  47. <h1 id="implementations">Implementations</h1>
  48. <ul>
  49. <li><em><a href="https://dev.angeley.es/s/fr33domlover/r/vervis">Vervis</a></em> is the reference implementation of ForgeFed. It serves as a demo platform for testing the protocol and trying new features</li>
  50. <li><em><a href="https://notabug.org/zPlus/mcfi">mcfi</a></em> is another command line implementation for testing the protocol</li>
  51. </ul>
  52. <h1 id="project-links">Project links</h1>
  53. <ul>
  54. <li><a href="https://notabug.org/peers/forgefed/issues">Issues tracker</a></li>
  55. <li><a href="https://notabug.org/peers/forgefed/wiki">Wiki</a></li>
  56. <li><a href="https://talk.feneas.org/c/forgefed">Forum</a></li>
  57. <li><a href="/forgefed-vocabulary.html">Specification</a></li>
  58. <li><a href="https://dokk.org/ForgeFed">dokk</a></li>
  59. </ul>
  60. </main>
  61. <footer class="footer">
  62. <p xmlns:dct="http://purl.org/dc/terms/">
  63. <a rel="license"
  64. href="http://creativecommons.org/publicdomain/zero/1.0/">
  65. <img src="https://licensebuttons.net/p/zero/1.0/88x31.png"
  66. style="border-style: none;"
  67. alt="CC0" />
  68. </a>
  69. <br />
  70. <a rel="dct:publisher" href="https://peers.community">
  71. <span property="dct:title">The ForgeFed team</span>
  72. </a>
  73. has dedicated all copyright and related and neighboring
  74. rights to
  75. <span property="dct:title">ForgeFed</span> to the public domain
  76. worldwide.
  77. </p>
  78. <p>❤ Copying is an act of love. Please copy, reuse and share!</p>
  79. <p>
  80. Site generated by
  81. <a class="footer__link" href="https://pandoc.org">pandoc</a>.
  82. </p>
  83. </footer>
  84. </body>
  85. </html>