benn/lumiera_
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Switch to HTTPS: also adjust protocol for the ASCIIDOC generated links

Browse source
This commit is contained in:
Fischlurch 2018-10-26 17:47:18 +02:00
parent 0626444855
commit 6ce66fc354
13 changed files with 33 additions and 33 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/design/architecture/playRender.txt
View file

@ -26,7 +26,7 @@ discussions and brainstorming sessions.
- link:http://article.gmane.org/gmane.comp.video.lumiera.general/2116[Timecode Widget and Framerates]
- link:http://article.gmane.org/gmane.comp.video.lumiera.general/2109[Time, Time-spans, Quatisation and Timecode]
- link:http://lumiera.org/wiki/renderengine.html#TimeQuant[Definition of Time entities]
- link:{l}/wiki/renderengine.html#TimeQuant[Definition of Time entities]
from the implementation notes in the TiddlyWiki

2
doc/devel/meeting_summary/2009-09-09.txt
View file

@ -96,7 +96,7 @@ _Ichthyo_ points out that he uses some reports frequently, and considers some
others nice-to-have. Finally it turns out that only Report #5 isn't used by
anyone and can be dropped.
_Cehteh_ points out that the http://issues.lumiera.org/tags[TracTags] macro
_Cehteh_ points out that the https://issues.lumiera.org/tags[TracTags] macro
is a convenient feature -- for example it allows to tag tickets by required skill.

16
doc/devel/meeting_summary/2011-04-13.txt
View file

