[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc@fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2018-10-17 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/
5 years, 6 months
New Mindshare team for docs.fp.o: Fedora Badges
by Justin W. Flory
Hello all,
Could someone familiar with the Antora pipeline review my pull request
to add a new repository for the Fedora Badges team to docs.fp.o?
https://pagure.io/fedora-badges/pull-request/649
We want to set up a new dedicated section for Fedora Badges resources
and migrate content we had on Trac. I wanted to get feedback that the PR
is a correct implementation.
Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 6 months
[feedback wanted] Planning Fedora Docs hack-fest targeting user
communities
by Justin W. Flory
Hi all,
In today's CommOps meeting, we revisited an old ticket about planning a
Fedora Docs hack-fest, focusing on getting active, knowledgeable users
across Fedora's user communities to contribute and update content in the
Quick Docs repo (also encouraging people from our user communities to
link and reference the official docs).
Please take a look and weigh in on this Fedora Discourse thread (please
don't reply on the mailing lists because it will inevitably exclude
someone from one sub-project or another):
https://discussion.fedoraproject.org/t/fedora-docs-community-contribution...
We learned Fedora Join SIG was talking about similar ideas recently, so
we wanted to prevent duplication of work and see if we can all work
together to make this idea happen.
Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 6 months
Let's get started on Fedora 29 Release Notes!
by Petr Bokoc
Hi docs!
It's that time of the half-year again; we're about a month from the
current planned date for Fedora 29 final release, and it's time to start
banging out release notes.
Anyone who wants to contribute should start here:
https://pagure.io/fedora-docs/release-notes/issues
1. Pick one or more issues that have "F29" in the title.
2. Open each issue you picked, and click the Take button on the right to
claim it. (If you claim an issue but later find out you don't have time
to write about it, remove yourself from the issue ASAP so others can see
it's free and take it!)
3. Find some information about the issue. A lot of them have plenty of
info in them already; if not, find out who's responsible for the change,
and talk to them on IRC or via mail. Of course it's always better if you
try to do research before you ask questions.
4. Write a release note about the issue. If you're not sure how exactly
a release note looks, check out some of the previous releases for
inspiration. We don't want any long, overly technical texts, the release
notes are meant to highlight changes, not tell people how to use something.
5. Now the workflow diverges based on your permissions and technical skills:
5a. If you know how to use git and asciidoc, we'd appreciate if you
wrote up the release note and sent a pull request against the main repo,
branch "f29". Note that we have a different directory structure for this
release; your contributions should go into one of the files in
"modules/release-notes/pages/". Use the "build.sh" and "preview.sh"
scripts in the repository root to preview your changes locally; see the
repository README for specific instructions. If you can't see the
section where you added your contributions at all, make sure it's
included in "modules/release-notes/nav.adoc".
5b. If the above sounds like gibberish to you, it's fine: just add a
comment with your text into the issue, and ping me on IRC or through
e-mail; I'll mark it up for you and make sure your contribution appears
in the final document.
If anyone has any questions, go ahead and ask. The current schedule
shows the preferred final release target at October 23, giving us about
a month and a half. Don't count on the release date slipping :).
Happy writing!
--
Petr Bokoč (pbokoc)
Senior Technical Writer
Community Platform Engineering
Red Hat Czech, s. r. o.
Purkyňova 99
612 45 Brno, Czech Republic
5 years, 6 months
[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc@fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2018-10-10 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/
5 years, 6 months
The Telegram <-> IRC bridge is now up!
by Petr Bokoc
Hi everyone,
The Telegram <-> IRC bridge for #fedora-docs is now up, so you can join
the channel through Telegram: http://t.me/fedora_docs. This brings the
Docs Project together with several other Fedora communities that already
use the same setup for their channels. A full list of these is at:
https://fedoraproject.org/wiki/Telegram
If you're not familiar with Telegram, it's a chat protocol and a set of
apps (for both mobile and desktop) that give you some advantages that
IRC doesn't have (without a bouncer at least), namely that messages are
stored persistently so you don't lose any conversations that happen when
your IRC client isn't running. More info here: https://telegram.org/
Since this is a bridge, messages between Telegram and IRC are forwarded
back and forth by a bot: fdocs-tg on IRC and #fedora-docs IRC bridge on
Telegram. Pings work the same way they normally do, if you ping
someone's username (not the bot), they'll get a notification if they
haven't disabled them in their client. Direct messages (IRC /query and
Secret Chat on Telegram) don't work between the two protocols, however.
Cheers,
Petr
5 years, 6 months
Self-introduction-Amit Sharma
by amit kumar
Hello
I am Amit Sharma from Jaipur, India.I am currently looking to contribute in
Fedora community. I have been a Linux user since 2016 but this is my first
time on intending to join an open source software project since I am
confident that I already acquired necessary skills to contribute.my
computer skills level is intermediate because I can successfully install
and configure a Linux o .s.However, I can do only basic web programming
HTML, CSS, JAVASCRIPT and MySQL.The only thing i can immediately contribute
significantly to the Fedora project is user documentation especially about
installation and configuration in a desktop and laptop and also looking
forward to learn more things with you all.
Can anyone sponsor me for the group?
Kind regards
5 years, 6 months
Re: [Fedora-join] How do I translate docs?
by Justin W. Flory
On 10/1/18 7:06 AM, Joakim Forøysund wrote:
> Hi!
> I would like to translate some docs, but not sure where to start. I
> successfully translated some software a few months ago, so all
> formalities should be fine. All docs files in Zanata are shown as
> read-only. Am I missing something? Please point me in the right
> direction. :)
>
Hi Joakim, welcome! I am including the Fedora Docs mailing list on this
reply.
There is ongoing work to support localization and translation for Fedora
Docs, but it is not yet ready. I am not sure if Zanata will be used or
not. See this thread for more info:
https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.or...
I'm not sure if there is anything you can do to support the translations
yet, but someone else on the list should be able to explain better than me.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 6 months