public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: tulpenknicker@disroot.org
To: documentation@lists.ipfire.org
Subject: Wiki - doku
Date: Thu, 27 May 2021 10:45:42 +0000	[thread overview]
Message-ID: <a97ceeaf27c7f9c69f49e2592986203e@disroot.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2805 bytes --]

I have the urgent need to address the following things that are currently bothering me. The current development of the wiki does not give me much pleasure. I have already been in contact with the author about this. I'm especially concerned about what I see as an extremely wrong balance between having enough pictures and information to understand, but not being recognized as a picture book or "idiot guide" on the other hand. 
Furthermore there is a discrepancy of understanding. Either I am totally wrong or the author is. Whereby I would like the latter more ;-)

It is about the definition DMZ Pinhole. My understanding is that this is used regardless of whether orange is involved or not, i.e. if you want to get from one isolated, separate network to the next, that's a DMZ pinhole for me. For the author it is a blue green pinhole. 

Therefore he created/changed the pages

https://wiki.ipfire.org/configuration/firewall/default-policy

https://wiki.ipfire.org/configuration/firewall/accesstoblue

And created a "picture book". The only thing that is "missing" is the marking of which key to press...

https://wiki.ipfire.org/configuration/firewall/rules/bg-holes

Urgent clarification is requested on my part.

As it looks to me the author only promotes a new generation of copy and paste professionals. It seems to me that he has only considered that he wants to help everyone. What this can cause is not considered. The style how the whole was formulated rounds it then down. It reminds me somehow a small child to motivate and to hold out to the end. We're almost there...just this...hang in there....
I may be too dogged about the latter. Probably I'm just too old ;-)

What annoys me most about the whole story is the fact that this informations are many years written and has already been changed several times. So already many have looked over the Doku. Regardless of whether one is now right with something or not, if someone brings forward an objection then at least for me the absolute logical consequence is that this must be discussed! Until its resolved! If necessary you ask someone else to join the party  to provide who has there now right. To change it anyway with the words ~ "I have not understood that way, that has nothing to do with it for me" does not make it automatically right for all others. This train of thought is totally alien to me and also completely unacceptable!

It is important to me that the whole thing is not understood as pure criticism. My only interest is whether the wiki is correct and meaningful or false and unnecessary. 

The only reason why I post it here publicly is because there was no progress in the conversation between 4 eyes. And someone from the IPF Team i asked before this step, gave me the advice to ask here.

             reply	other threads:[~2021-05-27 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 10:45 tulpenknicker [this message]
2021-05-28  9:32 ` Michael Tremer
2021-05-28 12:56   ` tulpenknicker
2021-05-28 15:24     ` Michael Tremer
2021-05-28 15:42       ` Daniel Weismüller
2021-05-28 21:56       ` tulpenknicker
2021-05-30  8:15         ` ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a97ceeaf27c7f9c69f49e2592986203e@disroot.org \
    --to=tulpenknicker@disroot.org \
    --cc=documentation@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox