[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc＠fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-09-18 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/9360/
4 years, 7 months
Antora "watch mode" (and Vim hack)
by Ankur Sinha
Hi,
I was looking at whether Antora could automatically generate pages when
the source change so that previewing while modifying docs would be
somewhat easier. (One does not need to re-run ./preview.sh, but
./build.sh must be re-run after each change.)
I'd filed a ticket upstream and was directed to this discussion:
https://gitlab.com/antora/antora/issues/329
It seems to be a WIP, and for the moment there's a way to do this. It
uses a gulpfile(?) however, and I don't know enough to figure out how to
make this work with our workflow. Would someone know?
------
Also, as a hack in the meantime, if you use vim, you can re-run the
./build.sh script each time a buffer is saved using "BufWritePost". So
something like this in your .vimrc would work:
augroup fedora_docs
autocmd!
autocmd BufWritePost *adoc !./build.sh
augroup END
There's a caveat, though---you must start vim in the project root where
./build.sh resides. I'm sure there's a way to detect the project root
and find ./build.sh and put the output into the quickfix list etc, but
I've not gotten down to writing a full plugin yet. :)
Add fugitive to the mix etc., and you don't need to exit vim while
editing docs at all:
https://github.com/tpope/vim-fugitive
Please feel free to improve on this and share them with everyone. Your
friends in the vim documentation are:
: help augroup
: help autocmd
: help BufWritePost
My rather messy vimrc is here for reference:
https://github.com/sanjayankur31/vimfiles/blob/master/vimrc
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
4 years, 7 months
[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc＠fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-09-11 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/9360/
4 years, 7 months
here's me: gpg key
by Timothy Smith
Here's my key info. Uploaded to the MIT server as instructed.
pub rsa2048 2019-09-06 [SC] [expires: 2020-09-05]
2D3D 54A5 C7FF 07D8 AD2D 872D ED63 C7CC EA17 CF71
uid [ultimate] Timothy T. Smith (Mail Key) <timothytsmith(a)hotmail.com>
sub rsa2048 2019-09-06 [E] [expires: 2020-09-05]
4 years, 7 months
Introduction
by Michael Hall
Hi All
I've just signed up to a new Fedora account and am interested in
contributing to the docs and maybe translations projects.
I have been using some form of Red Hat linux since the year 2000,
occasionally digressing into Slackware and Debian over this time. My work
background is in IT system administration, web development, and teaching.
I'm currently working as an instructor in a vocational college teaching IT
networking and sysadmin subjects - the content level is roughly that of
RHCSA/RHCE, and includes things like automation with Ansible. To date we
have mostly used CentOS in labs, but I am increasingly introducing Fedora.
One thing we struggle with is finding decent course materials. The official
Red Hat documentation is, as far as I can see, amongst the best there is
and it has become our defacto coursebook. I'd like to see Fedora
documentation be as good in its own way.
I'll read up on the documetation systems used here and what needs doing and
let you know when I'm up to speed. I'm pretty familiar with markdown etc.
Note: I'm in Australia so typically most US-based events like meetings
happen while I'm fast asleep. I'll catch what I can.
Mike
4 years, 7 months
Fedora 31 Beta Release Readiness meeting
by Ben Cotton
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 31
Beta Release Readiness meeting. This meeting will be held on
Thursday, 2019-09-12 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the release
of Fedora 31 Beta. Please note that this meeting will be held even if
the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/meeting/9614/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 7 months
here's me
by tts
Greetings,
Let’s see. Nightmare Before Christmas is one of my all time favorite movies. I have others, but that just sort of came to mind. Been doing Linux for quite a number of years. Actually started with FreeBSD in my very first IT gig. Fedora was my go to for quite a few years until a friend tempted me with Debian, Knoppix I think it was.
At my last place of employment I found myself contributing a lot to the corporate wiki. Really enjoyed it. I had the opportunity to write up a lot of different sorts of IT related docs, from disaster recovery to how to manage the IP phones.
But I think I really got the bug after helping to review and update the company security policies as part of the annual security audit. Who’d a thunk that rewriting and revising for conciseness and clarity could be so satisfying?
Anyway. Presently, I’m between gigs. Been taking this time to explore technical writing more seriously, working through a couple tech comm books, practicing writing generally, and looking into some of the tools of the trade, like DITA and AsciiDoc -- which I have no idea how to use just yet. The whole idea of a document tool chain is pretty wicked though.
Recently I came across the beginners resource post on the relevant subreddit, and here’s me. Looking forward to helping out however I can.
Cheers,
-tim
4 years, 7 months
