DOC: update meeting and IRC transcript overview pages

doc/devel/meeting_summary/2011-05-11.txt

@@ -57,7 +57,30 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 
 ''''
 
+++++
+<br/>
+<br/>
+<br/>
+<br/>
+++++
 
+[[irctranscript]]
+IRC Transcript
+--------------
+- xref:scheduler[Engine and Scheduler interface]
+- xref:latency[Latency of GUI reaction]
+- xref:jobproperties[Aborting of Jobs, rescheduling, Job dependencies]
+- xref:resourcecleanup[Ressource handling, Callbacks after Modifications]
+- xref:externalrequirements[Requirements for integration with external libs/services]
+- xref:waitstate[explicit wait state on Jobs?]
+- xref:architecture[Interfaces and components working together?]
+- xref:responsibilities[Responsibilities: who cares for what part]
+- xref:timer[Dedicated Timer facility]
+- xref:guianimation[Animating the GUI during playback]
+- xref:collaborations[Interaction between proc and backend]
+- xref:prerequisites[Handling of prerequisite ressources]
+
+[[scheduler]]
 .-- Engine Interface ⟺ Scheduler Interface --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -102,6 +125,10 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
                                (potentially aborted) jobs
 ----------------------------
 
+
+
+
+[[latency]]
 .-- Latency of GUI reaction --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -133,6 +160,10 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-11 22:29:39] <hermanr> Indeed
 ----------------------------
 
+
+
+
+[[jobproperties]]
 .-- Aborting of Jobs, rescheduling, Job dependencies --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -168,6 +199,10 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-11 22:43:48] <ichthyo> but we can (and need) to 'abort' whole calculation streams
 ----------------------------
 
+
+
+
+[[resourcecleanup]]
 .-- Ressource handling, Callbacks after Modifications --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -238,6 +273,10 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-11 23:09:09] <cehteh> i write some low-level notes for the interface (nothing concrete)
 ----------------------------
 
+
+
+
+[[externalrequirements]]
 .-- one central service ⟺ integrating with external libs/services --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -346,6 +385,9 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-11 23:39:07] <ichthyo> yes, probably better approaching it that way
 ----------------------------
 
+
+
+[[waitstate]]
 .-- explicit wait state on Jobs? --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -388,6 +430,10 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-11 23:55:59] * ichthyo thinks the same
 ----------------------------
 
+
+
+
+[[architecture]]
 .-- Interfaces and components working together --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -437,6 +483,9 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-12 00:19:01] <cehteh> ok
 ----------------------------
 
+
+
+[[responsibilities]]
 .-- Responsibilities: who cares for what part --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -465,7 +514,11 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-12 00:28:50] <ichthyo> ok
 ----------------------------
 
-.-- Dedicated Time facility --
+
+
+
+[[timer]]
+.-- Dedicated Timer facility --
 [caption="☉Transcript☉ "]
 ----------------------------
 [2011-05-12 00:22:48] <cehteh> we once talked about that we want a timer facility (outside of player)
@@ -494,6 +547,9 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-12 00:37:08] <cehteh> (also a reason to make the tinyjobs which are much simpler)
 ----------------------------
 
+
+
+[[guianimation]]
 .-- animating the GUI during playback --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -585,6 +641,9 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-12 01:13:53] <cehteh> yep
 ----------------------------
 
+
+
+[[collaborations]]
 .-- interaction between proc and backend --
 [caption="☉Transcript☉ "]
 ----------------------------
@@ -650,6 +709,9 @@ The next meeting will be as usual, at Wednesday June 8, 20:00 UTC
 [2011-05-12 01:39:41] <ichthyo> especially for those cases, which combine several frames (e.g. time average, motion tracking)
 ----------------------------
 
+
+
+[[prerequisites]]
 .-- handling of prerequisite ressources --
 [caption="☉Transcript☉ "]
 ----------------------------

doc/devel/meeting_summary/2012-10-11.txt

@@ -16,7 +16,7 @@ __Participants__
 Summary of The Meeting 
 ----------------------
 
-. _cehteh_ now Debian package maintainer for NoBug as is  _ichthyo_.
+. _cehteh_ now also cares for Debian packaging of NoBug, as does _ichthyo_.
 . Discussed the naming convention for the Debian package of the Gnome Docking
   Library, (Lumiera have added some features to this library):  libgdlmm-lum
   and libgdlmm-#-dev; where '#' is a number that changes with each change in
@@ -31,5 +31,5 @@ Summary of The Meeting
   _benn_ agreed to write a script that would do the above. The script will be
   called directly by build_website.sh.
 . git://www.lumiera.org/website-staging is for experiments and contained the
-  new Lumiera site (http://staging.lumiera.org/). This was changed to contain
+  new Lumiera site graphics design draft. This was changed to contain
   the contents of the current Lumiera web site.

doc/devel/meeting_summary/index.txt

@@ -12,6 +12,45 @@ Anyone interested in Lumiera development is also encouraged to read mailing list
 archives and other documentation.
 
 
+12 Sep 2012
+-----------
+
+Topics
+~~~~~~
+ * Doxygen
+ * FrOSCon aftermath
+ * Scheduler interface and requirements definition
+
+Summary
+^^^^^^^
+ * link:2013-09-12.html[Summary (by ichthyo)]
+
+
+************************
+Most of our monthly developer meetings are informal discussions currently.
+At times, there is only one developer working at the code, and thus there
+is not much need for coordination. Sometimes, in-depth technical discussions
+and decisions take place, and we'll publish at least an IRC transcript in
+those cases; typically we also create a RfC to summarise the decisions.
+************************
+
+
+11 Oct 2012
+-----------
+
+Topics
+~~~~~~
+ * automatisation of packaging
+ * dealing with GTK-3 and the Gnome Docking Library
+ * builddrone improvements
+ * creating support tools for documentation writing,
+   especially for cross-links and glossary
+
+Summary
+^^^^^^^
+ * link:2012-10-11.html[Summary (by benn)]
+
+
 12 Sep 2012
 -----------
 

doc/devel/template/YYYY-MM-DD-developerMeetingSummary.txt

@@ -17,12 +17,12 @@ _Summary written by XXXXX_
 
 Recurring Topics
 ----------------
-Discussion of open link:/documentation/devel/rfc.html[design process] drafts.
+Discussion of open link:{ldoc}/devel/rfc.html[design process] drafts.
 
 
 Prop1
 ~~~~~
-link:/documentation/devel/rfc_pending/SomeProposal[descriptive name]
+link:{rfc}/SomeProposal[descriptive name]
 Summary what issues are discussed
 ..Details..
 
@@ -50,7 +50,7 @@ Conclusion
 Next meeting
 ------------
 
-The next meeting will be at Wednesday XX XX 20:00 UTC
+The next meeting will be Thursday XX XX 20:00 UTC
 
 
 ''''

doc/devel/transcript/index.txt

@@ -21,4 +21,19 @@ as well as the output process and some generation number. This topic was touched
 in one of our earliest meetings +
 ->link:{ldoc}/devel/meeting_summary/2007-08-10.html[summary]
 
+.shaping the engine interface
+Prompted by a RfC regarding the engine service, this discussion in May 2011 covered
+various aspects of architecture and implementation regarding the engine and especially
+scheduler and render jobs; aborting and superseding of jobs, questions of resource handling,
+waitstates, dedicated time bound operations. +
+->link:{ldoc}/devel/meeting_summary/2011-05-11.html#irctranscript[IRC transcript from 5/2011 dev meeting]
+
+.scheduler requirements
+This discussion in September 2013 touched various requirements for the scheduler
+and the ramifications for a possible implementation. More specifically, from the
+design and implementation for the playback and rendering subsystem done meanwhile
+we can derive some specific requirements to be imposed on the scheduler from the
+client's point of view. +
+->link:{ldoc}/devel/meeting_summary/2013-09-12.html#irctranscript[IRC transcript from 9/2013 dev meeting]
+