@ -327,7 +327,7 @@ Conclusion
Trac spam
---------
After an increasing amount of Spam tickets in the link:http://issues.lumiera.org[Trac],
After an increasing amount of Spam tickets in the link:https://issues.lumiera.org[Trac],
_Ichthyo_ installed the Trac antispam plugin (which required an upgrade to Trac 0.12,
actually repackaging a current version into an pre-release debian package, as the
official debian package isn't on the required level). After a bit of training,
@ -354,7 +354,7 @@ revisit the relevant design process entries in each developer meeting.
.-- the Application Install proposal --
[caption="☉Transcript☉ "]
----------------------------
[2011-04-14 00:48:25] <cehteh> http://lumiera.org/documentation/devel/rfc_pending/ApplicationInstall.html
[2011-04-14 00:48:25] <cehteh> link:{ldoc}/devel/rfc_pending/ApplicationInstall.html
[2011-04-14 00:48:40] <ichthyo> maybe only pick out some interestin ones or some which are quick to decide
[2011-04-14 00:49:06] <cehteh> well i want to go over all pending .. then we can put notes there "boring for the next meeting"
[2011-04-14 00:49:42] <cehteh> for example this application install .. is boring .. you did a lot work, imo you can finalize it
@ -421,7 +421,7 @@ Design the Render Nodes interface
Developer Documentation Structure
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--> see link:http://issues.lumiera.org/ticket/763[Ticket #763]
--> see link:https://issues.lumiera.org/ticket/763[Ticket #763]
.-- Discussion of details --
[caption="☉Transcript☉ "]
@ -498,12 +498,12 @@ While it needs more work, it's a bit out of focus right now, so _park it.
Proc High Level Model and Placement concept
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
That's rather final by now. This link:http://lumiera.org/documentation/devel/rfc/ProcHighLevelModel.html[proposal]
That's rather final by now. This link:{rfc}/ProcHighLevelModel.html[proposal]
meanwhile documents the existing design; it's up to date and didn't see significant
additions since almost two years. Generally agreed upon, so it's _final_ now.
The same holds true for the
link:http://lumiera.org/documentation/devel/rfc/ProcPlacementMetaphor.html[Placement] proposal
link:{rfc}/ProcPlacementMetaphor.html[Placement] proposal
@ -545,7 +545,7 @@ Render Optimizer, Resource Management and Profiling
Roadmap
~~~~~~~
The link:http://lumiera.org/documentation/devel/rfc/Roadmap-first.html[Roadmap document]
The link:{rfc}/rfc/Roadmap-first.html[Roadmap document]
was erroneously not marked as final; +
Seemingly it was decided upon in 2009 already ...
@ -614,7 +614,7 @@ Threads Signals and important management tasks
Session structure -- Timelines, Sequences, Output
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This link:http://lumiera.org/documentation/devel/rfc_pending/TimelineSequenceOutput.html[proposal]
This link:{rfc}/TimelineSequenceOutput.html[proposal]
can be considered definitively final. Key point is: we have multiple timelines and a sequence can be used
in multiple timelines. We pretty much agree on that, thus it counts as _finalised_ now.
@ -627,7 +627,7 @@ in charge of that right now. Thus _park_ it for the time being.
Version Number Scheme
~~~~~~~~~~~~~~~~~~~~~
The proposal for link:http://lumiera.org/documentation/devel/rfc_pending/VersionNumberScheme.html[Version numbering]
The proposal for link:{rfc}/VersionNumberScheme.html[Version numbering]
is _accepted_ -- it's considered close to common practice and _ichthyo_ relied on it for the debian
package already.

4
doc/devel/meeting_summary/2012-09-12.txt
View file

@ -20,7 +20,7 @@ RFCs
----
It was not clear what state
http://lumiera.org/documentation/devel/rfc.html[RFCs] have in our
link:{ldoc}/devel/rfc.html[RFCs] have in our
documentation structure. The question was if they should, after
becoming finalized integrated into some other document or stay first
class and be referenced from other documents.
@ -101,7 +101,7 @@ A complete rewrite of Builddrone (a continuous integration system) is
now (almost) finished and will be deployed on our build server within
the next days. It has numerous improvements over the old one. More
information and documentation will appear at
http://builddrone.pipapo.org/ soon. Stay tuned.
https://builddrone.pipapo.org/ soon. Stay tuned.
Thanks to Lenny for helping with the documentation and Simon for the
Logo.

12
doc/devel/report.txt
View file

@ -18,7 +18,7 @@ Statistics and Reports
++++++++++++++++++++++++++++++++++++++
''''
^Statistics generated automatically by *OpenHub* based on Git master footnote:[»http://blog.openhub.net/about/[OpenHub]«,
^Statistics generated automatically by *OpenHub* based on Git master footnote:[»link:https://blog.openhub.net/about/[OpenHub]«,
formerly known as »Ohloh« is a public directory and networking site for free and open source software (FOSS),
offering analytics and search services for evaluating and comparing open source projects.]^
@ -33,10 +33,10 @@ image:http://gmane.org/plot-rate.php?group=gmane.comp.video.lumiera.general[Lumi
Tickets
-------
* link:http://issues.lumiera.org/query?group=status&milestone=0integration[report: Milestone Integration]
* link:http://issues.lumiera.org/report/14[recently changed tickets]
* link:http://issues.lumiera.org/report/13[blocked tickets]
* link:http://issues.lumiera.org/report/5[stalled tickets]
* link:https://issues.lumiera.org/query?group=status&milestone=0integration[report: Milestone Integration]
* link:https://issues.lumiera.org/report/14[recently changed tickets]
* link:https://issues.lumiera.org/report/13[blocked tickets]
* link:https://issues.lumiera.org/report/5[stalled tickets]
See the link:http://issues.lumiera.org/report[Trac overview] for more ticket reports.
See the link:https://issues.lumiera.org/report[Trac overview] for more ticket reports.

4
doc/devel/rfc/LumieraForwardIterator.txt
View file

@ -12,7 +12,7 @@ The situation focussed by this concept is when an API needs to expose a
sequence of results, values or objects, instead of just yielding a function
result value. As the naive solution of passing an pointer or array creates
coupling to internals, it was superseded by the GoF
http://en.wikipedia.org/wiki/Iterator[Iterator pattern]. Iteration can be
https://en.wikipedia.org/wiki/Iterator[Iterator pattern]. Iteration can be
implemented by convention, polymorphically or by generic programming; we use
the latter approach.
@ -94,7 +94,7 @@ relies on that interface for discovering session contents. Besides that, we
need more implementation experience.
Some existing iterators or collection-style interfaces should be retro-fitted.
See http://issues.lumiera.org/ticket/349[Ticket #349]. +
See https://issues.lumiera.org/ticket/349[Ticket #349]. +
Moreover, we need to
gain experience about mapping this concept down into a flat C-style API.

2
doc/devel/rfc/Roadmap-first.txt
View file

@ -18,7 +18,7 @@ level. We should
''not'' define ''Features'' to go into a certain level.
''the following text is copied from the Lumiera
http://issues.lumiera.org/roadmap[Trac]''
https://issues.lumiera.org/roadmap[Trac]''
Description: Milestones up to first Release

6
doc/index.txt
View file

@ -31,13 +31,13 @@ used as design notebook, featuring day-to-day design sketches, notes but also
quite some more persistent planning. Finished documentation text is constantly
moved over to the documentation section(s) of the Lumiera website.
-> access the Proc-Layer link:http://lumiera.org/wiki/renderengine.html[TiddlyWiki online here]
-> access the Proc-Layer link:{l}/wiki/renderengine.html[TiddlyWiki online here]
=== API Documentation ===
We use the link:http://www.doxygen.org/index.html[Doxygen] tool to extract
We use the link:http://doxygen.org[Doxygen] tool to extract
code comments and generate code level API and reference documentation.
-> link:http://lumiera.org/doxy/index.html[Doxygen generated documentation]
-> link:/doxy/index.html[Doxygen generated documentation]
== Media and Presentations ==

4
doc/technical/howto/backporting.txt
View file

@ -75,8 +75,8 @@ Transcript from a build session on a ``pristine'' Mint 17.2 installation:
* add the following to your `/etc/apt/sources.list`
+
----
deb http://lumiera.org/debian/ rafaela experimental
deb-src http://lumiera.org/debian/ rafaela experimental
deb https://lumiera.org/debian/ rafaela experimental
deb-src https://lumiera.org/debian/ rafaela experimental
----
* install _Ichthyo's_ DEB signing key

4
doc/technical/infra/MenuGen.txt
View file

@ -6,7 +6,7 @@ Website Navigation Generator
This page contains documentation and notes regarding the +menugen.py+ --
written 2/2011 during our attempt to get the new Lumiera website online finally.
The link::http://git.lumiera.org/gitweb?p=website-staging;a=blob;f=menugen.lua;h=aad2129d7f4ed3f3b35b2fc3ac2a63a9f1bfb62d;hb=menugen[initial draft version] was written by _cehteh_ in Lua
The link::https://git.lumiera.org/gitweb?p=website-staging;a=blob;f=menugen.lua;h=aad2129d7f4ed3f3b35b2fc3ac2a63a9f1bfb62d;hb=menugen[initial draft version] was written by _cehteh_ in Lua
**************************************************************************
@ -141,7 +141,7 @@ def addPredefined():
proj.putChildLast ('press')
proj.putChildAfter('faq', refPoint=Node('screenshots')) # <4>
proj.link('http://issues.lumiera.org/roadmap', label="Roadmap (Trac)") # <5>
proj.link('https://issues.lumiera.org/roadmap',label="Roadmap (Trac)") # <5>
Node('rfc').sortChildren()
--------------------------------------------------------------------------
<1> the _root node_ by convention uses a special ID token. Additional

2
doc/technical/overview.txt
View file

@ -71,7 +71,7 @@ There is an embedded JavaScript wiki (TiddlyWiki) within the source tree, mostly
used as design notebook, featuring day-to-day design sketches and notes, but also
quite some more persistent planning. Finished documentation text is constantly
moved over to the documentation section(s) of the Lumiera website. +
-> access the Proy-Layer link:http://lumiera.org/wiki/renderengine.html[TiddlyWiki online here]
-> access the Proy-Layer link:{l}/wiki/renderengine.html[TiddlyWiki online here]
Test Driven Development

2
doc/technical/proc/index.txt
View file

@ -21,7 +21,7 @@ While additions to the TiddlyWiki generally propagate to Lumiera/Master through
the normal merges, we've put up a rsynced version of the TiddlyWiki online for
direct access (of course read-only).
-> access the Proy-Layer link:http://lumiera.org/wiki/renderengine.html[TiddlyWiki online here]
-> access the Proy-Layer link:{l}/wiki/renderengine.html[TiddlyWiki online here]

6
doc/user/tutorials/DebianBuilding.txt
View file

@ -37,7 +37,7 @@ should _not_ be done as root.
. add a suitable source line to your *Apt configuration* ('/etc/apt/sources.lst')
+
----
deb-src http://lumiera.org/debian/ jessie experimental
deb-src https://lumiera.org/debian/ jessie experimental
----
. get all the *build dependencies*
+
@ -145,8 +145,8 @@ prefix, which matches the 'official' package name and version.
Quite frequently, a given source package generates several binary packages, e.g. the
main program, maybe a library and a documentation bundle. Because of this, often the
source package is named slightly different then the binary package, which can be a
problem sometimes. If in doubt, use the link:http://packages.debian.org[Debian package
search] or the link:http://packages.ubuntu.com[equivalent for Ubuntu] to locate packages,
problem sometimes. If in doubt, use the link:https://packages.debian.org[Debian package
search] or the link:https://packages.ubuntu.com[equivalent for Ubuntu] to locate packages,
versions, even individual files, or to get at the bug tracker for a package.
interesting files in the debian subdirectory