https://forgefed.org/ (repo: https://codeberg.org/ForgeFed/ForgeFed )

It is a protocol attempting to create a standard for distributed projects, including issues, code reviews, forks and other things. It looks to me like it might make sense for bit-bug to eventually implemet some of their API.

... though it is decentralized, not distributed.

My thoughts on this after skimming the documents:

• it's an awesome idea in general (think opening a PR on Gitlab from Github)
• it would make sense for git-bug, but only in a configuration where a project expose the webUI in a centralized server to accept public contribution (forgefed require a public endpoint)
• I don't have the bandwidth to deal with that subject and many more pressing things to implement ...

I mentioned git-bug as a project for consideration on the ForgeFed forum: https://talk.feneas.org/t/standard-list-of-existing-software-to-examine/194/10

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

bots 😩

github-actions (github-actions) removed label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 8 months ago

github-actions (github-actions) removed label lifecycle/stale 8 months ago

sudoforge added label area/bridge 8 months ago

sudoforge added label kind/feature 8 months ago

sudoforge added label triage/needs-priority 8 months ago

sudoforge added label triage/needs-information 8 months ago

sudoforge added label triage/needs-approval 8 months ago

sudoforge removed label lifecycle/rotten 8 months ago

It would be nice if this was available as a bridge if not fully integrated. e.g. just pulling from a forgefed-enabled instance