From: dnl <dnlipfire@runbox.co>
To: documentation@lists.ipfire.org
Subject: Re: New wiki painful to use
Date: Tue, 13 Aug 2019 01:06:24 +0000 [thread overview]
Message-ID: <AE31CDD3-01EB-4F7E-8C2F-9F2F20D69E9F@runbox.co> (raw)
In-Reply-To: <EEBA0832-ADEA-4DEC-A62A-C0165425A75F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Hi,
I've not used the new wiki and while I like the idea of using markup in theory I can imagine the frustration of using it regularly.
I didn't want to say this earlier as Michael seemed keen to write his own wiki, but have you considered using Atlassian confluence? It's free for open source software https://www.atlassian.com/software/views/open-source-license-request
They may even host a copy on their cloud if you want.
dnl
next parent reply other threads:[~2019-08-13 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EEBA0832-ADEA-4DEC-A62A-C0165425A75F@gmail.com>
2019-08-13 1:06 ` dnl [this message]
2019-08-14 13:58 ` Michael Tremer
2019-08-14 13:56 ` Michael Tremer
2019-08-15 20:51 ` Jon Murphy
2019-08-27 14:41 ` Michael Tremer
2019-08-27 15:54 ` Jon Murphy
2019-08-27 16:14 ` Michael Tremer
2019-09-03 22:19 ` Jon Murphy
2019-09-05 9:24 ` Michael Tremer
2019-09-05 20:52 ` Jon Murphy
2019-09-05 21:23 ` Tom Rymes
2019-09-06 12:01 ` Michael Tremer
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=AE31CDD3-01EB-4F7E-8C2F-9F2F20D69E9F@runbox.co \
--to=dnlipfire@runbox.co \
--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