2e72684fd5
This is such a huge patch, it's probably impossible to tell what it does by looking at the code. One thing is clear: It changes *everything* :P so here's an overview: - There are now 5 types of actors, each having its own top-level route - So projects, repos, etc. are no longer "under" sharers - Actor routes are now based on their KeyHashid, there are no "idents" anymore, i.e. URLs look random and don't contain user or repo names - No sharers anymore; people and groups are distinct entities not sharing a common namespace or anything like that - Project has been renamed to Deck and it simply means a ticket tracker; repos are no longer "under" projects - In addition to Person, Group, Repo and Deck, there's a new actor type Loom, which is a patch tracker; i.e. Repo actors don't manage MRs anymore - All C2S and S2S is temporarily disabled, because huge changes to the whole code are required and I'll do them gradually in the next patches - Since form-based actions are implemented using C2S, they're disabled as well, so Vervis is now essentially read-only - Some views have been temporarily removed, e.g. repo history and commit view - A huge set of DB migrations has been added to adapt the DB to these changes; I haven't tested them yet on a read DB so there may be errors there; I'll fix them in the next patches if I find any (probably going to test on the main instance where Vervis itself is hosted...) - Some modules got tech upgrades, e.g. LocalActor became a higher-kinded type and a similar pattern is probably relevant for several other types - There's an 'Actor' entity in the DB schema now, and all 5 actor types use it for common things like inbox and outbox - Although inbox and outbox are used only by Actor, so essentially could be removed, I haven't removed them; that's because I wonder if at some point users can have a tree of inboxes much like in email; I don't have an excuse for Outbox, but anyway, leaving them as is for now - Workflows, roles and collaborators are partially removed/unused until I figure out a sane federated way to provide these features - Since repo routes don't contain a "sharer" anymore, SSH URIs are now simpler, they already look like user@host/repo regardless of who "controls" that repo
48 lines
1 KiB
Text
48 lines
1 KiB
Text
Person
|
|
RemoteObject
|
|
RemoteActivity
|
|
|
|
Discussion
|
|
|
|
FollowerSet
|
|
|
|
Outbox
|
|
|
|
OutboxItem
|
|
outbox OutboxId
|
|
activity PersistJSONObject
|
|
published UTCTime
|
|
|
|
Ticket
|
|
number Int Maybe
|
|
created UTCTime
|
|
title Text -- HTML
|
|
source Text -- Pandoc Markdown
|
|
description Text -- HTML
|
|
assignee PersonId Maybe
|
|
status TicketStatus
|
|
discuss DiscussionId
|
|
followers FollowerSetId
|
|
accept OutboxItemId
|
|
|
|
UniqueTicketDiscuss discuss
|
|
UniqueTicketFollowers followers
|
|
UniqueTicketAccept accept
|
|
|
|
RemoteTicketDependency
|
|
ident RemoteObjectId
|
|
child LocalTicketId
|
|
childNew TicketId
|
|
accept RemoteActivityId
|
|
|
|
UniqueRemoteTicketDependency ident
|
|
UniqueRemoteTicketDependencyAccept accept
|
|
|
|
LocalTicket
|
|
ticket TicketId
|
|
discuss DiscussionId
|
|
followers FollowerSetId
|
|
|
|
UniqueLocalTicket ticket
|
|
UniqueLocalTicketDiscussion discuss
|
|
UniqueLocalTicketFollowers followers
|