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: Tue, 19 May 2020 17:40:48 -0400 [thread overview]
Message-ID: <CAHC9VhTgXU=yLncdXHrZkyo23OGc+aLDcNZinqkTLPLiq81Ycw@mail.gmail.com> (raw)
In-Reply-To: <60438e5b407320275932f60bc10936b75c9280aa.camel@btinternet.com>
On Tue, May 19, 2020 at 9:50 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
> On Sun, 2020-05-17 at 17:59 -0400, Paul Moore wrote:
> > On Sun, May 17, 2020 at 7:17 AM Richard Haines
> > <richard_c_haines@btinternet.com> wrote:
> > > I update the notebook occasionally to keep track of changes for my
> > > own
> > > reference, but currently have no plans to publish a new one. If you
> > > do
> > > have comments I'm happy to take them onboard, however no guarantees
> > > to
> > > publish.
> >
> > I just wanted to say thank you once again for all your work on the
> > notebook, it's a great resource!
> Glad it's useful
>
> >
> > I understand not wanting to go through the process of generating new
> > editions of the notebook, but is the source material posted somewhere
> > online so that people who wanted an updated copy could access it?
> The source is not available anywhere that I know of (I did send it to a
> few people who wanted to translate it but never heard from them again
> !!!). I edit it with LibreOffice Writer as an odt document. It converts
> to pdf okay, but epub looks real crap.
>
> I guess I could post it somewhere, would you like to host it on your
> site ??.
>
> It needs cleaning up as I've scribbled all over it so will take a few
> weeks.
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.
However, the last thing I would want to do is put a hurdle between you
and the doc.
Let me know what you think, I'm happy to create a new repo for you on
the SELinuxProject GH org and set you up with the necessary
permissions - assuming the others don't mind, and I can't imagine they
would.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2020-05-19 21:41 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 [this message]
2020-05-21 8:57 ` Richard Haines
2020-05-22 16:10 ` Paul Moore
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='CAHC9VhTgXU=yLncdXHrZkyo23OGc+aLDcNZinqkTLPLiq81Ycw@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).