Commit graph

12 commits

Author SHA1 Message Date
051cb31e28 clean-up: re-classify essential RfCs
The RfC documents were written to complement discussions of the Lumiera developers;
yet since the time where ''Ichthyo'' is working basically alone on the project,
this kind of discussions have ceased. During the following years, some ideas
promoted by the existing RfC documents became rather detached from the
actual state of development in the code base.

Many of the existing RfC documents require some commentary to place them
into context, and some of the decisions taken in the early stage of the
project should be **re-assessed**. This includes the decision to reject
some proposals, which initially might have seemed desirable, yet could not
be reconciled with the understanding of the matter and topic in question,
as was gained through the ongoing analysis and development.
2025-10-08 00:48:13 +02:00
c7528bbe8a clean-up: some RfCs became effectively final
The purpose of RfCs is to channel and document discussions
among a group of developers regarding questions of design.
While there is unfortunately no longer a group of developers
discussing matters and working together on the code base,
some questions can be considered more or less settled,
by being implemented and validated.

- the Scheduler
- structure of the Developer Documentation
- Application installation as relocatable bundle
2025-09-21 05:40:15 +02:00
67695c97b8 clean-up: drop superseded or obsoleted RfCs
See added comments for the reason
2025-09-21 05:40:15 +02:00
23f6f731f1 DOC: update technical docs to reflect recent development
At various places, concepts and drafts from the early stage of the
Lumiera Project are still reflected in the online documentation pages.
During the last months, development focussed on the Render Engine,
causing a shift in some parts of the design, and obsoleting other
parts altogether (notably we consider to use IO_URING for async IO)
2023-10-25 00:02:08 +02:00
4c748c543b Rfc: overrule and push the "Scripting language Lua" back to draft.
During the last years, I became more and more doubtful and regretted
that decision. In hindsight, the fundamental conflict was present
already in the original discussion.

My own experience showed me again and again: skipping the hard work
of specification for sake of some kind of fluid prototyping rarely
leads to anything solid. If "time to market" counts, this can be
a viable strategy though...
2023-02-04 02:08:25 +01:00
24d421c6ed DOC: decide to pull through with the layer renaming 2018-11-15 19:40:12 +01:00
be59e8c2e0 DOC: mark this RfC as dropped -- it was never implemented this way 2014-09-08 02:46:46 +02:00
a034c8be18 fix typo on RfC name
...spotted by looking into the Apache logs on www.lumiera.org
2014-09-08 01:29:48 +02:00
d1558bbe95 Fix navigation for RfCs 2012-09-18 02:31:44 +02:00
Christian Thaeter
61e5a6a47b RFC: finalize GitCommitMessageFormat 2012-09-13 03:59:45 +02:00
Christian Thaeter
aa60486066 apply the new RFC structure to existing RFC's 2012-08-30 20:50:08 +02:00
Christian Thaeter
7d964825d3 internal RFC reorganization
* rfcs are now all stored in the rfc folder (formerly hold the final rfcs)
* a new rfc_final folder is created
* the state folders (rfc_final|pending|parked|dropped) now contain
  symlinks back to the rfc pool
2012-08-30 20:50:08 +02:00