From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: Peter Whittaker <pww@edgekeep.com>, selinux@vger.kernel.org
Subject: Re: Bad context in PostgreSQL page on SELinux Project wiki?
Date: Fri, 22 May 2020 12:10:29 -0400 [thread overview]
Message-ID: <CAHC9VhSWPxODxgPC5JPTAvRbA=HVa9QcE1dYm-x4U0-a8F7_PA@mail.gmail.com> (raw)
In-Reply-To: <321f492f19164c43104ec1fd9d699e80ad2a7380.camel@btinternet.com>
On Thu, May 21, 2020 at 4:57 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
> On Tue, 2020-05-19 at 17:40 -0400, Paul Moore wrote:
> > While I'm happy to host it, I think it might be better if we hosted
> > it
> > in the community GitHub repo - what would you think about creating a
> > new repo under https://github.com/SELinuxProject? Perhaps
> > https://github.com/SELinuxProject/notebook? While it might seem a
> > bit
> > odd to host an ODT file in a git repo, it is a good way to keep track
> > of historical changes and there are other tools such as the issue
> > tracker and "release" hosting which might be helpful.
>
> githubs sounds good, however as the document is quite large I'm
> splitting into sections like on the wiki as it will make easier editing
> (should anyone feel the need).
That sounds like a good idea. I imagine it would also help for people
using it as a reference - something I personally find very helpful.
> I've converted with pandoc using 'markdown_strict', where it converts
> text to md but most tables into html (as their own md table format will
> not render in some viewers). With firefox and the Markdown Viewer
> Webext, the samples I've done look ok.
>
> As with all these conversion apps, pandoc leaves a lot of cleaning up
> to do, so I'll be some time. I'll send you the files once I'm done.
> Thanks for your support.
Wow, that would be great! I was thinking just posting the ODT would
be a nice win, having it in something like Markdown so that GH can
render it from the web UI would be a *really* nice thing to have!
Once again, thanks for your help on this - documentation, especially
good and comprehensive documentation - is so hard to find.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2020-05-22 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 20:03 Bad context in PostgreSQL page on SELinux Project wiki? Peter Whittaker
2020-05-15 20:20 ` Stephen Smalley
2020-05-15 21:13 ` Peter Whittaker
2020-05-17 11:17 ` Richard Haines
2020-05-17 21:59 ` Paul Moore
2020-05-19 13:50 ` Richard Haines
2020-05-19 21:40 ` Paul Moore
2020-05-21 8:57 ` Richard Haines
2020-05-22 16:10 ` Paul Moore [this message]
2020-05-22 16:12 ` Paul Moore
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='CAHC9VhSWPxODxgPC5JPTAvRbA=HVa9QcE1dYm-x4U0-a8F7_PA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=pww@edgekeep.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).