2016-02-14 10:10:21 +01:00
|
|
|
-- This file is part of Vervis.
|
|
|
|
|
--
|
2024-04-10 15:27:29 +02:00
|
|
|
-- Written in 2016, 2018, 2019, 2020, 2022, 2024
|
2022-06-22 08:19:37 +02:00
|
|
|
-- by fr33domlover <fr33domlover@riseup.net>.
|
2016-02-14 10:10:21 +01:00
|
|
|
--
|
|
|
|
|
-- ♡ Copying is an act of love. Please copy, reuse and share.
|
|
|
|
|
--
|
|
|
|
|
-- The author(s) have dedicated all copyright and related and neighboring
|
|
|
|
|
-- rights to this software to the public domain worldwide. This software is
|
|
|
|
|
-- distributed without any warranty.
|
|
|
|
|
--
|
|
|
|
|
-- You should have received a copy of the CC0 Public Domain Dedication along
|
|
|
|
|
-- with this software. If not, see
|
|
|
|
|
-- <http://creativecommons.org/publicdomain/zero/1.0/>.
|
|
|
|
|
|
2024-07-06 11:53:31 +02:00
|
|
|
Report
|
|
|
|
|
time UTCTime
|
|
|
|
|
message Text
|
|
|
|
|
types [ByteString]
|
|
|
|
|
body ByteString
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-- ========================================================================= --
|
|
|
|
|
-- Remote Object
|
|
|
|
|
-- ========================================================================= --
|
2019-11-06 20:47:50 +01:00
|
|
|
|
|
|
|
|
Instance
|
|
|
|
|
host Host
|
|
|
|
|
|
|
|
|
|
UniqueInstance host
|
|
|
|
|
|
2019-11-05 05:08:36 +01:00
|
|
|
RemoteObject
|
2023-04-29 12:40:44 +02:00
|
|
|
instance InstanceId
|
|
|
|
|
ident LocalURI
|
|
|
|
|
-- fetched UTCTime Maybe
|
|
|
|
|
|
|
|
|
|
-- type Text Maybe
|
|
|
|
|
-- followers LocalURI Maybe
|
|
|
|
|
-- team LocalURI Maybe
|
2019-11-05 05:08:36 +01:00
|
|
|
|
|
|
|
|
UniqueRemoteObject instance ident
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
RemoteActivity
|
|
|
|
|
ident RemoteObjectId
|
|
|
|
|
content PersistJSONObject
|
|
|
|
|
received UTCTime
|
2016-05-24 10:28:57 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueRemoteActivity ident
|
2022-07-19 14:12:49 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UnfetchedRemoteActor
|
|
|
|
|
ident RemoteObjectId
|
|
|
|
|
since UTCTime Maybe
|
2022-07-19 14:12:49 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueUnfetchedRemoteActor ident
|
2016-02-16 12:41:13 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
RemoteActor
|
|
|
|
|
ident RemoteObjectId
|
|
|
|
|
name Text Maybe
|
|
|
|
|
inbox LocalURI
|
|
|
|
|
followers LocalURI Maybe
|
|
|
|
|
errorSince UTCTime Maybe
|
2023-06-27 12:27:51 +02:00
|
|
|
type ActorType
|
2016-02-16 12:41:13 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueRemoteActor ident
|
|
|
|
|
|
|
|
|
|
RemoteCollection
|
|
|
|
|
ident RemoteObjectId
|
|
|
|
|
|
|
|
|
|
UniqueRemoteCollection ident
|
|
|
|
|
|
|
|
|
|
-- ========================================================================= --
|
|
|
|
|
-- Local Actor
|
|
|
|
|
-- ========================================================================= --
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- Outbox
|
|
|
|
|
-------------------------------------------------------------------------------
|
2019-06-15 20:51:26 +02:00
|
|
|
|
|
|
|
|
Outbox
|
2016-02-16 12:41:13 +01:00
|
|
|
|
2019-03-28 22:08:30 +01:00
|
|
|
OutboxItem
|
2019-06-15 20:51:26 +02:00
|
|
|
outbox OutboxId
|
2019-06-29 05:19:00 +02:00
|
|
|
activity PersistJSONObject
|
2019-03-28 22:08:30 +01:00
|
|
|
published UTCTime
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- Inbox
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
|
2019-06-09 15:16:32 +02:00
|
|
|
Inbox
|
|
|
|
|
|
2019-05-05 12:20:55 +02:00
|
|
|
InboxItem
|
2022-09-01 13:21:31 +02:00
|
|
|
unread Bool
|
|
|
|
|
received UTCTime
|
2024-04-27 18:15:28 +02:00
|
|
|
result Text
|
2019-05-05 12:20:55 +02:00
|
|
|
|
2019-04-11 15:44:44 +02:00
|
|
|
InboxItemLocal
|
2019-06-09 15:16:32 +02:00
|
|
|
inbox InboxId
|
2019-04-11 15:44:44 +02:00
|
|
|
activity OutboxItemId
|
2019-05-05 12:20:55 +02:00
|
|
|
item InboxItemId
|
2019-04-11 15:44:44 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueInboxItemLocal inbox activity
|
2019-05-05 12:20:55 +02:00
|
|
|
UniqueInboxItemLocalItem item
|
2019-04-11 15:44:44 +02:00
|
|
|
|
2019-04-23 04:57:53 +02:00
|
|
|
InboxItemRemote
|
2019-06-09 15:16:32 +02:00
|
|
|
inbox InboxId
|
2019-04-23 04:57:53 +02:00
|
|
|
activity RemoteActivityId
|
2019-05-05 12:20:55 +02:00
|
|
|
item InboxItemId
|
2019-04-23 04:57:53 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueInboxItemRemote inbox activity
|
2019-05-05 12:20:55 +02:00
|
|
|
UniqueInboxItemRemoteItem item
|
2019-04-23 04:57:53 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- Followers
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
FollowerSet
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- Actors
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Actor
|
|
|
|
|
name Text
|
|
|
|
|
desc Text
|
|
|
|
|
createdAt UTCTime
|
|
|
|
|
inbox InboxId
|
|
|
|
|
outbox OutboxId
|
|
|
|
|
followers FollowerSetId
|
2024-04-27 21:46:37 +02:00
|
|
|
errbox InboxId
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
|
|
|
|
|
UniqueActorInbox inbox
|
|
|
|
|
UniqueActorOutbox outbox
|
|
|
|
|
UniqueActorFollowers followers
|
|
|
|
|
|
2024-08-06 11:33:02 +02:00
|
|
|
ActorCreateLocal
|
|
|
|
|
actor ActorId
|
|
|
|
|
create OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueActorCreateLocalActor actor
|
|
|
|
|
UniqueActorCreateLocalCreate create
|
|
|
|
|
|
|
|
|
|
ActorCreateRemote
|
|
|
|
|
actor ActorId
|
|
|
|
|
create RemoteActivityId
|
|
|
|
|
sender RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueActorCreateRemoteActor actor
|
|
|
|
|
UniqueActorCreateRemoteCreate create
|
|
|
|
|
|
Improve the AP async HTTP delivery API and per-actor key support
New iteration of the ActivityPub delivery implementation and interface.
Advantages over previous interface:
* When sending a ByteString body, the sender is explicitly passed as a
parameter instead of JSON-parsing it out of the ByteString
* Clear 3 operations provided: Send, Resend and Forward
* Support for per-actor keys
* Actor-type-specific functions (e.g. deliverRemoteDB_D) removed
* Only the most high-level API is exposed to Activity handler code, making
handler code more concise and clear
Also added in this patch:
* Foundation for per-actor key support
* 1 key per actor allowed in DB
* Disabled C2S and S2S handlers now un-exported for clarity
* Audience and capability parsing automatically done for all C2S handlers
* Audience and activity composition automatically done for Vervis.Client
builder functions
Caveats:
* Actor documents still don't link to their per-actor keys; that should be the
last piece to complete per-actor key support
* No moderation and anti-spam tools yet
* Delivery API doesn't yet have good integration of persistence layer, e.g.
activity is separately encoded into bytestring for DB and for HTTP; this will
be improved in the next iteration
* Periodic delivery now done in 3 separate steps, running sequentially; it
simplifies the code, but may be changed for efficiency/robustness in the next
iterations
* Periodic delivery collects per-actor keys in a
1-DB-transaction-for-each-delivery fashion, rather than grabbing them in the
big Esqueleto query (or keeping the signed output in the DB; this isn't done
currently to allow for smooth actor key renewal)
* No support yet in the API for delivery where the actor key has already been
fetched, rather than doing a DB transaction to grab it; such support would be
just an optimization, so it's low-priority, but will be added in later
iterations
2022-10-12 18:50:11 +02:00
|
|
|
SigKey
|
|
|
|
|
actor ActorId
|
|
|
|
|
material ActorKey
|
|
|
|
|
|
|
|
|
|
UniqueSigKey actor
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
Person
|
|
|
|
|
username Username
|
|
|
|
|
login Text
|
|
|
|
|
passphraseHash ByteString
|
|
|
|
|
email EmailAddress
|
|
|
|
|
verified Bool
|
|
|
|
|
verifiedKey Text
|
|
|
|
|
verifiedKeyCreated UTCTime
|
|
|
|
|
resetPassKey Text
|
|
|
|
|
resetPassKeyCreated UTCTime
|
|
|
|
|
actor ActorId
|
|
|
|
|
-- reviewFollow Bool
|
|
|
|
|
|
|
|
|
|
UniquePersonUsername username
|
|
|
|
|
UniquePersonLogin login
|
|
|
|
|
UniquePersonEmail email
|
|
|
|
|
UniquePersonActor actor
|
|
|
|
|
|
2024-04-20 02:52:34 +02:00
|
|
|
Resource
|
|
|
|
|
actor ActorId
|
|
|
|
|
|
|
|
|
|
UniqueResource actor
|
|
|
|
|
|
2024-04-29 13:38:37 +02:00
|
|
|
Komponent
|
|
|
|
|
resource ResourceId
|
|
|
|
|
|
|
|
|
|
UniqueKomponent resource
|
|
|
|
|
|
2024-08-02 17:31:06 +02:00
|
|
|
Factory
|
2024-08-06 14:37:49 +02:00
|
|
|
resource ResourceId
|
|
|
|
|
allowDeck Bool
|
|
|
|
|
allowProject Bool
|
|
|
|
|
allowTeam Bool
|
2024-08-02 17:31:06 +02:00
|
|
|
|
|
|
|
|
UniqueFactory resource
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-- ========================================================================= --
|
|
|
|
|
-- Delivery
|
|
|
|
|
-- ========================================================================= --
|
|
|
|
|
|
2019-04-16 16:27:50 +02:00
|
|
|
UnlinkedDelivery
|
2019-05-02 11:31:56 +02:00
|
|
|
recipient UnfetchedRemoteActorId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
forwarding Bool
|
|
|
|
|
running Bool
|
2019-04-16 16:27:50 +02:00
|
|
|
|
|
|
|
|
UniqueUnlinkedDelivery recipient activity
|
|
|
|
|
|
|
|
|
|
Delivery
|
2019-05-02 11:31:56 +02:00
|
|
|
recipient RemoteActorId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
forwarding Bool
|
|
|
|
|
running Bool
|
2019-04-16 16:27:50 +02:00
|
|
|
|
|
|
|
|
UniqueDelivery recipient activity
|
|
|
|
|
|
2019-05-03 23:04:53 +02:00
|
|
|
Forwarding
|
|
|
|
|
recipient RemoteActorId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
activityRaw ByteString
|
|
|
|
|
signature ByteString
|
Improve the AP async HTTP delivery API and per-actor key support
New iteration of the ActivityPub delivery implementation and interface.
Advantages over previous interface:
* When sending a ByteString body, the sender is explicitly passed as a
parameter instead of JSON-parsing it out of the ByteString
* Clear 3 operations provided: Send, Resend and Forward
* Support for per-actor keys
* Actor-type-specific functions (e.g. deliverRemoteDB_D) removed
* Only the most high-level API is exposed to Activity handler code, making
handler code more concise and clear
Also added in this patch:
* Foundation for per-actor key support
* 1 key per actor allowed in DB
* Disabled C2S and S2S handlers now un-exported for clarity
* Audience and capability parsing automatically done for all C2S handlers
* Audience and activity composition automatically done for Vervis.Client
builder functions
Caveats:
* Actor documents still don't link to their per-actor keys; that should be the
last piece to complete per-actor key support
* No moderation and anti-spam tools yet
* Delivery API doesn't yet have good integration of persistence layer, e.g.
activity is separately encoded into bytestring for DB and for HTTP; this will
be improved in the next iteration
* Periodic delivery now done in 3 separate steps, running sequentially; it
simplifies the code, but may be changed for efficiency/robustness in the next
iterations
* Periodic delivery collects per-actor keys in a
1-DB-transaction-for-each-delivery fashion, rather than grabbing them in the
big Esqueleto query (or keeping the signed output in the DB; this isn't done
currently to allow for smooth actor key renewal)
* No support yet in the API for delivery where the actor key has already been
fetched, rather than doing a DB transaction to grab it; such support would be
just an optimization, so it's low-priority, but will be added in later
iterations
2022-10-12 18:50:11 +02:00
|
|
|
forwarder ActorId
|
2019-05-03 23:04:53 +02:00
|
|
|
running Bool
|
|
|
|
|
|
|
|
|
|
UniqueForwarding recipient activity
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-- ========================================================================= --
|
|
|
|
|
-- ========================================================================= --
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- People
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
|
2019-02-03 14:58:14 +01:00
|
|
|
VerifKey
|
2019-07-23 15:59:48 +02:00
|
|
|
ident LocalRefURI
|
2019-02-06 03:48:23 +01:00
|
|
|
instance InstanceId
|
|
|
|
|
expires UTCTime Maybe
|
2019-03-11 00:15:42 +01:00
|
|
|
public PublicVerifKey
|
2019-04-12 02:56:27 +02:00
|
|
|
sharer RemoteActorId Maybe
|
2019-02-03 14:58:14 +01:00
|
|
|
|
2019-02-22 00:59:53 +01:00
|
|
|
UniqueVerifKey instance ident
|
2019-02-03 14:58:14 +01:00
|
|
|
|
Record usage of instance keys in the DB
When we verify an HTTP signature,
* If we know the key, check in the DB whether we know the actor lists it. If it
doesn't, and there's room left for keys, HTTP GET the actor and update the DB
accordingly.
* If we know the key but had to update it, do the same, check usage in DB and
update DB if needed
* If we don't know the key, record usage in DB
However,
* If we're GETing a key and discovering it's a shared key, we GET the actor to
verify it lists the key. When we don't know the key at all yet, that's fine
(can be further optimized but it's marginal), but if it's a key we do know,
it means we already know the actor and for now it's enough for us to rely
only on the DB to test usage.
2019-02-19 11:54:55 +01:00
|
|
|
VerifKeySharedUsage
|
|
|
|
|
key VerifKeyId
|
2019-04-12 02:56:27 +02:00
|
|
|
user RemoteActorId
|
Record usage of instance keys in the DB
When we verify an HTTP signature,
* If we know the key, check in the DB whether we know the actor lists it. If it
doesn't, and there's room left for keys, HTTP GET the actor and update the DB
accordingly.
* If we know the key but had to update it, do the same, check usage in DB and
update DB if needed
* If we don't know the key, record usage in DB
However,
* If we're GETing a key and discovering it's a shared key, we GET the actor to
verify it lists the key. When we don't know the key at all yet, that's fine
(can be further optimized but it's marginal), but if it's a key we do know,
it means we already know the actor and for now it's enough for us to rely
only on the DB to test usage.
2019-02-19 11:54:55 +01:00
|
|
|
|
|
|
|
|
UniqueVerifKeySharedUsage key user
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
--RemoteFollowRequest
|
|
|
|
|
-- actor RemoteActorId
|
|
|
|
|
-- target PersonId
|
|
|
|
|
--
|
|
|
|
|
-- UniqueRemoteFollowRequest actor target
|
|
|
|
|
--
|
2019-05-18 00:42:01 +02:00
|
|
|
|
2019-09-25 12:43:05 +02:00
|
|
|
FollowRemoteRequest
|
|
|
|
|
person PersonId
|
|
|
|
|
target FedURI
|
|
|
|
|
recip FedURI Maybe
|
|
|
|
|
public Bool
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueFollowRemoteRequest person target
|
|
|
|
|
UniqueFollowRemoteRequestActivity activity
|
|
|
|
|
|
|
|
|
|
FollowRemote
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
actor ActorId
|
2019-09-25 12:43:05 +02:00
|
|
|
recip RemoteActorId -- actor managing the followed object
|
|
|
|
|
target FedURI -- the followed object
|
|
|
|
|
public Bool
|
|
|
|
|
follow OutboxItemId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueFollowRemote actor target
|
2019-09-25 12:43:05 +02:00
|
|
|
UniqueFollowRemoteFollow follow
|
|
|
|
|
UniqueFollowRemoteAccept accept
|
|
|
|
|
|
2023-06-15 14:44:43 +02:00
|
|
|
FollowRequest
|
|
|
|
|
actor ActorId
|
|
|
|
|
target FollowerSetId
|
|
|
|
|
public Bool
|
|
|
|
|
follow OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueFollowRequest actor target
|
|
|
|
|
UniqueFollowRequestFollow follow
|
2019-04-11 15:26:57 +02:00
|
|
|
|
|
|
|
|
Follow
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
actor ActorId
|
2019-04-11 15:26:57 +02:00
|
|
|
target FollowerSetId
|
2019-09-09 02:33:36 +02:00
|
|
|
public Bool
|
2019-09-25 12:43:05 +02:00
|
|
|
follow OutboxItemId
|
|
|
|
|
accept OutboxItemId
|
2019-04-11 15:26:57 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueFollow actor target
|
2019-09-25 12:43:05 +02:00
|
|
|
UniqueFollowFollow follow
|
|
|
|
|
UniqueFollowAccept accept
|
2019-04-11 15:26:57 +02:00
|
|
|
|
|
|
|
|
RemoteFollow
|
2019-04-12 02:56:27 +02:00
|
|
|
actor RemoteActorId
|
2019-04-11 15:26:57 +02:00
|
|
|
target FollowerSetId
|
2019-09-09 02:33:36 +02:00
|
|
|
public Bool
|
2019-09-25 12:43:05 +02:00
|
|
|
follow RemoteActivityId
|
|
|
|
|
accept OutboxItemId
|
2019-04-11 15:26:57 +02:00
|
|
|
|
|
|
|
|
UniqueRemoteFollow actor target
|
2019-09-25 12:43:05 +02:00
|
|
|
UniqueRemoteFollowFollow follow
|
|
|
|
|
UniqueRemoteFollowAccept accept
|
2019-04-11 15:26:57 +02:00
|
|
|
|
2016-03-06 12:58:48 +01:00
|
|
|
SshKey
|
2016-05-23 22:46:54 +02:00
|
|
|
ident KyIdent
|
2016-03-06 12:58:48 +01:00
|
|
|
person PersonId
|
|
|
|
|
algo ByteString
|
|
|
|
|
content ByteString
|
|
|
|
|
|
2016-05-23 22:46:54 +02:00
|
|
|
UniqueSshKey person ident
|
2016-03-06 12:58:48 +01:00
|
|
|
|
2016-02-16 12:41:13 +01:00
|
|
|
Group
|
2024-04-20 02:52:34 +02:00
|
|
|
actor ActorId
|
|
|
|
|
resource ResourceId
|
2016-02-16 12:41:13 +01:00
|
|
|
|
2023-11-21 14:48:14 +01:00
|
|
|
UniqueGroupActor actor
|
2016-05-24 10:28:57 +02:00
|
|
|
|
|
|
|
|
GroupMember
|
|
|
|
|
person PersonId
|
|
|
|
|
group GroupId
|
2016-05-25 17:52:15 +02:00
|
|
|
role GroupRole
|
2016-05-26 18:25:23 +02:00
|
|
|
joined UTCTime
|
2016-05-24 10:28:57 +02:00
|
|
|
|
|
|
|
|
UniqueGroupMember person group
|
|
|
|
|
|
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
|
-- Projects
|
|
|
|
|
-------------------------------------------------------------------------------
|
2016-02-16 12:41:13 +01:00
|
|
|
|
2023-06-26 16:26:20 +02:00
|
|
|
Project
|
2024-04-20 02:52:34 +02:00
|
|
|
actor ActorId
|
|
|
|
|
resource ResourceId
|
2023-06-26 16:26:20 +02:00
|
|
|
|
|
|
|
|
UniqueProjectActor actor
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
Deck
|
2022-07-19 14:12:49 +02:00
|
|
|
actor ActorId
|
2024-04-20 02:52:34 +02:00
|
|
|
resource ResourceId
|
2024-04-29 13:38:37 +02:00
|
|
|
komponent KomponentId
|
2016-08-08 21:05:22 +02:00
|
|
|
workflow WorkflowId
|
2016-08-08 20:35:01 +02:00
|
|
|
nextTicket Int
|
2019-01-29 23:24:32 +01:00
|
|
|
wiki RepoId Maybe
|
2016-02-16 12:41:13 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueDeckActor actor
|
|
|
|
|
|
|
|
|
|
Loom
|
|
|
|
|
nextTicket Int
|
|
|
|
|
actor ActorId
|
2024-04-20 02:52:34 +02:00
|
|
|
resource ResourceId
|
2024-04-29 13:38:37 +02:00
|
|
|
komponent KomponentId
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
repo RepoId
|
|
|
|
|
|
|
|
|
|
UniqueLoomActor actor
|
|
|
|
|
UniqueLoomRepo repo
|
2016-02-16 12:41:13 +01:00
|
|
|
|
|
|
|
|
Repo
|
2016-08-08 20:35:01 +02:00
|
|
|
vcs VersionControlSystem
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
project DeckId Maybe
|
2016-08-08 20:35:01 +02:00
|
|
|
mainBranch Text
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
actor ActorId
|
2024-04-20 02:52:34 +02:00
|
|
|
resource ResourceId
|
2024-04-29 13:38:37 +02:00
|
|
|
komponent KomponentId
|
2022-09-17 10:31:22 +02:00
|
|
|
loom LoomId Maybe
|
2016-02-16 12:41:13 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueRepoActor actor
|
2016-02-16 12:41:13 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
-- I removed the 'sharer' field so Workflows don't specify who controls them
|
|
|
|
|
-- For now there's no way to create new ones, and what's already in the DB can
|
|
|
|
|
-- be publicly experimented with, until I make a plan for federated workflows
|
2016-08-08 13:05:19 +02:00
|
|
|
Workflow
|
|
|
|
|
ident WflIdent
|
|
|
|
|
name Text Maybe
|
|
|
|
|
desc Text Maybe
|
2016-09-01 19:40:02 +02:00
|
|
|
scope WorkflowScope
|
2016-08-08 13:05:19 +02:00
|
|
|
|
2016-08-08 16:01:06 +02:00
|
|
|
WorkflowField
|
2016-08-11 11:27:30 +02:00
|
|
|
workflow WorkflowId
|
|
|
|
|
ident FldIdent
|
|
|
|
|
name Text
|
2020-01-05 13:04:17 +01:00
|
|
|
desc Text Maybe
|
2016-08-11 11:27:30 +02:00
|
|
|
type WorkflowFieldType
|
2020-01-05 13:04:17 +01:00
|
|
|
enm WorkflowEnumId Maybe
|
2016-08-11 11:27:30 +02:00
|
|
|
required Bool
|
|
|
|
|
constant Bool
|
|
|
|
|
filterNew Bool
|
|
|
|
|
filterTodo Bool
|
|
|
|
|
filterClosed Bool
|
2020-01-16 11:29:47 +01:00
|
|
|
color Int Maybe
|
2016-08-08 16:01:06 +02:00
|
|
|
|
|
|
|
|
UniqueWorkflowField workflow ident
|
|
|
|
|
|
2020-01-05 13:04:17 +01:00
|
|
|
WorkflowEnum
|
2016-08-08 16:48:38 +02:00
|
|
|
workflow WorkflowId
|
|
|
|
|
ident EnmIdent
|
|
|
|
|
name Text
|
|
|
|
|
desc Text Maybe
|
|
|
|
|
|
2020-01-05 13:04:17 +01:00
|
|
|
UniqueWorkflowEnum workflow ident
|
2016-08-08 16:48:38 +02:00
|
|
|
|
2020-01-05 13:04:17 +01:00
|
|
|
WorkflowEnumCtor
|
|
|
|
|
enum WorkflowEnumId
|
2016-08-08 19:05:09 +02:00
|
|
|
name Text
|
2020-01-05 13:04:17 +01:00
|
|
|
desc Text Maybe
|
2016-08-08 19:05:09 +02:00
|
|
|
|
2020-01-05 13:04:17 +01:00
|
|
|
UniqueWorkflowEnumCtor enum name
|
2016-08-08 19:05:09 +02:00
|
|
|
|
2016-08-08 22:51:58 +02:00
|
|
|
TicketParamText
|
|
|
|
|
ticket TicketId
|
|
|
|
|
field WorkflowFieldId
|
|
|
|
|
value Text
|
|
|
|
|
|
|
|
|
|
UniqueTicketParamText ticket field
|
|
|
|
|
|
2016-08-09 13:36:14 +02:00
|
|
|
TicketParamEnum
|
|
|
|
|
ticket TicketId
|
|
|
|
|
field WorkflowFieldId
|
2020-01-05 13:04:17 +01:00
|
|
|
value WorkflowEnumCtorId
|
2016-08-09 13:36:14 +02:00
|
|
|
|
|
|
|
|
UniqueTicketParamEnum ticket field value
|
|
|
|
|
|
2020-01-05 15:33:10 +01:00
|
|
|
TicketParamClass
|
|
|
|
|
ticket TicketId
|
|
|
|
|
field WorkflowFieldId
|
|
|
|
|
|
|
|
|
|
UniqueTicketParamClass ticket field
|
|
|
|
|
|
2016-04-30 22:40:33 +02:00
|
|
|
Ticket
|
2020-02-03 16:44:16 +01:00
|
|
|
number Int Maybe
|
2019-06-03 14:45:02 +02:00
|
|
|
created UTCTime
|
2022-09-21 14:50:26 +02:00
|
|
|
title Text
|
|
|
|
|
source PandocMarkdown
|
|
|
|
|
description HTML
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
discuss DiscussionId
|
|
|
|
|
followers FollowerSetId
|
|
|
|
|
accept OutboxItemId
|
2016-04-30 22:40:33 +02:00
|
|
|
|
2020-02-03 16:44:16 +01:00
|
|
|
-- UniqueTicket project number
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueTicketDiscuss discuss
|
|
|
|
|
UniqueTicketFollowers followers
|
|
|
|
|
UniqueTicketAccept accept
|
2016-05-17 22:34:22 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
TicketAssignee
|
|
|
|
|
ticket TicketId
|
|
|
|
|
person PersonId
|
2020-05-18 12:28:43 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueTicketAssignee ticket person
|
2020-02-06 05:18:19 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
TicketDeck
|
|
|
|
|
ticket TicketId
|
|
|
|
|
deck DeckId
|
2020-02-22 20:45:27 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueTicketDeck ticket
|
2020-02-22 20:45:27 +01:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
TicketLoom
|
|
|
|
|
ticket TicketId
|
|
|
|
|
loom LoomId
|
|
|
|
|
branch Text Maybe
|
2020-04-08 19:02:04 +02:00
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueTicketLoom ticket
|
2020-04-08 19:02:04 +02:00
|
|
|
|
2022-09-18 17:55:42 +02:00
|
|
|
MergeOriginLocal
|
|
|
|
|
ticket TicketLoomId
|
|
|
|
|
repo RepoId
|
|
|
|
|
branch Text Maybe
|
|
|
|
|
|
|
|
|
|
UniqueMergeOriginLocal ticket
|
|
|
|
|
|
|
|
|
|
MergeOriginRemote
|
|
|
|
|
ticket TicketLoomId
|
|
|
|
|
repo RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueMergeOriginRemote ticket
|
|
|
|
|
|
|
|
|
|
MergeOriginRemoteBranch
|
|
|
|
|
merge MergeOriginRemoteId
|
|
|
|
|
ident LocalURI Maybe
|
|
|
|
|
name Text
|
|
|
|
|
|
|
|
|
|
UniqueMergeOriginRemoteBranch merge
|
|
|
|
|
|
2019-06-07 06:26:32 +02:00
|
|
|
TicketAuthorLocal
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
ticket TicketId
|
2019-06-07 06:26:32 +02:00
|
|
|
author PersonId
|
2020-02-08 10:35:35 +01:00
|
|
|
open OutboxItemId
|
2019-06-07 06:26:32 +02:00
|
|
|
|
2020-02-08 10:35:35 +01:00
|
|
|
UniqueTicketAuthorLocal ticket
|
|
|
|
|
UniqueTicketAuthorLocalOpen open
|
2019-06-07 06:26:32 +02:00
|
|
|
|
|
|
|
|
TicketAuthorRemote
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
ticket TicketId
|
2019-06-07 06:26:32 +02:00
|
|
|
author RemoteActorId
|
2020-02-08 10:35:35 +01:00
|
|
|
open RemoteActivityId
|
2019-06-07 06:26:32 +02:00
|
|
|
|
2020-02-08 10:35:35 +01:00
|
|
|
UniqueTicketAuthorRemote ticket
|
|
|
|
|
UniqueTicketAuthorRemoteOpen open
|
2019-06-07 06:26:32 +02:00
|
|
|
|
2020-08-13 12:26:20 +02:00
|
|
|
Bundle
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
ticket TicketLoomId
|
2022-09-22 19:23:33 +02:00
|
|
|
auto Bool
|
2020-08-13 12:26:20 +02:00
|
|
|
|
2020-05-24 11:17:49 +02:00
|
|
|
Patch
|
2020-08-13 12:26:20 +02:00
|
|
|
bundle BundleId
|
2020-05-25 11:40:48 +02:00
|
|
|
created UTCTime
|
2020-08-14 23:16:33 +02:00
|
|
|
type PatchMediaType
|
2020-05-24 11:17:49 +02:00
|
|
|
content Text
|
|
|
|
|
|
2020-06-21 10:02:05 +02:00
|
|
|
RemoteTicketDependency
|
|
|
|
|
ident RemoteObjectId
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
child TicketId
|
2020-06-21 10:02:05 +02:00
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueRemoteTicketDependency ident
|
2020-06-21 10:02:05 +02:00
|
|
|
UniqueRemoteTicketDependencyAccept accept
|
2020-06-18 12:38:04 +02:00
|
|
|
|
|
|
|
|
LocalTicketDependency
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
parent TicketId
|
2019-07-11 17:14:16 +02:00
|
|
|
created UTCTime
|
2020-06-18 12:38:04 +02:00
|
|
|
accept OutboxItemId
|
|
|
|
|
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
UniqueLocalTicketDependencyAccept accept
|
|
|
|
|
|
2020-06-18 12:38:04 +02:00
|
|
|
TicketDependencyChildLocal
|
|
|
|
|
dep LocalTicketDependencyId
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
child TicketId
|
2020-06-18 12:38:04 +02:00
|
|
|
|
|
|
|
|
UniqueTicketDependencyChildLocal dep
|
|
|
|
|
|
|
|
|
|
TicketDependencyChildRemote
|
|
|
|
|
dep LocalTicketDependencyId
|
|
|
|
|
child RemoteObjectId
|
|
|
|
|
|
|
|
|
|
UniqueTicketDependencyChildRemote dep
|
|
|
|
|
|
|
|
|
|
TicketDependencyAuthorLocal
|
|
|
|
|
dep LocalTicketDependencyId
|
|
|
|
|
author PersonId
|
|
|
|
|
open OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueTicketDependencyAuthorLocal dep
|
|
|
|
|
UniqueTicketDependencyAuthorLocalOpen open
|
|
|
|
|
|
|
|
|
|
TicketDependencyAuthorRemote
|
|
|
|
|
dep LocalTicketDependencyId
|
|
|
|
|
author RemoteActorId
|
|
|
|
|
open RemoteActivityId
|
2016-06-07 22:16:15 +02:00
|
|
|
|
2020-06-18 12:38:04 +02:00
|
|
|
UniqueTicketDependencyAuthorRemote dep
|
|
|
|
|
UniqueTicketDependencyAuthorRemoteOpen open
|
2016-06-07 22:16:15 +02:00
|
|
|
|
2016-06-07 12:01:57 +02:00
|
|
|
TicketClaimRequest
|
|
|
|
|
person PersonId
|
|
|
|
|
ticket TicketId
|
2016-06-07 18:31:55 +02:00
|
|
|
message Text -- Assume this is Pandoc Markdown
|
2016-06-07 12:01:57 +02:00
|
|
|
created UTCTime
|
|
|
|
|
|
|
|
|
|
UniqueTicketClaimRequest person ticket
|
|
|
|
|
|
2020-07-28 11:35:27 +02:00
|
|
|
TicketResolve
|
Switch to new actor layout
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
2022-08-15 15:57:42 +02:00
|
|
|
ticket TicketId
|
2020-07-28 11:35:27 +02:00
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueTicketResolve ticket
|
|
|
|
|
UniqueTicketResolveAccept accept
|
|
|
|
|
|
|
|
|
|
TicketResolveLocal
|
|
|
|
|
ticket TicketResolveId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueTicketResolveLocal ticket
|
|
|
|
|
UniqueTicketResolveLocalActivity activity
|
|
|
|
|
|
|
|
|
|
TicketResolveRemote
|
|
|
|
|
ticket TicketResolveId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueTicketResolveRemote ticket
|
|
|
|
|
UniqueTicketResolveRemoteActivity activity
|
|
|
|
|
|
2016-05-17 22:34:22 +02:00
|
|
|
Discussion
|
|
|
|
|
|
2019-03-22 21:46:42 +01:00
|
|
|
RemoteDiscussion
|
2020-02-08 11:55:19 +01:00
|
|
|
ident RemoteObjectId
|
|
|
|
|
discuss DiscussionId
|
2019-03-22 21:46:42 +01:00
|
|
|
|
2020-02-08 11:55:19 +01:00
|
|
|
UniqueRemoteDiscussionIdent ident
|
|
|
|
|
UniqueRemoteDiscussion discuss
|
2019-03-22 21:46:42 +01:00
|
|
|
|
2016-05-17 22:34:22 +02:00
|
|
|
Message
|
|
|
|
|
created UTCTime
|
2022-10-16 13:26:24 +02:00
|
|
|
source PandocMarkdown
|
|
|
|
|
content HTML
|
2016-05-17 22:34:22 +02:00
|
|
|
parent MessageId Maybe
|
|
|
|
|
root DiscussionId
|
2019-02-12 12:46:12 +01:00
|
|
|
|
2019-03-20 09:07:37 +01:00
|
|
|
LocalMessage
|
2022-10-16 13:26:24 +02:00
|
|
|
author ActorId
|
2019-03-28 22:08:30 +01:00
|
|
|
rest MessageId
|
2019-05-25 05:23:57 +02:00
|
|
|
create OutboxItemId
|
2019-03-28 22:08:30 +01:00
|
|
|
unlinkedParent FedURI Maybe
|
2019-03-20 09:07:37 +01:00
|
|
|
|
|
|
|
|
UniqueLocalMessage rest
|
2019-05-25 14:59:54 +02:00
|
|
|
UniqueLocalMessageCreate create
|
2019-03-20 09:07:37 +01:00
|
|
|
|
|
|
|
|
RemoteMessage
|
2019-04-12 02:56:27 +02:00
|
|
|
author RemoteActorId
|
2020-02-10 15:07:00 +01:00
|
|
|
ident RemoteObjectId
|
2019-03-21 23:57:15 +01:00
|
|
|
rest MessageId
|
2019-04-23 04:57:53 +02:00
|
|
|
create RemoteActivityId
|
2019-03-22 21:46:42 +01:00
|
|
|
lostParent FedURI Maybe
|
2019-03-21 23:57:15 +01:00
|
|
|
|
2020-02-10 15:07:00 +01:00
|
|
|
UniqueRemoteMessageIdent ident
|
|
|
|
|
UniqueRemoteMessage rest
|
2019-06-09 20:41:37 +02:00
|
|
|
UniqueRemoteMessageCreate create
|
2019-03-20 09:07:37 +01:00
|
|
|
|
2022-06-22 08:19:37 +02:00
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
|
2023-11-22 17:11:07 +01:00
|
|
|
-- Collaborators, from resource perspective
|
2022-06-22 08:19:37 +02:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Collab
|
2024-04-26 01:00:41 +02:00
|
|
|
role Role
|
|
|
|
|
topic ResourceId
|
2022-06-22 08:19:37 +02:00
|
|
|
|
2022-09-05 18:19:52 +02:00
|
|
|
-------------------------------- Collab reason -------------------------------
|
|
|
|
|
|
|
|
|
|
CollabFulfillsLocalTopicCreation
|
|
|
|
|
collab CollabId
|
|
|
|
|
|
|
|
|
|
UniqueCollabFulfillsLocalTopicCreation collab
|
|
|
|
|
|
2024-08-06 11:33:02 +02:00
|
|
|
CollabFulfillsResidentFactory
|
|
|
|
|
collab CollabId
|
|
|
|
|
|
|
|
|
|
UniqueCollabFulfillsResidentFactory collab
|
|
|
|
|
|
2022-10-20 14:53:54 +02:00
|
|
|
CollabFulfillsInvite
|
2022-09-05 18:19:52 +02:00
|
|
|
collab CollabId
|
2023-06-28 13:10:09 +02:00
|
|
|
accept OutboxItemId
|
2022-10-20 14:53:54 +02:00
|
|
|
|
2023-06-28 13:18:45 +02:00
|
|
|
UniqueCollabFulfillsInvite collab
|
|
|
|
|
UniqueCollabFulfillsInviteAccept accept
|
2022-10-20 14:53:54 +02:00
|
|
|
|
|
|
|
|
CollabInviterLocal
|
|
|
|
|
collab CollabFulfillsInviteId
|
2022-09-05 18:19:52 +02:00
|
|
|
invite OutboxItemId
|
|
|
|
|
|
2022-10-20 14:53:54 +02:00
|
|
|
UniqueCollabInviterLocal collab
|
|
|
|
|
UniqueCollabInviterLocalInvite invite
|
2022-09-05 18:19:52 +02:00
|
|
|
|
2022-10-20 14:53:54 +02:00
|
|
|
CollabInviterRemote
|
|
|
|
|
collab CollabFulfillsInviteId
|
2022-09-05 18:19:52 +02:00
|
|
|
actor RemoteActorId
|
|
|
|
|
invite RemoteActivityId
|
|
|
|
|
|
2022-10-20 14:53:54 +02:00
|
|
|
UniqueCollabInviterRemote collab
|
|
|
|
|
UniqueCollabInviterRemoteInvite invite
|
2022-09-05 18:19:52 +02:00
|
|
|
|
2022-11-14 16:11:25 +01:00
|
|
|
CollabFulfillsJoin
|
|
|
|
|
collab CollabId
|
|
|
|
|
|
|
|
|
|
UniqueCollabFulfillsJoin collab
|
|
|
|
|
|
|
|
|
|
CollabApproverLocal
|
|
|
|
|
collab CollabFulfillsJoinId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueCollabApproverLocal collab
|
|
|
|
|
UniqueCollabApproverLocalAccept accept
|
|
|
|
|
|
|
|
|
|
CollabApproverRemote
|
|
|
|
|
collab CollabFulfillsJoinId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueCollabApproverRemote collab
|
|
|
|
|
UniqueCollabApproverRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
CollabRecipLocalJoin
|
|
|
|
|
collab CollabRecipLocalId
|
|
|
|
|
fulfills CollabFulfillsJoinId
|
|
|
|
|
join OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipLocalJoinCollab collab
|
|
|
|
|
UniqueCollabRecipLocalJoinFulfills fulfills
|
|
|
|
|
UniqueCollabRecipLocalJoinJoin join
|
|
|
|
|
|
|
|
|
|
CollabRecipRemoteJoin
|
|
|
|
|
collab CollabRecipRemoteId
|
|
|
|
|
fulfills CollabFulfillsJoinId
|
|
|
|
|
join RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipRemoteJoinCollab collab
|
|
|
|
|
UniqueCollabRecipRemoteJoinFulfills fulfills
|
|
|
|
|
UniqueCollabRecipRemoteJoinJoin join
|
|
|
|
|
|
2022-06-22 08:19:37 +02:00
|
|
|
-------------------------------- Collab recipient ----------------------------
|
|
|
|
|
|
|
|
|
|
CollabRecipLocal
|
|
|
|
|
collab CollabId
|
|
|
|
|
person PersonId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipLocal collab
|
|
|
|
|
|
2022-08-21 20:10:03 +02:00
|
|
|
CollabRecipLocalAccept
|
|
|
|
|
collab CollabRecipLocalId
|
2022-10-20 14:53:54 +02:00
|
|
|
invite CollabFulfillsInviteId
|
2022-08-21 20:10:03 +02:00
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipLocalAcceptCollab collab
|
2022-10-20 14:53:54 +02:00
|
|
|
UniqueCollabRecipLocalAcceptInvite invite
|
2022-08-21 20:10:03 +02:00
|
|
|
UniqueCollabRecipLocalAcceptAccept accept
|
|
|
|
|
|
2022-06-22 08:19:37 +02:00
|
|
|
CollabRecipRemote
|
|
|
|
|
collab CollabId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipRemote collab
|
2022-07-25 19:15:22 +02:00
|
|
|
|
2022-08-21 20:10:03 +02:00
|
|
|
CollabRecipRemoteAccept
|
|
|
|
|
collab CollabRecipRemoteId
|
2022-10-20 14:53:54 +02:00
|
|
|
invite CollabFulfillsInviteId
|
2022-08-21 20:10:03 +02:00
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueCollabRecipRemoteAcceptCollab collab
|
2022-10-20 14:53:54 +02:00
|
|
|
UniqueCollabRecipRemoteAcceptInvite invite
|
2022-08-21 20:10:03 +02:00
|
|
|
UniqueCollabRecipRemoteAcceptAccept accept
|
2023-06-27 02:20:30 +02:00
|
|
|
|
2023-11-21 19:44:09 +01:00
|
|
|
-------------------------------- Collab enable -------------------------------
|
|
|
|
|
|
|
|
|
|
CollabEnable
|
|
|
|
|
collab CollabId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueCollabEnable collab
|
|
|
|
|
UniqueCollabEnableGrant grant
|
|
|
|
|
|
|
|
|
|
-- Component: N/A
|
|
|
|
|
-- Project/Team: Witnesses that using the above Grant, the collaborator has
|
|
|
|
|
-- sent me a delegator-Grant, which I can now use to extend chains to them
|
|
|
|
|
|
|
|
|
|
CollabDelegLocal
|
|
|
|
|
enable CollabEnableId
|
|
|
|
|
recip CollabRecipLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueCollabDelegLocal enable
|
|
|
|
|
UniqueCollabDelegLocalRecip recip
|
|
|
|
|
UniqueCollabDelegLocalGrant grant
|
|
|
|
|
|
|
|
|
|
CollabDelegRemote
|
|
|
|
|
enable CollabEnableId
|
|
|
|
|
recip CollabRecipRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueCollabDelegRemote enable
|
|
|
|
|
UniqueCollabDelegRemoteRecip recip
|
|
|
|
|
UniqueCollabDelegRemoteGrant grant
|
|
|
|
|
|
2023-11-22 17:11:07 +01:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Collaborators, from person perspective
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Permit
|
|
|
|
|
person PersonId
|
|
|
|
|
role Role
|
|
|
|
|
|
|
|
|
|
-------------------------------- Permit topic --------------------------------
|
|
|
|
|
|
|
|
|
|
PermitTopicLocal
|
|
|
|
|
permit PermitId
|
2024-04-26 01:00:41 +02:00
|
|
|
topic ResourceId
|
2023-11-22 17:11:07 +01:00
|
|
|
|
|
|
|
|
UniquePermitTopicLocal permit
|
|
|
|
|
|
|
|
|
|
PermitTopicRemote
|
|
|
|
|
permit PermitId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicRemote permit
|
|
|
|
|
|
|
|
|
|
------------------------------- Permit reason --------------------------------
|
|
|
|
|
|
|
|
|
|
PermitFulfillsTopicCreation
|
|
|
|
|
permit PermitId
|
|
|
|
|
|
|
|
|
|
UniquePermitFulfillsTopicCreation permit
|
|
|
|
|
|
2024-08-06 11:33:02 +02:00
|
|
|
PermitFulfillsResidentFactory
|
|
|
|
|
permit PermitId
|
|
|
|
|
|
|
|
|
|
UniquePermitFulfillsResidentFactory permit
|
|
|
|
|
|
2023-11-22 17:11:07 +01:00
|
|
|
PermitFulfillsInvite
|
|
|
|
|
permit PermitId
|
|
|
|
|
|
|
|
|
|
UniquePermitFulfillsInvite permit
|
|
|
|
|
|
|
|
|
|
PermitFulfillsJoin
|
|
|
|
|
permit PermitId
|
|
|
|
|
|
|
|
|
|
UniquePermitFulfillsJoin permit
|
|
|
|
|
|
|
|
|
|
-- Person's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Join: Witnesses the initial Join that started the sequence
|
|
|
|
|
-- Invite: Witnesses their approval, seeing the topic's accept, and then
|
|
|
|
|
-- sending their own accept
|
|
|
|
|
-- Create: Records the Create activity that created the topic
|
2024-08-06 11:33:02 +02:00
|
|
|
-- Factory: Records the self-Create the Person published
|
2023-11-22 17:11:07 +01:00
|
|
|
|
|
|
|
|
PermitPersonGesture
|
|
|
|
|
permit PermitId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniquePermitPersonGesture permit
|
|
|
|
|
UniquePermitPersonGestureActivity activity
|
|
|
|
|
|
|
|
|
|
-- Topic collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Join: N/A (it happens but we don't record it)
|
|
|
|
|
-- Invite: Witnesses the initial Invite that started the sequence
|
|
|
|
|
|
|
|
|
|
PermitTopicGestureLocal
|
|
|
|
|
fulfills PermitFulfillsInviteId
|
|
|
|
|
invite OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicGestureLocal fulfills
|
|
|
|
|
UniquePermitTopicGestureLocalInvite invite
|
|
|
|
|
|
|
|
|
|
PermitTopicGestureRemote
|
|
|
|
|
fulfills PermitFulfillsInviteId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
invite RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicGestureRemote fulfills
|
|
|
|
|
UniquePermitTopicGestureRemoteInvite invite
|
|
|
|
|
|
|
|
|
|
-- Topic's accept
|
|
|
|
|
--
|
|
|
|
|
-- Join: N/A
|
|
|
|
|
-- Invite: Witnesses that the topic saw and approved the Invite
|
|
|
|
|
|
|
|
|
|
PermitTopicAcceptLocal
|
|
|
|
|
fulfills PermitFulfillsInviteId
|
|
|
|
|
topic PermitTopicLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicAcceptLocal fulfills
|
|
|
|
|
UniquePermitTopicAcceptLocalTopic topic
|
|
|
|
|
UniquePermitTopicAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
PermitTopicAcceptRemote
|
|
|
|
|
fulfills PermitFulfillsInviteId
|
|
|
|
|
topic PermitTopicRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicAcceptRemote fulfills
|
|
|
|
|
UniquePermitTopicAcceptRemoteTopic topic
|
|
|
|
|
UniquePermitTopicAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
-------------------------------- Permit enable -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Topic's grant
|
|
|
|
|
--
|
|
|
|
|
-- Join: Seeing the new-collaborator's Join and existing-collaborator's Accept,
|
|
|
|
|
-- the topic has made the link official and sent a direct-grant
|
|
|
|
|
-- Invite: Seeing existing-collaborator's Invite and new-collaborator's Accept,
|
|
|
|
|
-- the topic has made the link official and sent a direct-grant
|
|
|
|
|
-- Create: Upon being created, topic has sent its creator an admin-Grant
|
2024-08-06 11:33:02 +02:00
|
|
|
-- Factory: A factory that became active sent me a Grant (usually because I've
|
|
|
|
|
-- just created a new account)
|
2023-11-22 17:11:07 +01:00
|
|
|
|
|
|
|
|
PermitTopicEnableLocal
|
|
|
|
|
permit PermitPersonGestureId
|
|
|
|
|
topic PermitTopicLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicEnableLocal permit
|
|
|
|
|
UniquePermitTopicEnableLocalTopic topic
|
|
|
|
|
UniquePermitTopicEnableLocalGrant grant
|
|
|
|
|
|
|
|
|
|
PermitTopicEnableRemote
|
|
|
|
|
permit PermitPersonGestureId
|
|
|
|
|
topic PermitTopicRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicEnableRemote permit
|
|
|
|
|
UniquePermitTopicEnableRemoteTopic topic
|
|
|
|
|
UniquePermitTopicEnableRemoteGrant grant
|
|
|
|
|
|
|
|
|
|
----------------------- Permit delegator+extension ---------------------------
|
|
|
|
|
|
|
|
|
|
-- This section is only for Project or Team topics
|
|
|
|
|
-- Person sends delegator-Grant, topic starts sending extension-Grants
|
|
|
|
|
|
|
|
|
|
-- Witnesses that the person used the direct-Grant to send a delegator-Grant to
|
|
|
|
|
-- the topic
|
|
|
|
|
PermitPersonSendDelegator
|
|
|
|
|
permit PermitPersonGestureId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniquePermitPersonSendDelegator permit
|
|
|
|
|
UniquePermitPersonSendDelegatorGrant grant
|
|
|
|
|
|
|
|
|
|
-- Witnesses extension-Grants that the topic has sent, extending chains from
|
|
|
|
|
-- its components/subprojects or projects/superteams
|
|
|
|
|
|
2024-04-19 01:30:33 +02:00
|
|
|
PermitTopicExtend
|
2023-11-22 17:11:07 +01:00
|
|
|
permit PermitPersonSendDelegatorId
|
2024-04-19 01:30:33 +02:00
|
|
|
role Role
|
|
|
|
|
|
|
|
|
|
PermitTopicExtendLocal
|
|
|
|
|
permit PermitTopicExtendId
|
2023-11-22 17:11:07 +01:00
|
|
|
topic PermitTopicEnableLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
2024-04-19 01:30:33 +02:00
|
|
|
UniquePermitTopicExtendLocal permit
|
2023-11-22 17:11:07 +01:00
|
|
|
UniquePermitTopicExtendLocalGrant grant
|
|
|
|
|
|
|
|
|
|
PermitTopicExtendRemote
|
2024-04-19 01:30:33 +02:00
|
|
|
permit PermitTopicExtendId
|
2023-11-22 17:11:07 +01:00
|
|
|
topic PermitTopicEnableRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
2024-04-19 01:30:33 +02:00
|
|
|
UniquePermitTopicExtendRemote permit
|
2023-11-22 17:11:07 +01:00
|
|
|
UniquePermitTopicExtendRemoteGrant grant
|
|
|
|
|
|
2024-04-19 01:30:33 +02:00
|
|
|
PermitTopicExtendResourceLocal
|
2024-04-20 02:52:34 +02:00
|
|
|
permit PermitTopicExtendId
|
2024-04-20 03:15:59 +02:00
|
|
|
resource ResourceId
|
2024-04-19 01:30:33 +02:00
|
|
|
|
|
|
|
|
UniquePermitTopicExtendResourceLocal permit
|
|
|
|
|
|
|
|
|
|
PermitTopicExtendResourceRemote
|
|
|
|
|
permit PermitTopicExtendId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniquePermitTopicExtendResourceRemote permit
|
|
|
|
|
|
2023-06-27 02:20:30 +02:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Components, from project perspective
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Component
|
|
|
|
|
project ProjectId
|
2023-06-27 21:56:52 +02:00
|
|
|
role Role
|
2023-06-27 02:20:30 +02:00
|
|
|
|
|
|
|
|
------------------------------ Component reason ------------------------------
|
|
|
|
|
|
|
|
|
|
ComponentOriginAdd
|
|
|
|
|
component ComponentId
|
|
|
|
|
|
|
|
|
|
UniqueComponentOriginAdd component
|
|
|
|
|
|
|
|
|
|
ComponentOriginInvite
|
|
|
|
|
component ComponentId
|
|
|
|
|
|
|
|
|
|
UniqueComponentOriginInvite component
|
|
|
|
|
|
|
|
|
|
-- Component collaborators's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Add: Witnesses the initial Add that started the sequence
|
|
|
|
|
-- Invite: N/A (they send their Accept but we don't record it)
|
|
|
|
|
|
|
|
|
|
ComponentGestureLocal
|
|
|
|
|
origin ComponentOriginAddId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentGestureLocal origin
|
|
|
|
|
UniqueComponentGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
ComponentGestureRemote
|
|
|
|
|
origin ComponentOriginAddId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueComponentGestureRemote origin
|
|
|
|
|
UniqueComponentGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Component's accept
|
|
|
|
|
--
|
|
|
|
|
-- Add: Witnesses that the component saw and approved the Add
|
|
|
|
|
-- Invite: Witnesses that the component saw project's accept and component
|
|
|
|
|
-- collaborator's accept, and sent its own accept
|
|
|
|
|
|
|
|
|
|
ComponentAcceptLocal
|
|
|
|
|
ident ComponentLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentAcceptLocal ident
|
|
|
|
|
UniqueComponentAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
ComponentAcceptRemote
|
|
|
|
|
ident ComponentRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueComponentAcceptRemote ident
|
|
|
|
|
UniqueComponentAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
-- Project collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Add: Witnesses their approval, seeing the component's accept
|
|
|
|
|
-- Invite: Witnesses the initial Invite that started the sequence
|
|
|
|
|
|
|
|
|
|
ComponentProjectGestureLocal
|
|
|
|
|
component ComponentId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentProjectGestureLocal component
|
|
|
|
|
UniqueComponentProjectGestureLocalActivity activity
|
|
|
|
|
|
|
|
|
|
ComponentProjectGestureRemote
|
|
|
|
|
component ComponentId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueComponentProjectGestureRemote component
|
|
|
|
|
UniqueComponentProjectGestureRemoteActivity activity
|
|
|
|
|
|
|
|
|
|
-- Project's accept
|
|
|
|
|
--
|
|
|
|
|
-- Add: N/A
|
|
|
|
|
-- Invite: Witnesses that the project saw and approved the Invite
|
|
|
|
|
|
|
|
|
|
ComponentProjectAccept
|
|
|
|
|
origin ComponentOriginInviteId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentProjectAccept origin
|
|
|
|
|
UniqueComponentProjectAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
----------------------------- Component identity -----------------------------
|
|
|
|
|
|
|
|
|
|
ComponentLocal
|
|
|
|
|
component ComponentId
|
2024-04-29 22:23:59 +02:00
|
|
|
actor KomponentId
|
2023-06-27 02:20:30 +02:00
|
|
|
|
|
|
|
|
UniqueComponentLocal component
|
|
|
|
|
|
|
|
|
|
ComponentRemote
|
|
|
|
|
component ComponentId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueComponentRemote component
|
|
|
|
|
|
|
|
|
|
------------------------------ Component enable ------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing the project collaborator approval on the Add or the
|
|
|
|
|
-- component approval on the Invite, the project has sent the component a Grant
|
|
|
|
|
-- with the "delegator" role and now officially considering it a component of
|
|
|
|
|
-- the project
|
|
|
|
|
ComponentEnable
|
|
|
|
|
component ComponentId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentEnable component
|
|
|
|
|
UniqueComponentEnableGrant grant
|
|
|
|
|
|
2024-05-27 23:03:47 +02:00
|
|
|
-- Witnesses that the component used the delegator Grant to send a start-Grant
|
|
|
|
|
-- to the project, to extend further
|
2024-03-13 14:36:50 +01:00
|
|
|
|
2023-06-27 02:20:30 +02:00
|
|
|
ComponentDelegateLocal
|
|
|
|
|
component ComponentLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentDelegateLocal component
|
|
|
|
|
UniqueComponentDelegateLocalGrant grant
|
|
|
|
|
|
|
|
|
|
ComponentDelegateRemote
|
|
|
|
|
component ComponentRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueComponentDelegateRemote component
|
|
|
|
|
UniqueComponentDelegateRemoteGrant grant
|
|
|
|
|
|
2024-05-27 23:03:47 +02:00
|
|
|
-- Witnesses that the project has extended the start-Grant to a given
|
2023-06-27 02:20:30 +02:00
|
|
|
-- direct collaborator
|
2024-03-13 14:36:50 +01:00
|
|
|
|
2023-06-27 02:20:30 +02:00
|
|
|
ComponentFurtherLocal
|
|
|
|
|
component ComponentEnableId
|
S2S: Project: Send ext-Grants to new collab upon getting their delegator-Grant
Until now, adding a direct collaborator to a Project worked exactly like
with components: Invite or Join, then Accept, finally the direct-Grant.
I missed the fact that much like with project-component relationships,
projects (and teams) need to be able to send extension-Grants to their
direct collaborators.
So in Project's Grant handler it now:
- Recognizes the delegator-Grant coming from a new collaborator
- Sends extension-Grants, using the delegator-Grant as the capability
- When getting a new component and sending extension-Grants for it to
direct collaborators, Project uses their delegator-Grants as
capability
And in Project's Accept handler, it no longer sends extension-Grants
(because it doesn't yet have the collaborator's delegator-Grant at this
point).
NOTE, THIS TEMPORARILY BREAKS grant chains: If you create a Project and
add a Deck to it, you won't get an extension-Grant-for-the-Deck from the
Project, because the Project doesn't yet have your delegator-Grant.
The next commits will implement the Person-side of Collab records, and
will cause Person actors to automatically send the delegator-Grant,
fixing the break.
2023-11-22 13:16:08 +01:00
|
|
|
collab CollabDelegLocalId
|
2023-06-27 02:20:30 +02:00
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentFurtherLocal component collab
|
|
|
|
|
UniqueComponentFurtherLocalGrant grant
|
|
|
|
|
|
|
|
|
|
ComponentFurtherRemote
|
|
|
|
|
component ComponentEnableId
|
S2S: Project: Send ext-Grants to new collab upon getting their delegator-Grant
Until now, adding a direct collaborator to a Project worked exactly like
with components: Invite or Join, then Accept, finally the direct-Grant.
I missed the fact that much like with project-component relationships,
projects (and teams) need to be able to send extension-Grants to their
direct collaborators.
So in Project's Grant handler it now:
- Recognizes the delegator-Grant coming from a new collaborator
- Sends extension-Grants, using the delegator-Grant as the capability
- When getting a new component and sending extension-Grants for it to
direct collaborators, Project uses their delegator-Grants as
capability
And in Project's Accept handler, it no longer sends extension-Grants
(because it doesn't yet have the collaborator's delegator-Grant at this
point).
NOTE, THIS TEMPORARILY BREAKS grant chains: If you create a Project and
add a Deck to it, you won't get an extension-Grant-for-the-Deck from the
Project, because the Project doesn't yet have your delegator-Grant.
The next commits will implement the Person-side of Collab records, and
will cause Person actors to automatically send the delegator-Grant,
fixing the break.
2023-11-22 13:16:08 +01:00
|
|
|
collab CollabDelegRemoteId
|
2023-06-27 02:20:30 +02:00
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentFurtherRemote component collab
|
|
|
|
|
UniqueComponentFurtherRemoteGrant grant
|
|
|
|
|
|
2024-05-27 23:03:47 +02:00
|
|
|
-- Witnesses that the project has extended the start-Grant to a given
|
2024-03-13 14:36:50 +01:00
|
|
|
-- parent
|
|
|
|
|
|
2024-04-14 14:21:56 +02:00
|
|
|
ComponentGather
|
2024-03-13 14:36:50 +01:00
|
|
|
component ComponentEnableId
|
2024-04-14 14:21:56 +02:00
|
|
|
parent DestUsStartId
|
2024-03-13 14:36:50 +01:00
|
|
|
grant OutboxItemId
|
|
|
|
|
|
2024-04-14 14:21:56 +02:00
|
|
|
UniqueComponentGather component parent
|
|
|
|
|
UniqueComponentGatherGrant grant
|
2024-03-13 14:36:50 +01:00
|
|
|
|
2024-05-27 23:03:47 +02:00
|
|
|
-- Witnesses that the project has extended the start-Grant to a given team
|
2024-05-14 22:14:12 +02:00
|
|
|
|
|
|
|
|
ComponentConvey
|
|
|
|
|
component ComponentEnableId
|
|
|
|
|
team SquadUsStartId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueComponentConvey component team
|
|
|
|
|
UniqueComponentConveyGrant grant
|
|
|
|
|
|
2023-06-27 02:20:30 +02:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Components, from component perspective
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Stem
|
2024-04-29 23:32:30 +02:00
|
|
|
role Role
|
|
|
|
|
holder KomponentId
|
2023-06-27 02:20:30 +02:00
|
|
|
|
|
|
|
|
-------------------------------- Stem project --------------------------------
|
|
|
|
|
|
|
|
|
|
StemProjectLocal
|
|
|
|
|
stem StemId
|
|
|
|
|
project ProjectId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectLocal stem
|
|
|
|
|
|
|
|
|
|
StemProjectRemote
|
|
|
|
|
stem StemId
|
|
|
|
|
project RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectRemote stem
|
|
|
|
|
|
|
|
|
|
--------------------------------- Stem reason --------------------------------
|
|
|
|
|
|
|
|
|
|
StemOriginAdd
|
|
|
|
|
stem StemId
|
|
|
|
|
|
|
|
|
|
UniqueStemOriginAdd stem
|
|
|
|
|
|
|
|
|
|
StemOriginInvite
|
|
|
|
|
stem StemId
|
|
|
|
|
|
|
|
|
|
UniqueStemOriginInvite stem
|
|
|
|
|
|
|
|
|
|
-- Component collaborators's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Add: Witnesses the initial Add that started the sequence
|
|
|
|
|
-- Invite: Witnesses their approval, seeing the project's accept
|
|
|
|
|
|
|
|
|
|
StemComponentGestureLocal
|
|
|
|
|
stem StemId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemComponentGestureLocal stem
|
|
|
|
|
UniqueStemComponentGestureLocalActivity activity
|
|
|
|
|
|
|
|
|
|
StemComponentGestureRemote
|
|
|
|
|
stem StemId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueStemComponentGestureRemote stem
|
|
|
|
|
UniqueStemComponentGestureRemoteActivity activity
|
|
|
|
|
|
|
|
|
|
-- Component's accept
|
|
|
|
|
--
|
|
|
|
|
-- Add: Witnesses that the component saw and approved the initial Add
|
|
|
|
|
-- Invite: Witnesses that the component saw project's accept and component
|
|
|
|
|
-- collaborator's accept, and sent its own accept
|
|
|
|
|
|
|
|
|
|
StemComponentAccept
|
|
|
|
|
stem StemId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemComponentAccept stem
|
|
|
|
|
UniqueStemComponentAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
-- Project collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- Add: N/A (it happens but we don't record it)
|
|
|
|
|
-- Invite: Witnesses the initial Invite that started the sequence
|
|
|
|
|
|
|
|
|
|
StemProjectGestureLocal
|
|
|
|
|
origin StemOriginInviteId
|
|
|
|
|
invite OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectGestureLocal origin
|
|
|
|
|
UniqueStemProjectGestureLocalInvite invite
|
|
|
|
|
|
|
|
|
|
StemProjectGestureRemote
|
|
|
|
|
origin StemOriginInviteId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
invite RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectGestureRemote origin
|
|
|
|
|
UniqueStemProjectGestureRemoteInvite invite
|
|
|
|
|
|
|
|
|
|
-- Project's accept
|
|
|
|
|
--
|
|
|
|
|
-- Add: N/A
|
|
|
|
|
-- Invite: Witnesses that the project saw and approved the Invite
|
|
|
|
|
|
|
|
|
|
StemProjectAcceptLocal
|
|
|
|
|
origin StemOriginInviteId
|
|
|
|
|
project StemProjectLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectAcceptLocal origin
|
|
|
|
|
UniqueStemProjectAcceptLocalProject project
|
|
|
|
|
UniqueStemProjectAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
StemProjectAcceptRemote
|
|
|
|
|
origin StemOriginInviteId
|
|
|
|
|
project StemProjectRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectAcceptRemote origin
|
|
|
|
|
UniqueStemProjectAcceptRemoteProject project
|
|
|
|
|
UniqueStemProjectAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
------------------------------ Stem enable ------------------------------
|
|
|
|
|
|
|
|
|
|
-- Project's grant
|
|
|
|
|
--
|
|
|
|
|
-- Add: Seeing component's accept and project collaborator's accept, the
|
|
|
|
|
-- project has made the link official and sent a delegator grant
|
|
|
|
|
-- Invite: Seeing project collaborator's Invite and component's accept, the
|
|
|
|
|
-- project has made the link official and sent a delegator grant
|
|
|
|
|
|
|
|
|
|
StemProjectGrantLocal
|
|
|
|
|
stem StemComponentAcceptId
|
|
|
|
|
project StemProjectLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectGrantLocal stem
|
|
|
|
|
UniqueStemProjectGrantLocalProject project
|
|
|
|
|
UniqueStemProjectGrantLocalGrant grant
|
|
|
|
|
|
|
|
|
|
StemProjectGrantRemote
|
|
|
|
|
stem StemComponentAcceptId
|
|
|
|
|
project StemProjectRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueStemProjectGrantRemote stem
|
|
|
|
|
UniqueStemProjectGrantRemoteProject project
|
|
|
|
|
UniqueStemProjectGrantRemoteGrant grant
|
|
|
|
|
|
|
|
|
|
-- Witnesses that the stem used the delegator Grant to send an admin
|
|
|
|
|
-- delegation to the project, to extend the delegation further
|
|
|
|
|
StemDelegateLocal
|
|
|
|
|
stem StemComponentAcceptId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueStemDelegateLocal stem
|
|
|
|
|
UniqueStemDelegateLocalGrant grant
|
2023-12-11 17:49:42 +01:00
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Inheritance - Receiver tracking her givers
|
|
|
|
|
-- (Project tracking its children)
|
|
|
|
|
-- (Team tracking its parents)
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Source
|
|
|
|
|
role Role
|
|
|
|
|
|
|
|
|
|
SourceHolderProject
|
|
|
|
|
source SourceId
|
|
|
|
|
project ProjectId
|
|
|
|
|
|
|
|
|
|
UniqueSourceHolderProject source
|
|
|
|
|
|
|
|
|
|
SourceHolderGroup
|
|
|
|
|
source SourceId
|
|
|
|
|
group GroupId
|
|
|
|
|
|
|
|
|
|
UniqueSourceHolderGroup source
|
|
|
|
|
|
|
|
|
|
-------------------------------- Source topic --------------------------------
|
|
|
|
|
|
|
|
|
|
SourceTopicLocal
|
|
|
|
|
source SourceId
|
|
|
|
|
|
|
|
|
|
UniqueSourceTopicLocal source
|
|
|
|
|
|
|
|
|
|
SourceTopicProject
|
|
|
|
|
holder SourceHolderProjectId
|
|
|
|
|
topic SourceTopicLocalId
|
|
|
|
|
child ProjectId
|
|
|
|
|
|
|
|
|
|
UniqueSourceTopicProject holder
|
|
|
|
|
UniqueSourceTopicProjectTopic topic
|
|
|
|
|
|
|
|
|
|
SourceTopicGroup
|
|
|
|
|
holder SourceHolderGroupId
|
|
|
|
|
topic SourceTopicLocalId
|
|
|
|
|
parent GroupId
|
|
|
|
|
|
|
|
|
|
UniqueSourceTopicGroup holder
|
|
|
|
|
UniqueSourceTopicGroupTopic topic
|
|
|
|
|
|
|
|
|
|
SourceTopicRemote
|
|
|
|
|
source SourceId
|
|
|
|
|
topic RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueSourceTopicRemote source
|
|
|
|
|
|
|
|
|
|
-------------------------------- Source flow ---------------------------------
|
|
|
|
|
|
|
|
|
|
SourceOriginUs
|
|
|
|
|
source SourceId
|
|
|
|
|
|
|
|
|
|
UniqueSourceOriginUs source
|
|
|
|
|
|
|
|
|
|
SourceOriginThem
|
|
|
|
|
source SourceId
|
|
|
|
|
|
|
|
|
|
UniqueSourceOriginThem source
|
|
|
|
|
|
|
|
|
|
-- Our collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: The Add that started the sequence
|
|
|
|
|
-- OriginThem: N/A (they send their Accept but we don't record it)
|
|
|
|
|
|
|
|
|
|
SourceUsGestureLocal
|
|
|
|
|
us SourceOriginUsId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsGestureLocal us
|
|
|
|
|
UniqueSourceUsGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
SourceUsGestureRemote
|
|
|
|
|
us SourceOriginUsId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsGestureRemote us
|
|
|
|
|
UniqueSourceUsGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Our accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: I checked the Add and sending my Accept
|
|
|
|
|
-- OriginThem: N/A
|
|
|
|
|
|
|
|
|
|
SourceUsAccept
|
|
|
|
|
us SourceOriginUsId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsAccept us
|
|
|
|
|
UniqueSourceUsAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
-- Their collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A (they send it but we don't record it)
|
|
|
|
|
-- OriginThem: The Add that started the sequence
|
|
|
|
|
|
|
|
|
|
SourceThemGestureLocal
|
|
|
|
|
them SourceOriginThemId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceThemGestureLocal them
|
|
|
|
|
UniqueSourceThemGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
SourceThemGestureRemote
|
|
|
|
|
them SourceOriginThemId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSourceThemGestureRemote them
|
|
|
|
|
UniqueSourceThemGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Their accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: Seeing our accept and their collaborator's accept, they send their
|
|
|
|
|
-- own accept
|
|
|
|
|
-- OriginThem: Checking the Add, they send their Accept
|
|
|
|
|
|
|
|
|
|
SourceThemAcceptLocal
|
|
|
|
|
topic SourceTopicLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceThemAcceptLocal topic
|
|
|
|
|
UniqueSourceThemAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
SourceThemAcceptRemote
|
|
|
|
|
topic SourceTopicRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSourceThemAcceptRemote topic
|
|
|
|
|
UniqueSourceThemAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
-------------------------------- Source enable -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing their approval and our collaborator's gesture, I've
|
2023-12-12 22:21:06 +01:00
|
|
|
-- sent them a delegator-Grant and now officially considering them a source of
|
2023-12-11 17:49:42 +01:00
|
|
|
-- us
|
|
|
|
|
SourceUsSendDelegator
|
|
|
|
|
source SourceId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsSendDelegator source
|
|
|
|
|
UniqueSourceUsSendDelegatorGrant grant
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, using the delegator-Grant, they sent us a start-Grant or
|
|
|
|
|
-- extension-Grant to delegate further
|
|
|
|
|
|
|
|
|
|
SourceThemDelegateLocal
|
|
|
|
|
source SourceThemAcceptLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
2024-04-10 15:27:29 +02:00
|
|
|
UniqueSourceThemDelegateLocal grant
|
2023-12-11 17:49:42 +01:00
|
|
|
|
|
|
|
|
SourceThemDelegateRemote
|
|
|
|
|
source SourceThemAcceptRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
2024-04-10 15:27:29 +02:00
|
|
|
UniqueSourceThemDelegateRemote grant
|
2023-12-11 17:49:42 +01:00
|
|
|
|
|
|
|
|
-- Witnesses that, seeing the delegation from them, I've sent an
|
|
|
|
|
-- extension-Grant to a Dest of mine
|
|
|
|
|
|
2024-03-11 11:50:15 +01:00
|
|
|
SourceUsGather
|
|
|
|
|
source SourceUsSendDelegatorId
|
2024-04-14 14:06:50 +02:00
|
|
|
dest DestUsStartId
|
2024-03-11 11:50:15 +01:00
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
SourceUsGatherFromLocal
|
|
|
|
|
gather SourceUsGatherId
|
|
|
|
|
from SourceThemDelegateLocalId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsGatherFromLocal gather
|
|
|
|
|
|
|
|
|
|
SourceUsGatherFromRemote
|
|
|
|
|
gather SourceUsGatherId
|
|
|
|
|
from SourceThemDelegateRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsGatherFromRemote gather
|
|
|
|
|
|
2023-12-11 17:49:42 +01:00
|
|
|
-- Witnesses that, seeing the delegation from them, I've sent a leaf-Grant to a
|
|
|
|
|
-- direct-collaborator of mine
|
|
|
|
|
|
2024-03-11 11:50:15 +01:00
|
|
|
SourceUsLeaf
|
|
|
|
|
source SourceUsSendDelegatorId
|
|
|
|
|
collab CollabEnableId
|
2023-12-11 17:49:42 +01:00
|
|
|
grant OutboxItemId
|
|
|
|
|
|
2024-03-11 11:50:15 +01:00
|
|
|
SourceUsLeafFromLocal
|
|
|
|
|
leaf SourceUsLeafId
|
|
|
|
|
from SourceThemDelegateLocalId
|
2023-12-11 17:49:42 +01:00
|
|
|
|
2024-03-11 11:50:15 +01:00
|
|
|
UniqueSourceUsLeafFromLocal leaf
|
|
|
|
|
|
|
|
|
|
SourceUsLeafFromRemote
|
|
|
|
|
leaf SourceUsLeafId
|
|
|
|
|
from SourceThemDelegateRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsLeafFromRemote leaf
|
|
|
|
|
|
|
|
|
|
SourceUsLeafToLocal
|
|
|
|
|
leaf SourceUsLeafId
|
|
|
|
|
to CollabDelegLocalId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsLeafToLocal leaf
|
|
|
|
|
|
|
|
|
|
SourceUsLeafToRemote
|
|
|
|
|
leaf SourceUsLeafId
|
|
|
|
|
to CollabDelegRemoteId
|
2023-12-11 17:49:42 +01:00
|
|
|
|
2024-03-11 11:50:15 +01:00
|
|
|
UniqueSourceUsLeafToRemote leaf
|
2023-12-11 17:49:42 +01:00
|
|
|
|
2024-05-14 22:14:12 +02:00
|
|
|
-- Witnesses that, seeing the delegation from them, I've sent an
|
|
|
|
|
-- extension-Grant to a team-collaborator of mine
|
|
|
|
|
|
|
|
|
|
SourceUsConvey
|
|
|
|
|
source SourceUsSendDelegatorId
|
|
|
|
|
team SquadUsStartId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
SourceUsConveyFromLocal
|
|
|
|
|
convey SourceUsConveyId
|
|
|
|
|
from SourceThemDelegateLocalId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsConveyFromLocal convey
|
|
|
|
|
|
|
|
|
|
SourceUsConveyFromRemote
|
|
|
|
|
convey SourceUsConveyId
|
|
|
|
|
from SourceThemDelegateRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueSourceUsConveyFromRemote convey
|
|
|
|
|
|
2024-04-04 10:54:13 +02:00
|
|
|
-------------------------------- Source remove -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses there's a removal request from the child's side, and I'm waiting
|
|
|
|
|
-- for the child project/team to Accept, which is when I'll do the removal on
|
|
|
|
|
-- my side
|
|
|
|
|
|
|
|
|
|
SourceRemove
|
|
|
|
|
send SourceUsSendDelegatorId
|
|
|
|
|
activity InboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSourceRemove activity
|
|
|
|
|
|
2023-12-11 17:49:42 +01:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Inheritance - Giver tracking her receivers
|
|
|
|
|
-- (Project tracking its parents)
|
|
|
|
|
-- (Team tracking its children)
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Dest
|
|
|
|
|
role Role
|
|
|
|
|
|
|
|
|
|
DestHolderProject
|
|
|
|
|
dest DestId
|
|
|
|
|
project ProjectId
|
|
|
|
|
|
|
|
|
|
UniqueDestHolderProject dest
|
|
|
|
|
|
|
|
|
|
DestHolderGroup
|
|
|
|
|
dest DestId
|
|
|
|
|
group GroupId
|
|
|
|
|
|
|
|
|
|
UniqueDestHolderGroup dest
|
|
|
|
|
|
|
|
|
|
---------------------------------- Dest topic --------------------------------
|
|
|
|
|
|
|
|
|
|
DestTopicLocal
|
|
|
|
|
dest DestId
|
|
|
|
|
|
|
|
|
|
UniqueDestTopicLocal dest
|
|
|
|
|
|
|
|
|
|
DestTopicProject
|
|
|
|
|
holder DestHolderProjectId
|
|
|
|
|
topic DestTopicLocalId
|
|
|
|
|
parent ProjectId
|
|
|
|
|
|
|
|
|
|
UniqueDestTopicProject holder
|
|
|
|
|
UniqueDestTopicProjectTopic topic
|
|
|
|
|
|
|
|
|
|
DestTopicGroup
|
|
|
|
|
holder DestHolderGroupId
|
|
|
|
|
topic DestTopicLocalId
|
|
|
|
|
child GroupId
|
|
|
|
|
|
|
|
|
|
UniqueDestTopicGroup holder
|
|
|
|
|
UniqueDestTopicGroupTopic topic
|
|
|
|
|
|
|
|
|
|
DestTopicRemote
|
|
|
|
|
dest DestId
|
|
|
|
|
topic RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueDestTopicRemote dest
|
|
|
|
|
|
|
|
|
|
---------------------------------- Dest flow ---------------------------------
|
|
|
|
|
|
|
|
|
|
DestOriginUs
|
|
|
|
|
dest DestId
|
|
|
|
|
|
|
|
|
|
UniqueDestOriginUs dest
|
|
|
|
|
|
|
|
|
|
DestOriginThem
|
|
|
|
|
dest DestId
|
|
|
|
|
|
|
|
|
|
UniqueDestOriginThem dest
|
|
|
|
|
|
|
|
|
|
-- Our collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: The Add that started the sequence
|
|
|
|
|
-- OriginThem: Seeing the Add and their Accept, my collaborator has sent her
|
|
|
|
|
-- Accept
|
|
|
|
|
|
|
|
|
|
DestUsGestureLocal
|
|
|
|
|
dest DestId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestUsGestureLocal dest
|
|
|
|
|
UniqueDestUsGestureLocalActivity activity
|
|
|
|
|
|
|
|
|
|
DestUsGestureRemote
|
|
|
|
|
dest DestId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueDestUsGestureRemote dest
|
|
|
|
|
UniqueDestUsGestureRemoteActivity activity
|
|
|
|
|
|
|
|
|
|
-- Our accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: Checking my collaborator's Add, I sent my Accept
|
|
|
|
|
-- OriginThem: Seeing the Add, their Accept and my collaborator's Accept, I
|
|
|
|
|
-- sent my Accept
|
|
|
|
|
|
|
|
|
|
DestUsAccept
|
|
|
|
|
dest DestId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestUsAccept dest
|
|
|
|
|
UniqueDestUsAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
-- Their collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A (they send it but we don't record it)
|
|
|
|
|
-- OriginThem: The Add that started the sequence
|
|
|
|
|
|
|
|
|
|
DestThemGestureLocal
|
|
|
|
|
them DestOriginThemId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemGestureLocal them
|
|
|
|
|
UniqueDestThemGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
DestThemGestureRemote
|
|
|
|
|
them DestOriginThemId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemGestureRemote them
|
|
|
|
|
UniqueDestThemGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Their accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A
|
|
|
|
|
-- OriginThem: Seeing their collaborator's Add, they sent an Accept
|
|
|
|
|
|
|
|
|
|
DestThemAcceptLocal
|
|
|
|
|
them DestOriginThemId
|
|
|
|
|
topic DestTopicLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemAcceptLocal them
|
|
|
|
|
UniqueDestThemAcceptLocalTopic topic
|
|
|
|
|
UniqueDestThemAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
DestThemAcceptRemote
|
|
|
|
|
them DestOriginThemId
|
|
|
|
|
topic DestTopicRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemAcceptRemote them
|
|
|
|
|
UniqueDestThemAcceptRemoteTopic topic
|
|
|
|
|
UniqueDestThemAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
---------------------------------- Dest enable -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing our approval and their collaborator's gesture,
|
|
|
|
|
-- they've sent us a delegator-Grant, and we now officially consider them a
|
|
|
|
|
-- dest of us
|
|
|
|
|
|
|
|
|
|
DestThemSendDelegatorLocal
|
|
|
|
|
dest DestUsAcceptId
|
|
|
|
|
topic DestTopicLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemSendDelegatorLocal dest
|
|
|
|
|
UniqueDestThemSendDelegatorLocalTopic topic
|
|
|
|
|
UniqueDestThemSendDelegatorLocalGrant grant
|
|
|
|
|
|
|
|
|
|
DestThemSendDelegatorRemote
|
|
|
|
|
dest DestUsAcceptId
|
|
|
|
|
topic DestTopicRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueDestThemSendDelegatorRemote dest
|
|
|
|
|
UniqueDestThemSendDelegatorRemoteTopic topic
|
|
|
|
|
UniqueDestThemSendDelegatorRemoteGrant grant
|
2024-04-13 15:05:37 +02:00
|
|
|
|
|
|
|
|
-- Witnesses that, seeing the delegator-Grant, I've sent my new parent a
|
|
|
|
|
-- start-Grant to delegate further
|
|
|
|
|
|
|
|
|
|
DestUsStart
|
|
|
|
|
dest DestUsAcceptId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueDestUsStart dest
|
|
|
|
|
UniqueDestUsStartGrant grant
|
2024-05-14 20:29:28 +02:00
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Team tracking its resources (project, repo-deck-loom)
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Effort
|
|
|
|
|
role Role
|
|
|
|
|
holder GroupId
|
|
|
|
|
|
|
|
|
|
-------------------------------- Effort topic --------------------------------
|
|
|
|
|
|
|
|
|
|
EffortTopicLocal
|
|
|
|
|
effort EffortId
|
2024-05-18 12:16:20 +02:00
|
|
|
topic ResourceId
|
2024-05-14 20:29:28 +02:00
|
|
|
|
|
|
|
|
UniqueEffortTopicLocal effort
|
|
|
|
|
|
|
|
|
|
EffortTopicRemote
|
|
|
|
|
effort EffortId
|
|
|
|
|
topic RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueEffortTopicRemote effort
|
|
|
|
|
|
|
|
|
|
-------------------------------- Effort flow ---------------------------------
|
|
|
|
|
|
|
|
|
|
EffortOriginUs
|
|
|
|
|
effort EffortId
|
|
|
|
|
|
|
|
|
|
UniqueEffortOriginUs effort
|
|
|
|
|
|
|
|
|
|
EffortOriginThem
|
|
|
|
|
effort EffortId
|
|
|
|
|
|
|
|
|
|
UniqueEffortOriginThem effort
|
|
|
|
|
|
|
|
|
|
-- Our collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: The Add that started the sequence
|
|
|
|
|
-- OriginThem: N/A (they send their Accept but we don't record it)
|
|
|
|
|
|
|
|
|
|
EffortUsGestureLocal
|
|
|
|
|
us EffortOriginUsId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsGestureLocal us
|
|
|
|
|
UniqueEffortUsGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
EffortUsGestureRemote
|
|
|
|
|
us EffortOriginUsId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsGestureRemote us
|
|
|
|
|
UniqueEffortUsGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Our accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: I checked the Add and sending my Accept
|
|
|
|
|
-- OriginThem: N/A
|
|
|
|
|
|
|
|
|
|
EffortUsAccept
|
|
|
|
|
us EffortOriginUsId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsAccept us
|
|
|
|
|
UniqueEffortUsAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
-- Their collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A (they send it but we don't record it)
|
|
|
|
|
-- OriginThem: The Add that started the sequence
|
|
|
|
|
|
|
|
|
|
EffortThemGestureLocal
|
|
|
|
|
them EffortOriginThemId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemGestureLocal them
|
|
|
|
|
UniqueEffortThemGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
EffortThemGestureRemote
|
|
|
|
|
them EffortOriginThemId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemGestureRemote them
|
|
|
|
|
UniqueEffortThemGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Their accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: Seeing our accept and their collaborator's accept, they send their
|
|
|
|
|
-- own accept
|
|
|
|
|
-- OriginThem: Checking the Add, they send their Accept
|
|
|
|
|
|
|
|
|
|
EffortThemAcceptLocal
|
|
|
|
|
topic EffortTopicLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemAcceptLocal topic
|
|
|
|
|
UniqueEffortThemAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
EffortThemAcceptRemote
|
|
|
|
|
topic EffortTopicRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemAcceptRemote topic
|
|
|
|
|
UniqueEffortThemAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
-------------------------------- Effort enable -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing their approval and our collaborator's gesture, I've
|
|
|
|
|
-- sent them a delegator-Grant and now officially considering them a effort of
|
|
|
|
|
-- us
|
|
|
|
|
EffortUsSendDelegator
|
|
|
|
|
effort EffortId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsSendDelegator effort
|
|
|
|
|
UniqueEffortUsSendDelegatorGrant grant
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, using the delegator-Grant, they sent us a start-Grant or
|
|
|
|
|
-- extension-Grant to delegate further
|
|
|
|
|
|
|
|
|
|
EffortThemDelegateLocal
|
|
|
|
|
effort EffortThemAcceptLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemDelegateLocal grant
|
|
|
|
|
|
|
|
|
|
EffortThemDelegateRemote
|
|
|
|
|
effort EffortThemAcceptRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueEffortThemDelegateRemote grant
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing the delegation from them, I've sent an
|
|
|
|
|
-- extension-Grant to a Dest of mine
|
|
|
|
|
|
|
|
|
|
EffortUsDistribute
|
|
|
|
|
effort EffortUsSendDelegatorId
|
|
|
|
|
dest DestUsStartId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
EffortUsDistributeFromLocal
|
|
|
|
|
distribute EffortUsDistributeId
|
|
|
|
|
from EffortThemDelegateLocalId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsDistributeFromLocal distribute
|
|
|
|
|
|
|
|
|
|
EffortUsDistributeFromRemote
|
|
|
|
|
distribute EffortUsDistributeId
|
|
|
|
|
from EffortThemDelegateRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsDistributeFromRemote distribute
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing the delegation from them, I've sent a leaf-Grant to a
|
|
|
|
|
-- direct-collaborator of mine
|
|
|
|
|
|
|
|
|
|
EffortUsLeaf
|
|
|
|
|
effort EffortUsSendDelegatorId
|
|
|
|
|
collab CollabEnableId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
EffortUsLeafFromLocal
|
|
|
|
|
leaf EffortUsLeafId
|
|
|
|
|
from EffortThemDelegateLocalId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsLeafFromLocal leaf
|
|
|
|
|
|
|
|
|
|
EffortUsLeafFromRemote
|
|
|
|
|
leaf EffortUsLeafId
|
|
|
|
|
from EffortThemDelegateRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsLeafFromRemote leaf
|
|
|
|
|
|
|
|
|
|
EffortUsLeafToLocal
|
|
|
|
|
leaf EffortUsLeafId
|
|
|
|
|
to CollabDelegLocalId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsLeafToLocal leaf
|
|
|
|
|
|
|
|
|
|
EffortUsLeafToRemote
|
|
|
|
|
leaf EffortUsLeafId
|
|
|
|
|
to CollabDelegRemoteId
|
|
|
|
|
|
|
|
|
|
UniqueEffortUsLeafToRemote leaf
|
|
|
|
|
|
|
|
|
|
-------------------------------- Effort remove -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses there's a removal request from the child's side, and I'm waiting
|
|
|
|
|
-- for the child project/team to Accept, which is when I'll do the removal on
|
|
|
|
|
-- my side
|
|
|
|
|
|
|
|
|
|
EffortRemove
|
|
|
|
|
send EffortUsSendDelegatorId
|
|
|
|
|
activity InboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueEffortRemove activity
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
-- Non-team resource tracking its teams
|
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Squad
|
2024-05-15 12:51:09 +02:00
|
|
|
role Role
|
|
|
|
|
holder ResourceId
|
2024-05-14 20:29:28 +02:00
|
|
|
|
|
|
|
|
---------------------------------- Squad topic --------------------------------
|
|
|
|
|
|
|
|
|
|
SquadTopicLocal
|
|
|
|
|
squad SquadId
|
|
|
|
|
group GroupId
|
|
|
|
|
|
|
|
|
|
UniqueSquadTopicLocal squad
|
|
|
|
|
|
|
|
|
|
SquadTopicRemote
|
|
|
|
|
squad SquadId
|
|
|
|
|
topic RemoteActorId
|
|
|
|
|
|
|
|
|
|
UniqueSquadTopicRemote squad
|
|
|
|
|
|
|
|
|
|
---------------------------------- Squad flow ---------------------------------
|
|
|
|
|
|
|
|
|
|
SquadOriginUs
|
|
|
|
|
squad SquadId
|
|
|
|
|
|
|
|
|
|
UniqueSquadOriginUs squad
|
|
|
|
|
|
|
|
|
|
SquadOriginThem
|
|
|
|
|
squad SquadId
|
|
|
|
|
|
|
|
|
|
UniqueSquadOriginThem squad
|
|
|
|
|
|
|
|
|
|
-- Our collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: The Add that started the sequence
|
|
|
|
|
-- OriginThem: Seeing the Add and their Accept, my collaborator has sent her
|
|
|
|
|
-- Accept
|
|
|
|
|
|
|
|
|
|
SquadUsGestureLocal
|
|
|
|
|
squad SquadId
|
|
|
|
|
activity OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadUsGestureLocal squad
|
|
|
|
|
UniqueSquadUsGestureLocalActivity activity
|
|
|
|
|
|
|
|
|
|
SquadUsGestureRemote
|
|
|
|
|
squad SquadId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
activity RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSquadUsGestureRemote squad
|
|
|
|
|
UniqueSquadUsGestureRemoteActivity activity
|
|
|
|
|
|
|
|
|
|
-- Our accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: Checking my collaborator's Add, I sent my Accept
|
|
|
|
|
-- OriginThem: Seeing the Add, their Accept and my collaborator's Accept, I
|
|
|
|
|
-- sent my Accept
|
|
|
|
|
|
|
|
|
|
SquadUsAccept
|
|
|
|
|
squad SquadId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadUsAccept squad
|
|
|
|
|
UniqueSquadUsAcceptAccept accept
|
|
|
|
|
|
|
|
|
|
-- Their collaborator's gesture
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A (they send it but we don't record it)
|
|
|
|
|
-- OriginThem: The Add that started the sequence
|
|
|
|
|
|
|
|
|
|
SquadThemGestureLocal
|
|
|
|
|
them SquadOriginThemId
|
|
|
|
|
add OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemGestureLocal them
|
|
|
|
|
UniqueSquadThemGestureLocalAdd add
|
|
|
|
|
|
|
|
|
|
SquadThemGestureRemote
|
|
|
|
|
them SquadOriginThemId
|
|
|
|
|
actor RemoteActorId
|
|
|
|
|
add RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemGestureRemote them
|
|
|
|
|
UniqueSquadThemGestureRemoteAdd add
|
|
|
|
|
|
|
|
|
|
-- Their accept
|
|
|
|
|
--
|
|
|
|
|
-- OriginUs: N/A
|
|
|
|
|
-- OriginThem: Seeing their collaborator's Add, they sent an Accept
|
|
|
|
|
|
|
|
|
|
SquadThemAcceptLocal
|
|
|
|
|
them SquadOriginThemId
|
|
|
|
|
topic SquadTopicLocalId
|
|
|
|
|
accept OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemAcceptLocal them
|
|
|
|
|
UniqueSquadThemAcceptLocalTopic topic
|
|
|
|
|
UniqueSquadThemAcceptLocalAccept accept
|
|
|
|
|
|
|
|
|
|
SquadThemAcceptRemote
|
|
|
|
|
them SquadOriginThemId
|
|
|
|
|
topic SquadTopicRemoteId
|
|
|
|
|
accept RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemAcceptRemote them
|
|
|
|
|
UniqueSquadThemAcceptRemoteTopic topic
|
|
|
|
|
UniqueSquadThemAcceptRemoteAccept accept
|
|
|
|
|
|
|
|
|
|
---------------------------------- Squad enable -------------------------------
|
|
|
|
|
|
|
|
|
|
-- Witnesses that, seeing our approval and their collaborator's gesture,
|
|
|
|
|
-- they've sent us a delegator-Grant, and we now officially consider them a
|
|
|
|
|
-- squad of us
|
|
|
|
|
|
|
|
|
|
SquadThemSendDelegatorLocal
|
|
|
|
|
squad SquadUsAcceptId
|
|
|
|
|
topic SquadTopicLocalId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemSendDelegatorLocal squad
|
|
|
|
|
UniqueSquadThemSendDelegatorLocalTopic topic
|
|
|
|
|
UniqueSquadThemSendDelegatorLocalGrant grant
|
|
|
|
|
|
|
|
|
|
SquadThemSendDelegatorRemote
|
|
|
|
|
squad SquadUsAcceptId
|
|
|
|
|
topic SquadTopicRemoteId
|
|
|
|
|
grant RemoteActivityId
|
|
|
|
|
|
|
|
|
|
UniqueSquadThemSendDelegatorRemote squad
|
|
|
|
|
UniqueSquadThemSendDelegatorRemoteTopic topic
|
|
|
|
|
UniqueSquadThemSendDelegatorRemoteGrant grant
|
|
|
|
|
|
2024-05-14 22:14:12 +02:00
|
|
|
-- Witnesses that, seeing the delegator-Grant, I've sent my new team a
|
2024-05-14 20:29:28 +02:00
|
|
|
-- start-Grant to delegate further
|
|
|
|
|
|
|
|
|
|
SquadUsStart
|
|
|
|
|
squad SquadUsAcceptId
|
|
|
|
|
grant OutboxItemId
|
|
|
|
|
|
|
|
|
|
UniqueSquadUsStart squad
|
|
|
|
|
UniqueSquadUsStartGrant grant
|
