From dc143f5c87d172933903150834b033e0b30baeca Mon Sep 17 00:00:00 2001 From: Ichthyostega Date: Fri, 15 Sep 2023 01:58:06 +0200 Subject: [PATCH] DOC: add Benny as author --- doc/devel/meeting_summary/2023-09-13.txt | 36 ++++++++++++++---------- 1 file changed, 21 insertions(+), 15 deletions(-) diff --git a/doc/devel/meeting_summary/2023-09-13.txt b/doc/devel/meeting_summary/2023-09-13.txt index d7c4a3c6b..b5e8e7eb8 100644 --- a/doc/devel/meeting_summary/2023-09-13.txt +++ b/doc/devel/meeting_summary/2023-09-13.txt @@ -1,6 +1,6 @@ 2023-09-13 Lumiera Developers Meeting ===================================== -:Author: Ichthyo +:Author: Ichthyo, Benny :Date: 2023-09-14 Sep 13, 2023 on #lumiera 20:00 - 22:30 UTC + @@ -11,7 +11,7 @@ __Participants__ * benny * cehteh -_Summary written by Ichthyo_ +_Summary written by Ichthyo and reviewed by Benny_ '''' @@ -24,32 +24,36 @@ and extended, and new tickets created, which were all marked with the `FocusTopi -> See https://issues.lumiera.org/report/17[Report-17] in the Lumiera Issue Tracker -_Ichthyo_ identified some difficult issued concerning session modifications and change logging, +_Ichthyo_ identified some difficult issues concerning session modifications and change logging, especially in connection with rules based configuration. We discussed in some detail event sourcing, session modification, session configuration and representation of a configuration possibly as a context in the session. Of particular interest is the portability of a session from one machine to another and, consequently, -the problems that can arise whem a change in configuration occurs: these should be +the problems that can arise when a change in configuration occurs: these should be recorded as an event in the Event-Log. However, this requires the representation of the entire configuration in a consolidated form as part of The Model. A change in the configuration could then be detected and recorded as an event. Another task of concern is how the actual Diff Messages will be generated. We could first manipulate the data model and then _detect_ a diff. Yet the favourable solution would be -to interpret the Commands and directly derive the events associated with the commmanbs, -with an attached diff, which can then be applied against the data model as a projection. +to interpret the commands and directly derive the events associated with the commands, +with an attached diff, which can then be applied against the data model as a _projection._ A discussion followed to sort out which topics should be addressed first. -It seems the topics regarding Event Log and Session persistence #1234 #540 and #569 should -be addressed first, since these may lead to decisions relevant to many other parts of the -system. Possibly also #332 regarding a full definition of placement capabilities. +It seems the topics regarding Event Log and Session persistence +https://issues.lumiera.org/ticket/1234[#1234] +https://issues.lumiera.org/ticket/540[#540] and +https://issues.lumiera.org/ticket/569[#569] +should be addressed first, since these may lead to decisions relevant to many other parts +of the system. Possibly also +https://issues.lumiera.org/ticket/332[#332] regarding a full definition of placement capabilities. -The topic of placement interpretation will be addressed in the *next* vertical slice, +The topic of Placement interpretation will be addressed in the *next* vertical slice, where we intend to add a clip to the timeline. To do this, we'll require at least a -_simple_ resolution capability of placements, because we'll attempt do the groundwork for +_simple_ resolution capability of Placements, because we'll attempt do the groundwork for The Builder. _Benny_ proposes to add »interface« and »mock« tickets for Event-Log and Placements, @@ -75,9 +79,11 @@ Next steps: - complete implementation of the Scheduler Layer-2, integrating Activity-Language and worker pool - integration test of The Scheduler -Documentation Index and Glossary -------------------------------- _Benny_ reworked and -extended the documentation overview in the Lumiera website. This can be published -now. Moreover, _Benny_ investigated Glossary and Index generation. It turns out that +Documentation Index and Glossary +-------------------------------- +_Benny_ reworked and extended the documentation overview in the Lumiera website. +This can be published now. +Moreover, _Benny_ investigated Glossary and Index generation. It turns out that ASCIIDOC already provides an index generation feature, which could be configured and used to build an index. But there is no support to generate a glossary which we'll build soon. The next goal would be to build a prototype for testing and to see how this can be @@ -93,7 +99,7 @@ solution. Moreover, GStreamer seems to have a much more active and helpful commu Next steps would be to look in more depth into libVLC, and especially to compare the feature sets of these solutions. _Cehteh_ points out that MPV (formerly MPlayer) would also be an interesting point of reference. _Benny_ mentions that GTK4 offers an integrated -video display capability. We'll invesigate these frameworks further. +video display capability. We'll investigate these frameworks further. Extended discussion ensued regarding video frameworks and the difficulties regarding the plethora of interfaces, especially when it comes to hardware acceleration support. Ideally, the Lumiera