forgefed implementation

Key Requirements

Implement the forgefed specification using ActivityPub for a common web server deployment, eg a LAMP server, cgi, fastcgi, or nodejs.
If using a persistent process, such as the node daemon, implement a cronjob that starts/stops the process on a cycle.
Must use one of the following frameworks: yesod, django, laravel, or react/react-native w/ redux on top of nodejs.
Users on one instance can interact with users of another instance for issue tracking, pull/merge requests, knowledge of public forks, and comments related to each.
Support at least git, though the forge doesn't necessarily need to pass the repository, just reference to the repository, eg the location and when necessary the commit hashes.
Import and export of a project from one instance to another.
Must have either the MIT, Apache 2, AGPLv3 or GPLv3, or compatible license.

Users create a high level task in the WBS and link to other issue trackers that contain lower level details.
Users can examine or determine critical paths.

All primary features work without client side JavaScript.
Include a CLI interface at the server or for clients.
Implement features from Project Management Tool.
Support other version control systems such as hg, darcs, fossil, svn.
Pass an accessibility audit, eg UI has markup and style that allows screenreaders.
Add one-way federation for tracking existing projects already in github, bitbucket, gogs, gitlab.
Create a module for existing gogs, gitlab, redmine, or trac to join the federation.
Add comment support from other ActivityPub apps.
Add comment support from fediverse apps in general, for example OStatus.
Use OpenID for login (already off the shelf if using yesod).
Since federated, implement a way to use with org-mode and magit in emacs.

Review [WikiPedia ActivityPub][ActivityPub articles] and other implementations such as Mastodon.
Perhaps instead of using a persistent process, add a manual or lazy feature to let the user get and then review changes to import.

TBD