Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Federated issue tracking #11

@yookoala

Description

@yookoala

Problem

  1. Ken on server A created an issue to Lennon's repository on server B.
  2. Mandy on server B is a contributor to Lennon's repository.
  3. Oprah on server C is also a contributor to Lenonn's repository.
  4. Who should have the permission to close the issue? And how?

@tantek has experience on Github bridging. And he has some insight about cross domain permission handling. He raised interesting point in the ActivityPub community group meeting tonight that lead me thinking of this problem. (I think @cwebber tried to raise the same point but I was too stupid to pick up.)

The same problem also applies to a PR. Do we handle it? Or do we omit it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions