Proposal: Adopt an AsciiBinder Based ToolChain
by Brian Exelbierd
Hi All,
I am sorry I missed yesterday's meeting, I am at a conference this week.
I have written a longish proposal
(http://www.winglemeyer.org/fedora_docs_proposal/latest/proposal/overview....)
about adopting an AsciiBinder toolchain.
I've tried to outline the challenges we have today and how I believe
this will get us a new documentation website and process quickly. There
is a Proof of Concept included with details on how you can replicate my
work.
I'd like feedback and to discuss if we can move forward with this
proposal. Can we please use email as travel will also prevent me from
attending next week's meeting.
regards,
bex
7 years, 6 months
Tooling, Tooling, Tooling
by Brian Exelbierd
This email is to drive some discussion around $subject. It follows from
a blog soon to be posted on the Fedora Community blog
(https://communityblog.fedoraproject.org). The text below is copied
from that blog:
Tooling, Tooling, Tooling
There was strong consensus around changing to new tools and markups. In
fact, most of the tooling conversations were held in small groups near
the end of the meeting. There was a desire to continue to see a drive to
simpler contribution and publication.
The only significant question was around the community, upstream
adoption and contributor base for pintail which is the central tool in
the new processing flow. People were very concerned that there wasn't
evidence of enough adoption and contribution to prevent the project from
being at risk of going either unmaintained or slowly maintained.
Please reply here for discussion.
regards,
bex
7 years, 6 months
Semantic Tagging in AsciiDoc
by Brian Exelbierd
Hi All,
A chance conversation today led me to thinking about semantic markup and
AsciiDoc. AsciiDoc is easier to write because it has fewer tags. It is
also easier because it has fewer keystrokes. However, it doesn't offer
a lot of options for marking up elements to:
* ensure consistency of localization by passing element information to
the localizer
* ensure consistency of formatting by ensuring all of the same elements,
for example command names, are marked up the same way
* allow for future automated testing with a project like `emender`
I went through the Installation Guide and found 97 DocBook XML tags.
I've put them in the table on this wiki page:
https://fedoraproject.org/wiki/Docs_Tag_Discussion
Please visit the page and edit it to weigh in on preferences about the
tags.
I believe this will help us complete our AsciiDoc style guide and do the
conversions more rapidly and effectively.
Today, if you want to discuss implementation of these tags in AsciiDoc,
please start a separate email thread.
Thank you.
regards,
bex
7 years, 6 months
I found a small hole in documentation
by Lailah
Hello folks,
I was trying to install Fedora in a laptop but I didn't want to delete
the Windows partition, just shrink it. I naturally looked up in
Documentation as it's not obvious in the partitioner how to shrink a
partition to make room in hard disk. I didn't find it. Not I found it
anywhere else. I eventually found it out by myself so I would like to
help others documenting the process or if it's a known bug, adding a
warning to documents.
Now.... How can I do that?
Cheers and thanks,
Sylvia
7 years, 6 months
Re : Release notes guide
by Jean-Baptiste
Hi, should we still advice not to translate because of publishing issues ?
----- Reply message -----
De : "Petr Bokoc" <pbokoc(a)redhat.com>
Pour : <docs(a)lists.fedoraproject.org>
Objet : Release notes guide
Date : lun., sept. 12, 2016 16:54
On 09/11/2016 11:27 PM, Glen Rundblom wrote:
> Hi everyone,
>
> Are we still doing the docbook guide for the Fedora 25 release notes?
Yep, looks like we are.
> Is the current repo here:
>
> https://pagure.io/release-notes
That's the one. We just talked about this on the weekly meeting and we
agreed that:
* we're still using DocBook for this release
* at this point it's prettty late in the release cycle (Beta comes out
in a month), so we're going to skip the part where we write beats in
wiki, and do it straight in docbook in the pagure repo
* we're going to use pagure to track progress. I'll create an issue
under the above repo for each Change listed at
https://fedoraproject.org/wiki/Releases/25/ChangeSet ; any contributor
wishing to cover that change can then assign it to themselves and work
on it. Also, anyone who finds a change not listed on the wiki page -
things like routine updates to major components - can obviously create
an issue for it as well.
Pete Travis is going to send out a mail with more detailed instructions
sometime soon.
> Thanks!
>
> -Glen
>
> --
> docs mailing list
> docs(a)lists.fedoraproject.org
> To unsubscribe:
> https://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
--
docs mailing list
docs(a)lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
7 years, 6 months