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.
98 lines
2.4 KiB
Text
98 lines
2.4 KiB
Text
Offering Skills for Help
|
|
========================
|
|
|
|
|
|
[options="autowidth"]
|
|
|====================================
|
|
|*State* | _Dropped_
|
|
|*Date* | _2007-06-13_
|
|
|*Proposed by* | ct
|
|
|====================================
|
|
|
|
|
|
Skills Collection
|
|
-----------------
|
|
Make a page where people can tell in which areas they are willing to support
|
|
others.
|
|
|
|
|
|
Description
|
|
~~~~~~~~~~~
|
|
Some Page should list different things needed for working on the project and
|
|
users should attach themself when they offer support for it. This is meant that
|
|
people who run into problems know who to ask. In contrast this is not meant
|
|
like these Skill pages on Sourceforge or such. I don't like this rating and
|
|
posing system. We let people assign themself to skill and not skills to people
|
|
and there is no rating.
|
|
|
|
Skills shall be anything which is needed like the tools we use, the code we
|
|
create etc.
|
|
|
|
|
|
|
|
Example
|
|
^^^^^^^
|
|
|
|
.Git
|
|
* ct
|
|
* j6t
|
|
|
|
.autotools
|
|
* ct
|
|
|
|
.lumiera/renderpipe
|
|
* ichthyo
|
|
|
|
|
|
Question: __shall this contain emails?__
|
|
|
|
|
|
Tasks
|
|
^^^^^
|
|
* just set this page up ... +
|
|
either on this wiki or in a TiddlyWiki which
|
|
becomes checked into the repo
|
|
|
|
|
|
Pros
|
|
^^^^
|
|
* inter developer support and help network
|
|
|
|
|
|
Cons
|
|
^^^^
|
|
* privacy concerns, people might not publish what they know or, even more,
|
|
what they _do not_ know
|
|
|
|
|
|
Alternatives
|
|
^^^^^^^^^^^^
|
|
...urgs 😶
|
|
|
|
|
|
Rationale
|
|
~~~~~~~~~
|
|
This only announces where people offer support within the lumiera developer
|
|
community and is absolutely voluntary.
|
|
|
|
|
|
|
|
|
|
|
|
Comments
|
|
--------
|
|
|
|
[underline]#Historical remark#: This RfC stems from the very first days of the »Cinelerra-3 movment«,
|
|
which turned into the Lumiera project over the course of the following months. The RfC was already
|
|
marked as __parked__ when first imported into the Lumiera Documentation in 2010. Early in 2008 however,
|
|
at the link:{ldoc}/devel/meeting_summary/2008-03-06.html#_draft_skills_collection[March developer meeting],
|
|
it was discussed shortly and deemed ``...only useful if there are more developers working on the project''.
|
|
|
|
Reading this RfC today gives me some kind of peculiar melancholic feeling -- it has the vibes of »zero hour«,
|
|
when all hands on deck are needed and everyone wants to help; people write their names on a blackboard
|
|
at the wayside, to get into contact, organise themselves or maybe just to find their beloved ones...
|
|
|
|
Ichthyostega:: '2025-09-11'
|
|
|
|
''''
|
|
Back to link:/x/DesignProcess.html[Lumiera Design Process overview]
|