Mirror of https://codeberg.org/ForgeFed/ForgeFed

Pere Lev 2c47d6bf68 Blog: Add post about team nesting (#221) 6 days ago
content 2c47d6bf68 Blog: Add post about team nesting (#221) 6 days ago
doc d342d19db9 Update doc README (#154) 1 year ago
static 079a123526 Build website pages & blog using Zola (#191) 1 year ago
templates aede6b8efd Update chat navigation link (#219) 6 days ago
.gitignore 079a123526 Build website pages & blog using Zola (#191) 1 year ago
.woodpecker.yml 0e45d12d12 Rewrite .woodpecker.yml to use Alpine and pipx (#206) 8 months ago
LICENSE 467dfe8467 Fix #173: Move redundant README content to website index.md (#187) 1 year ago
README.md c5475d2537 Mention NLNet funding in the README (#215) 1 month ago
build.sh 0e45d12d12 Rewrite .woodpecker.yml to use Alpine and pipx (#206) 8 months ago
config.toml 8961aa7789 Generate Atom feed and replace "pandoc" with "Zola" in the footer (#193) 1 year ago
context.jsonld 079a123526 Build website pages & blog using Zola (#191) 1 year ago
deploy.sh 079a123526 Build website pages & blog using Zola (#191) 1 year ago
resources.md 76ddd3201e Update 'resources.md' 1 year ago
spec.bs 7f2266532f Spec: Add sections about adding & removing team/project members (#214) 3 weeks ago

README.md

ForgeFed

<img alt="Get it on Codeberg" src="https://codeberg.org/Codeberg/GetItOnCodeberg/media/branch/main/get-it-on-neon-blue.png" height="60">

ForgeFed is an ActivityPub-based federation protocol for software forges. You can read more about ForgeFed and the protocol specification on our website.

Contributing

There's a huge variety of tasks to do! Come talk with us on the forum or chat. More eyes going over the spec are always welcome! And feel free to open an issue if you notice missing details or unclear text or have improvement suggestions or requests.

However, to maintain a manageable working environment, we do reserve the issue tracker for practical, actionable work items. If you want to talk first to achieve more clarity, we prefer you write to us on the forum or chat, and opening an issue may come later.

If you wish to join the work on the ForgeFed specification, here are some technical but important details:

  • We don't push commits to the main branch, we always open a pull request
  • Pull requests making changes to the specification content must have at least 2 reviews and then they wait for a cooldown period of 2 weeks during which more people can provide feedback, raise challenges and conflicts, improve the proposed changes etc.
  • If you wish to continuously participate in shaping the specification, it would be useful to go over the open PRs once a week or so, to make sure you have a chance to communicate your needs, ideas and thoughts before changes get merged into the spec

Important files in this repo to know about:

  • The file resources.md lists which team members have access to which project resources, openness and transparency are important to us!
  • The actual specification source texts are in the spec/ directory
  • JSON-LD context files are in the rdf/ directory

Repo mirrors

Website build instructions

The ForgeFed website is generated via a script using the Markdown files in this repository. See ./build.sh for more details.

License

All contents of this repository are are freely available under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.

The ForgeFed logo was created by iko.

Historical resources

ForgeFed started its life on a mailing list. The old ForgeFed forum at talk.feneas.org can be viewed via the Internet Archive's Wayback Machine.

Funding

This project is funded through the NGI Zero Entrust Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.

NLnet foundation logo NGI Zero Entrust Logo