nico/www.nico.schottelius.org
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

add topic headers

Browse source 
Signed-off-by: Nico Schottelius <nico@ikn.schottelius.org>
This commit is contained in:
Nico Schottelius 2009-06-22 23:09:28 +02:00
parent a4e7daa356
commit 0fbe5356e5
2 changed files with 14 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
blog/lighttpd-plone-rewrite-redirect.mdwn
View file

@ -29,6 +29,8 @@ configuration of lighttpd looks like this:
([[a more detailled version can be found here|configs/lighttpd-zope-http-and-https]]) ([[a more detailled version can be found here|configs/lighttpd-zope-http-and-https]])
## The idea
Now I created a new [[about page here|about]] and want to redirect Now I created a new [[about page here|about]] and want to redirect
the old URLs **"^/ueber/nico-schottelius$"** and **"^/about/nico-schottelius$"** the old URLs **"^/ueber/nico-schottelius$"** and **"^/about/nico-schottelius$"**
from the Plone site to it. from the Plone site to it.
@ -38,6 +40,8 @@ First I tried the normal redirect like this:
url.redirect = ( "^/ueber/nico-schottelius$" => "http://www.nico.schottelius.org/about/", url.redirect = ( "^/ueber/nico-schottelius$" => "http://www.nico.schottelius.org/about/",
"^/about/nico-schottelius$" => "http://www.nico.schottelius.org/about/" ) "^/about/nico-schottelius$" => "http://www.nico.schottelius.org/about/" )
## The solution
Unfortunately, this did not work. You may already have spotted the bug... Unfortunately, this did not work. You may already have spotted the bug...
The correct way to redirect pages from lighttpd in front of The correct way to redirect pages from lighttpd in front of
[Zope](http://www.zope.org), which does ***rewriting*** is to match on the [Zope](http://www.zope.org), which does ***rewriting*** is to match on the

13
docs/the-term-foss.mdwn
View file

@ -1,8 +1,15 @@
[[!meta title="The term FOSS"]] [[!meta title="The terms FOSS and the relation to FS, OSS and FLOSS"]]
## Introduction
Today, there are different terms in use to describe ***free*** and
***open source software***. This article gives you a short overview
about those terms and a short reason why I prefer to use ***FOSS***.
## Existing terms
### Free software ### Free software
<br /><a href="http://www.gnu.org/">GNU</a> prefers to use the term "<a href="http://www.gnu.org/philosophy/free-sw.html">Free software</a>". The reason for me not to use this term are:<br /> [GNU](http://www.gnu.org) prefers to use the term
"<a href="http://www.gnu.org/philosophy/free-sw.html">Free software</a>".
The reason for me not to use this term are:<br />
<ul><li>The abreviation is "FS", which is ambiguous. "FS" is often used as the abreviation for "filesystem".</li><li>The term does not tell you directly, that you also have access to the source (main reason one).</li><li>I think people can easily think free software is just free as in "nothing to pay for it" (main reason two).<br /></li><li>I do not like to pronounce it. Think about "I've like effess." Nothing my tongue likes.<br /></li></ul> <ul><li>The abreviation is "FS", which is ambiguous. "FS" is often used as the abreviation for "filesystem".</li><li>The term does not tell you directly, that you also have access to the source (main reason one).</li><li>I think people can easily think free software is just free as in "nothing to pay for it" (main reason two).<br /></li><li>I do not like to pronounce it. Think about "I've like effess." Nothing my tongue likes.<br /></li></ul>
### Open source software ### Open source software
<br />I liked to use the term "<a href="http://www.opensource.org/docs/definition.php">Open source software</a>" <br />I liked to use the term "<a href="http://www.opensource.org/docs/definition.php">Open source software</a>"