docs September 2019

docs@lists.stg.fedoraproject.org

12 participants
21 discussions

Error running build.sh
by Ankur Sinha 01 Oct '19

01 Oct '19

Hello, I'm running into errors while running ./build.sh in the council-docs repository for this PR: https://pagure.io/Fedora-Council/council-docs/pull-request/63 Initially, I got: > $ ./build.sh > > This build script is using Podman to run the build in an isolated environment. > > WARN[0000] Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument > Error: could not get runtime: default OCI runtime "runc" not found: invalid argument @hhlp pointed out that it's listed in F31 common bugs here: https://fedoraproject.org/wiki/Common_F31_bugs#Podman_fails_to_run_containe… The fix, unfortunately, doesn't seem to work fully: > (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$ rm ~/.config/containers/libpod.conf -f > > (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$ ./build.sh > > This build script is using Podman to run the build in an isolated environment. > > 2019-09-25T10:28:24.000811303Z: cannot rm state directory '/run/user/1000/crun/42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195': Directory not empty > ERRO[0002] Error removing container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error cleaning up container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error removing container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195 from runtime: `/usr/bin/crun delete --force 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195` failed: exit status 1 > (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$ > Would anyone have a workaround/fix please? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London

2 5

[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc＠fedoraproject.org 30 Sep '19

30 Sep '19

Dear all, You are kindly invited to the meeting: Docs Writing Hour on 2019-10-02 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/

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by bex＠fedoraproject.org 24 Sep '19

24 Sep '19

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2019-09-25 from 15:30:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: An hour of docs folks talking about what they are working on and what they'd like to work on. More information available at: [https://fedoraproject.org/wiki/Docs_Project_meetings](https://fedoraproject… Source: https://apps.fedoraproject.org/calendar/meeting/9196/

1 0

Redirecting the dnf-system-upgrade wiki page to the quick-docs page
by Ankur Sinha 23 Sep '19

23 Sep '19

Hello, The dnf-system-upgrade page on the wiki[1] was migrated to the quick-docs[2] sometime ago. What would the process be to set up a redirect? [1] https://fedoraproject.org/wiki/DNF_system_upgrade [2] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London

2 3

[Fedocal] Reminder meeting : Docs Writing Hour
by pbokoc＠fedoraproject.org 23 Sep '19

23 Sep '19

Dear all, You are kindly invited to the meeting: Docs Writing Hour on 2019-09-25 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/

1 0

Experimental feature — sections in menu
by Adam Samalik 19 Sep '19

19 Sep '19

Hi everyone! I've implemented an experimental feature — sections in the left menu. See an example. [1] Sections are created by making a bold item in the menu that doesn't link anywhere. See an example. [2] My motivation was restructuring the Modularity documentation — we have a lot of content in there and started to become quite hard to navigate. What do people think? Cheers! Adam [1] https://asamalik.fedorapeople.org/modularity-docs-restructure/modularity/ [2] https://pagure.io/fork/asamalik/fedora-docs/modularity/blob/restructure/f/m… -- Adam Šamalík --------------------------- Senior Software Engineer Red Hat

4 4

Documentation's internationalization
by Jean-Baptiste Holcroft 19 Sep '19

19 Sep '19

Hi, (please answer to docs mailing list) with future arrival of Weblate server for live testing, I want to continue the work we started long ago, and to work on making production deployment ready. While bringing localization support already is a great progress of our users, my plan is to use this project to allow us to test Weblate. Here are our tasks: https://teams.fedoraproject.org/project/translation-platform-migration/epic… #12 Autodetect new languages in site generation #13 Warn admin on missing l10n repositories #14 How do we deal with images? #15 User language autodetection #16 Fix homepage link issue for localized content #17 Admin documentation #18 i18n support in HTML #19 RTL support I think tasks #12 and #13 are ready for Adam's action. Tasks #14 and #15 are server side redirection. I assume website and infra team can help. Tasks #16, #18 requires a little bit of Antora knowledge. Tasks #19 may be easy to quick fix for any contributor. But challenging to properly cover with Antora generation? To me, tasks #12 to #16 are important tasks for production deployment. Please feel free to contribute in any way you'll like. Have a nice day, Jean-Baptiste

1 0

FYI: Errors when building versioned repos and how to fix them
by Petr Bokoc 18 Sep '19

18 Sep '19

Hi again! Yesterday I updated the build and preview scripts in several repositories (our versioned docs - Release Notes, Installation Guide, System Administrator's Guide); the old ones were still using Docker, the new ones use Podman and can build without root/sudo. If you used the old script before, you might run into an error message along the lines of "Error: relabel failed: operation not permitted" when trying to build using the new one. This happens because the build, cache, and public directories created by the old script contain a bunch of files owned by root; you can check by running "find . -group root" in the repo, if you get any output, you found the problem. To fix this, just run "sudo rm -rf build/ cache/ public/" to delete the old directories. The build script will recreate them the next time you run it, and the problem will go away. Don't worry about accidentally breaking anything, these directories are only used for temporary and preview files and they're all ignored in our repos (check the .gitignore), so you're not going to accidentally push them or anything like that. Cheers, Petr

1 0

Fedora 31 Release Notes season is open!
by Petr Bokoc 18 Sep '19

18 Sep '19

Hi everyone, Fedora 31 Beta is out[0] (yay!), and so it's time for us to get working on F31 Release Notes. As usual, we aim to cover notable Changes[1]. Ben Cotton has been tracking those in our release-notes issues for us, which allows us to grab a list of everything that needs to be documented[2]. Branch f31 is ready for your pull requests. = What to do 1. Pick one or more issues in the list linked above. 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!) Note that the Take button previously wasn't visible to people outside the fedora-docs group on pagure and I had no idea; it should work for everyone now :). 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. Note that you might not always be able to reach the owner in a reasonable timeframe; in that case just do your best, I'll be reviewing PRs, so if we publish something wrong, it's on me. 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 to 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[3] against the main repo, branch "f31". Your contributions should go into one of the files in "modules/release-notes/pages/", which one exactly depends on the contents of the change you're documenting. 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/Telegram 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 either here on the list or on IRC, I'm happy to help. The current schedule shows the preferred final release target on October 22, which gives us 5 weeks to do this. The release date may slip, but don't count on it. Happy writing! Petr [0] https://fedoramagazine.org/announcing-the-release-of-fedora-31-beta/ [1] https://fedoraproject.org/wiki/Releases/31/ChangeSet [2] https://pagure.io/fedora-docs/release-notes/issues?status=Open&search_patte… [3] https://docs.pagure.org/pagure/usage/pull_requests.html

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by bex＠fedoraproject.org 17 Sep '19

17 Sep '19

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2019-09-18 from 15:30:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: An hour of docs folks talking about what they are working on and what they'd like to work on. More information available at: [https://fedoraproject.org/wiki/Docs_Project_meetings](https://fedoraproject… Source: https://apps.fedoraproject.org/calendar/meeting/9196/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs September 2019