1
0
Fork
You've already forked ForgeFed
0
forked from ForgeFed/ForgeFed
ActivityPub-based forge federation protocol specification
Bikeshed 90.2%
CSS 6.6%
HTML 2.7%
Shell 0.5%
Anthony Wang bf4ae77cc3
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Rewrite .woodpecker.yml to use Alpine and pipx
2023年08月30日 14:34:29 -05:00
content Blog: Vervis Invite demo ( #202 ) 2023年07月19日 19:20:53 +00:00
doc Update doc README ( #154 ) 2022年07月12日 19:10:50 +02:00
static Build website pages & blog using Zola ( #191 ) 2023年03月27日 18:53:11 +00:00
templates enable atom feed auto discovery ( #205 ) 2023年08月30日 18:21:44 +00:00
.gitignore Build website pages & blog using Zola ( #191 ) 2023年03月27日 18:53:11 +00:00
.woodpecker.yml Rewrite .woodpecker.yml to use Alpine and pipx 2023年08月30日 14:34:29 -05:00
build.sh Rewrite .woodpecker.yml to use Alpine and pipx 2023年08月30日 14:34:29 -05:00
config.toml Generate Atom feed and replace "pandoc" with "Zola" in the footer ( #193 ) 2023年03月29日 17:29:42 +00:00
context.jsonld Build website pages & blog using Zola ( #191 ) 2023年03月27日 18:53:11 +00:00
deploy.sh Build website pages & blog using Zola ( #191 ) 2023年03月27日 18:53:11 +00:00
LICENSE Fix #173 : Move redundant README content to website index.md ( #187 ) 2023年02月06日 12:07:18 +00:00
README.md Fix #173 : Move redundant README content to website index.md ( #187 ) 2023年02月06日 12:07:18 +00:00
resources.md Update 'resources.md' 2022年06月24日 00:07:25 +02:00
spec.bs Fixes typos and clarifies some sentences ( #190 ) 2023年03月25日 18:02:53 +00:00

ForgeFed

Get it on Codeberg

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.