. The source is
on GitHub at
.
This is a branch on a fork of Fedora's Fedora-Dockerfiles. If the
project wants a pull request, let me know and I'll send one. It's
probably too late to get this into the F22 fedora-dockerfiles package.
Contents: python-sphinx-*, pandoc-*, FlightCrew and Calibre for ebook
wrangling and a few command-line utilities. At some point when I stop
having fun with Project Atomic on Windows Hyper-V I'll update this for
F22.
On Tue, Mar 24, 2015 at 2:54 PM, M. Edward (Ed) Borasky <znmeb(a)znmeb.net> wrote:
My two cents:
1. Pandoc is your friend!!! Write rST, Markdown, AsciiDoc, Textile,
DocBook, LaTeX and a bunch of others and Pandoc translates to HTML,
epub, various other text markups and if you've got the LaTeX tool
chain, PDFs. It will only take me half a day or so to put up a
Dockerfile with these goodies - I'll fork fedora-dockerfiles on GitHub
and build this puppy, since I use it heavily.
2. Standardization is good - IMHO vital. So let's make a decision that
minimizes the amount of time we waste building tools for ourselves and
standardize on something we can live with. Personally, I think Sphinx
/ rST / readthedocs is the best option - I'm a tad biased because I
know some of the creators, but given Pandoc's Markdown - rST
conversion I don't see any reason to use another toolchain.
On Tue, Mar 24, 2015 at 2:21 PM, David Gay <dgay(a)redhat.com> wrote:
> ----- Original Message -----
>> From: "Pete Travis" <lists(a)petetravis.com>
>> To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>,
jzb(a)redhat.com
>> Sent: Tuesday, March 24, 2015 11:04:00 AM
>> Subject: Re: Fedora Cloud Docs
>>
>>
>>
>>
>> On Mar 24, 2015 11:38 AM, "Joe Brockmeier" < jzb(a)redhat.com >
wrote:
>> >
>> > On 03/24/2015 01:01 PM, Jared K. Smith wrote:
>> > >
>> > > If there's a particular cloud-related topic you'd like to write
about --
>> > > go write! And then we can worry about the tooling, once there's
some
>> > > content to work with.
>> >
>> > I agree...ish. If Kushal, myself, mattdm, and jbrooks (for example) are
>> > collaborating on a document, we really need a single format to target.
>> >
>> > Best,
>> >
>> > jzb
>> > --
>> >
>>
>> I was actually polling about preferred markup format, because I am writing
>> tools, but Jared is right: don't let things like my misadventures with
>> python hold you back! Start now, don't worry about formats, docs will handle
>> the business of publishing and converting.
>>
>> --Pete
>>
>> _______________________________________________
>> cloud mailing list
>> cloud(a)lists.fedoraproject.org
>>
https://admin.fedoraproject.org/mailman/listinfo/cloud
>> Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct
>>
>
> I think it'd be good to have at least all *our* (Cloud) docs in one format. I
think it'd be a good idea to have that vote on markdown, rst, or otherwise.
>
> Of course, not being sure of that format yet doesn't mean you can't do some
writing now.
>
> My two cents.
> -- David
> _______________________________________________
> cloud mailing list
> cloud(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct
--
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-jou...
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.