bbc4f30 Spec: Add TicketTracker and PatchTracker actor types (#157)

Authored and Committed by fr33domlover 2 years ago
    Spec: Add TicketTracker and PatchTracker actor types (#157)
    
    Rather than being flexible and ambigious about types of actors, the spec
    now clearly specifies 3 forge related actor types:
    
    - Repository, which already existed
    - The now added TicketTracker
    - The now added PatchTracker
    
    There are other actor types such as Person of course, but Person is a
    standard ActivityPub type so we don't need to define it in ForgeFed :)
    
    On forges like Gitea and GitLab, projects contain all of those 3
    types of components, but any other combination is valid and supported.
    
    In addition to adding the actor types:
    
    - Ticket's 'context' in the Modeling spec requires the context to be a
      TicketTracker or a PatchTracker (but I haven't used the MUST word...
      yet, just in case some unexpected use case comes up)
    - In the Behavior spec, I removed the section talking about flexibility
      of actors because explicit actor types are now provided instead (yay,
      simpler life)
    
    Co-authored-by: fr33domlover <fr33domlover@riseup.net>
    Reviewed-on: https://codeberg.org/ForgeFed/ForgeFed/pulls/157
    Reviewed-by: Anthony Wang <xy@noreply.codeberg.org>
    
        
file modified
+0 -50
file modified
+5 -3
file modified
+69 -0