News for hackers. Stuff that matters.
Re:ForgeFed: A federation protocol for interop between versi... by rapnie on Saturday June 20, 2020 @02:51AM (#23582300)
Check the roadmap. ForgeFed recently received funding from NLNet and you could be compensated for work on roadmap items: https://notabug.org/peers/forgefed/issues/87

These are some forges under consideration for ForgeFed support: https://notabug.org/peers/forgefed/issues/59

Here is ForgeFed issue on Gitea project: https://github.com/go-gitea/gitea/issues/9045

Re:ForgeFed: A federation protocol for interop between versi... by 1wd on Saturday June 20, 2020 @03:22AM (#23582397)
I saw the initial discussions in 2018 and was intrigued enough to start writing a module for our VCS. But after a while I noticed it was (still) only a glorified notification system. I saw no advantage over email notification, and could not even really test the interoperability as there seemed to be no actual "client" application that could even receive notifications. Has this situation improved? What should I look at first when attempting integration again?
Re:ForgeFed: A federation protocol for interop between versi... by dbmueller on Saturday June 20, 2020 @07:05AM (#23583240)
what's your vcs?
Re:ForgeFed: A federation protocol for interop between versi... by dang on Friday June 19, 2020 @09:38PM (#23580764)
Re:ForgeFed: A federation protocol for interop between versi... by LockAndLol on Saturday June 20, 2020 @05:48AM (#23582919)
It'd be good to know how to contribute. Do they have regular calls? Are the documents written async? How are things agreed upon? Do they need outside input?

They don't seem to have a CONTRIBUTIG.md

Re:ForgeFed: A federation protocol for interop between versi... by pdimitar on Saturday June 20, 2020 @05:38AM (#23582878)
Can somebody TL;DR this for us? What language(s) is/are used, for example? That can be quite important as well, some runtimes and/or compilers produce security-imperfect code after all.

If this is to take off it should be quite secure.