ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/doc/devel/rfc/DistributedDevelopmentFramework.txt

107 lines
3.9 KiB
Text
Raw Normal View History

Import old DesignProcess into rfc_pending
2010-07-23 18:24:30 +02:00
Design Process : Distributed Development Framework
==================================================
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
[options="autowidth"]
|====================================
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-05 02:02:22 +02:00
|*State* | _Dropped_
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
|*Date* | _2007-06-07_
|*Proposed by* | ct
|====================================
Import old DesignProcess into rfc_pending
2010-07-23 18:24:30 +02:00
Distributed Development Framework
---------------------------------
Create our own toolset to track issues, tasks, bugs in a distributed manner.
Description
~~~~~~~~~~~
* Use git as backend
* Things get automatically updated/merged/pushed on a mob branch here
* Should be self-contained, checkout, ready to use
Tasks
~~~~~
* Serveral (shell?) scripts which ease the use
Rationale
~~~~~~~~~
Rewrap all RFC's This reverts commit 65bae31de4103abb7d7b6fd004a8315973d3144a. and reprocessed the wrapping. Note that the automatic wrapping is not perfect, some manual fixing by removing some hunks was required.
2010-07-26 02:54:14 +02:00
Import old DesignProcess into rfc_pending
2010-07-23 18:24:30 +02:00
* To cut the administrative overhead down
Comments
--------
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
Made this `final', this proposal got accepted and is already in use without
Line wrapped all rfc's
2010-07-24 16:48:32 +02:00
much discussion
Import old DesignProcess into rfc_pending
2010-07-23 18:24:30 +02:00
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
ct:: '2007-06-27T16:07:13Z'
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-05 02:02:22 +02:00
....
​
​
​
....
[large]#🌑 ​ 🌒 ​ 🌓 ​ 🌔 ​ 🌕 ​ 🌖 ​ 🌗 ​ 🌘 ​ 🌑#
[underline]#Historical remark#: This was ultimately the first
_conceptual_ (not process-related) RfC published in this Design-Process
(note the date!). Thus, _in hindsight,_
the question arises what this RfC was meant to propose; +
During the following months, an ambitious side-project named »**uWiki**« was started,
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
with the goal to provide a wiki-like web frontend based on completely self-contained
storage in a Git repository, without requiring any kind of data base. This project,
however -- in spite of some compelling prototype implementations -- was abandoned;
it became clear that such a system can not be bootstrapped from a lightweight,
minimalist setup and would require a significant amount of web development
rather -- a task no one was willing to take on.
Yet the Lumiera project succeeded in building a web presence based on
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-05 02:02:22 +02:00
https://asciidoc-py.github.io/[Asciidoc] sources
https://git.lumiera.org/?p=website;a=summary[checked into Git],
with a lightweight
https://git.lumiera.org/?p=website;a=blob;f=build_website.sh;h=60b90e18d5732d66566baf2c20a217212a5dcece;hb=aefc91e13a95a3c742dc8143c374ec982e0aa56b[commit-hook script]
to automatically publish any changes on git-push -- a scheme
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
which comes close to the gist of this RfC.
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-05 02:02:22 +02:00
Ichthyostega:: '2025-09-08'
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
Import old DesignProcess into rfc_pending
2010-07-23 18:24:30 +02:00
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-05 02:02:22 +02:00
.State -> Dropped
After reconsidering this RfC, _many years later,_ it seems prudent to mark it as __`Dropped'.__
The reasons for this decision are manifold. For one, the project never fully embraced this
working style, it was a vision from the early days rather. _Parts_ of that vision became a
practical reality, like the use of a link:{rfc}/MasterRepositorySetup.html[shared master repository],
or the use of Git and Asciidoc to generate and publish our website directly from a hook-script.
But we did not ``create our own toolset to track issues, tasks, bugs in a distributed manner''.
This idea might seem enticing for a new experimental project, and, when taken further, it leads to
a development style where most questions of coordination, and notably the preparation of releases
and the delivery and roll-out of published code are handled by an automated production line.
Developers can do what they like most: ``code cool things'' -- while all that
``nasty other stuff'' is dealt with by an »Invisible Hand«.
I do not consider such a setup healthy on the long run, nor can I see how it would be
adequate for a project with liabilities to care for: we should not consider the coordination
of a release cycle as something extraneous, to be ``automated away'' -- it requires the
full attention of the developers rather, to provide a longtime stable version and not to
interfere with the work of creative people, using the software in novel ways,
not foreseeable by the developers.
For this reason, I moved into the opposite direction and have now switched to the
link:/project/background/GitFlow.html[Git-flow branching model].
Ichthyostega:: '2025-09-20'
''''
clean-up: comb through the historical pages to fix markup errors Some sections of the Lumiera website document meeting minutes, discussion protocols and design proposals from the early days of the project; these pages were initially authored in the »Moin Moin Wiki« operated by Cehteh on pipapo.org at that time; this wiki backed the first publications of the »Cinelerra-3« initiative, which turned into the Lumiera project eventually. Some years later, those pages were transliterated into Asciidoc semi-automatically, resulting in a lot of broken markup and links. This is a long standing maintenance problem problem plaguing the Lumiera website, since those breakages cause a lot of warnings and flood the logs of any linkchecker run.
2025-09-08 04:04:39 +02:00
Back to link:/x/DesignProcess.html[Lumiera Design Process overview]
Reference in a new issue Copy permalink