public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Is there anybody out there?
Date: Thu, 23 Aug 2018 10:37:27 +0200	[thread overview]
Message-ID: <2c7f0d22aad25ea581a039bd7efe21541e7fa0ec.camel@ipfire.org> (raw)
In-Reply-To: <898278bf7da43d6920b58739809221962b6df2c0.camel@ipfire.org>

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

Hi Michael,
from my side i try to keep the wikis up-to-date where i more or less
maintain the software like OpenVPN if considerable changes has been
made. The Core123 changes aren´t documented until now cause i do wait
if the NCP patch will be included (compression problem is also in
working progress). If there are decisions made i will update it to the
latest state.

Otherwise, i try to keep all addons up-to-date which i´d introduced to
IPFire as good as possible. Some deeper changes which i do not
recognize may not be documented but there is always a link to
originated page which should deliver a detailed description of all if
needed.

Whith addons which i´d only updated it is more complicated since i can
test them only for functionality but the deeper know how of them lacks
sometimes so i leave better my fingers out of the documentation.

Great that you did this changes. If more of us do a part of this work,
the wiki might be a really nice one in my opinion.

Best,

Erik

Am Mittwoch, den 22.08.2018, 21:22 +0100 schrieb Michael Tremer:
> Hello,
> 
> I just wanted to send a message to everyone involved here about the
> wiki and
> what changes I have done. I sat down a couple of days ago and spent a
> few hours
> on writing, improving, moving and removing loads of content.
> Hopefully someone
> can have a look and check.
> 
> Biggest things:
> 
> * Main Page: I removed some sections which are not necessary for the
> average
> user and moved them together into a smaller list. That is nicer on
> mobile and
> draws attention to the four main sections.
> 
> * I entirely removed the crypto section which was quite empty and
> moved the few
> pages into the hardware section (HWRNGs and crypto accelerators).
> 
> * I added a guide on how to install IPFire on AWS: 
>     https://wiki.ipfire.org/installation/aws/start
> 
> * I added some details about the LWL hardware and removed the
> fountain networks
> section. This is going to merge into LWL soon. I also added a page
> about which
> appliances are affected by any of the Spectre/Meltdown/etc.
> vulnerabilities.
> 
> * I changed the sidebar to have more things on there that are
> accessed very
> often. I find that quite useful to get somewhere quickly.
> 
> * And then I restructured many pages without adding or removing any
> content.
> Have a look around. There is still plenty to do
> 
> All in all I am very often quite happy with the content on the wiki.
> But it does
> need work. Loads of things are outdated and pages can be shortened by
> referencing information that can be found somewhere else.
> 
> Is anybody in to help me out here?
> 
> Best,
> -Michael
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation

  reply	other threads:[~2018-08-23  8:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 20:22 Michael Tremer
2018-08-23  8:37 ` ummeegge [this message]
2018-08-23 13:13   ` Michael Tremer
2018-08-23 13:22     ` Alexander Schories
2018-08-23 13:25       ` Michael Tremer
2018-08-23 13:28         ` Alexander Schories
2018-08-23 13:37           ` Michael Tremer
2018-08-23 13:40             ` Alexander Schories
2018-08-23 13:42               ` Michael Tremer
2018-08-23 13:43                 ` Alexander Schories

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=2c7f0d22aad25ea581a039bd7efe21541e7fa0ec.camel@ipfire.org \
    --to=ummeegge@ipfire.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