Antora for Docs: making sure our contributors are on board
by Adam Samalik
As many of you have probably noticed, together with bex and few other
people I work on moving the Fedora Docs to Antora. It has many technical
benefits as well as an active community. Talking about community, I want to
make sure that when the time comes and we're ready to push this thing to
production, our contributors are on board.
So I've just created a new epic: People! [1]
"The main reason we go through all this trouble is people. We want to make
it simple for people to contribute to the docs. And might not be a bad idea
to make sure our contributors are on board when we go crazy and push this
thing to production."
I'm looking for any useful input about making sure our contributors are on
board. I want this to be as smooth as possible.
My thinking is:
* Announce it here on this very list.
* Contact in advance every group having their docs on the site and:
** making sure we have converted their asciibinder source into the Antora
source right
** making sure they know how to make changes
* Do this over a few days, switching the Antora branches in all
repositories the site is built from to be the main branches. During these
few days, the current asciibinder site wouldn't update. All updates from
this period would end up on the new site. Basically, doing a few-days-log
freeze.
How does that sound? Anything I've missed?
Thanks!
Adam
[1]
https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/58
--
Adam Šamalík
---------------------------
Software Engineer
Red Hat
5 years, 7 months
Introducing myself - hi!
by Sanja Bonic
Hi fellow docs contributors,
As expected from new people joining the group, I'd like to say hello to
everyone and introduce myself.
I joined this list because I'll be working with several other people on
coordinating and writing documentation for CoreOS, Silverblue, containers,
and rpm-ostree. Part of the discussion around this can be found here:
https://discussion.fedoraproject.org/t/migrating-the-silverblue-sites-int...
I'll make an announcement thread about it once the documentation is set up,
asking more people to join in and contribute to those parts they know well,
as most people have years of experience I personally don't have with
rpm-ostree systems.
Before I joined Red Hat, I worked in several jobs - some of those related
to documentation were Senior Technical Writer where I've restructured and
redesigned documentation, Head of Marketing where part of my job also was
the restructuring of documentation for SEO purposes, games journalist,
copywriter, and tutor for scientific writing at university.
I hold an MSc in computer science, have been using open source software
since 2002, and like my systems minimal and customizable which is what I
also push for with Silverblue and Fedora CoreOS.
All the best,
Sanja
5 years, 7 months
[Fedocal] Reminder meeting : Docs Writing Hour
by bex@fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2018-08-15 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9195/
5 years, 7 months
[Bug 1614615] New: "How to enable nested virtualization in KVM"
page incorrectly describes sysfs nested parameter
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1614615
Bug ID: 1614615
Summary: "How to enable nested virtualization in KVM" page
incorrectly describes sysfs nested parameter
Product: Fedora Documentation
Version: devel
Component: virtualization-guide
Assignee: pbokoc(a)redhat.com
Reporter: cela(a)mit.edu
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org, lnovich(a)redhat.com,
zach(a)oglesby.co
Description of problem:
The documentation at
https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualizati...
states that /sys/module/kvm_intel/parameters/nested reports whether or not
nested virtualization is supported. This is incorrect; it reports whether or
not nested virtualization is enabled on the kvm_intel or kvm_amd kernel module.
How reproducible:
always.
Steps to Reproduce:
1) use an intel system that supports virtualization
2) load the kvm_intel module normally
3) cat /sys/module/kvm_intel/parameters/nested
4) unlock kvm_intel
5) load kvm_intel with nested=Y
6) cat /sys/module/kvm_intel/parameters/nested
Actual results:
The first 'cat' command displays 'N'. The second 'cat' command display 'Y'. The
documentation says that 'N' as a result of the first 'cat' command implies that
nested virtualization is not supported, but the second 'cat' command
demonstrates that it is.
Expected results:
The documentation should correctly describe that, if the first 'cat' command
produces 'N', it means that nested virtualization is disabled, not that nested
virtualization is not supported.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
Aesthetic issue on mobile
by Alessio Ciregia
Hello.
First of all: congratulations, great work.
Then I'm not sure if this is the right place to report issues. Is it
supposed to use bugzilla? Or pagure?
Maybe you are already aware, but I would like to report that on an Android
phone, using Firefox or the stock browser as well, in the right side of the
header there is an hamburger menu icon that seems useless. This icon is not
present using Firefox on a desktop PC.
Ciao,
A.
5 years, 7 months
[Fedocal] Reminder meeting : Docs Writing Hour
by bex@fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2018-08-01 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9195/
5 years, 8 months