July 2015 - docs - Fedora mailing-lists

[Bug 1198984] New: firewalld: please improve documentation on using it on a RedHat/Fedora/CentOS router
by Red Hat Bugzilla 01 Sep '17

01 Sep '17

https://bugzilla.redhat.com/show_bug.cgi?id=1198984 Bug ID: 1198984 Summary: firewalld: please improve documentation on using it on a RedHat/Fedora/CentOS router Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: razvan.sandu(a)mobexpert.ro QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Hello, Description of problem: Even using the rich-language feature, it is still rather difficult to figure out how to use firewalld on a RedHat/Fedora/CentOS system that is used as a router (a "transparent" system). That's because: a. administrators will need *different* sets of rules/restrictions for access to the router itself and to the various services that run beyond the router (using or non using NAT). b. It is not very clear how/where the predefined firewalld zones implement their policies (ACCEPT or DROP) and when these policies apply to traffic bounded *to* the router system or to traffic that *traverses* the router. For example, an administrator needs an *easy* method to restrict VNC access *to* the router itself (INPUT), but may want free VNC access to some server located *behind* the router (FORWARD). In the second case, forwarding may (or may not) imply NAT, depending if he goes on the Internet via the external interface or simply goes in another LAN segment beyond the router. c. It is not very clear how/where the predefined firewalld zones implement their trafic rules ( *exceptions* to ACCEPT or DROP default policies) and when these rules apply to traffic bounded *to* the router system or to traffic that *traverses* the router. Additional info: Even it is not dynamic, the Shorewall application (http://shorewall.net/) acts as a higher-level language over iptables, offering the same concepts of "zones" for interfaces. Much of its conceptual architecture is directly applicable ("portable") to firewalld, if accepted by developers. Somewhat different from conceptual point of view, the "zones" are "levels of trust surrounding the router", including thr FW zone for the router itself. (unlike firewalld, the shorewall zones have no "sources" or "services" embedded in them). IPv4 and IPv6 zones are completely separated (they actually represent different levels of trust). Administrators may directly define policies, i.e. allow *default* actions to be done when an packet travels from a zone to another (ACCEPT, REJECT). The most sane policy between any two zones is REJECT (with further exceptions defined as rules, see below). Rules are *exceptions to policies* , explicitly defined (based on various criteria such as source IP, destination IP, ports, etc.) Rules may be expressed via predefined (or customised) "macros" (which are the direct equivalent of firewalld's "services"). IPv4 and IPv6 policy and rules are completely separated (IMHO that's good, since the use of global IPv6 addresses pose completely different security problems than NATted & externally firewalled IPv4). Best regards, Răzvan -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 2

[Bug 755744] New: typo in PV-Configuring_Additional_Devices
by Red Hat Bugzilla 01 Sep '17

01 Sep '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: typo in PV-Configuring_Additional_Devices https://bugzilla.redhat.com/show_bug.cgi?id=755744 Summary: typo in PV-Configuring_Additional_Devices Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: virtualization-guide AssignedTo: docs(a)lists.fedoraproject.org ReportedBy: shaiton(a)fedoraproject.org QAContact: nobody(a)fedoraproject.org CC: kwade(a)redhat.com, oglesbyzm(a)gmail.com Classification: Fedora Story Points: --- Type: --- >From the file available in transifex, Now you can configure the new network interfaces using <command>redhat-config-network</command> or Red Hat Enterprise Linux3 or <command>system-config-network</command> on Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5. that should be "on" Red Hat. I could have corrected that now that I have git access, but this git is still for F14… There were plenty of update about virt since F14, is it outdated? http://fedoraproject.org/wiki/Docs_Project_meetings#Guides -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 7

[Bug 1095977] New: RFE: static IP assignment
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1095977 Bug ID: 1095977 Summary: RFE: static IP assignment Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Static IP addresses are crucial for applications like DHCP servers or other infrastructure that can't rely on external assignment. They're also helpful for home users that want to predictably locate their Fedora installation. Explain the use case for this and some alternative methods, then the procedure for setting a setting a static IP using both ifcfg files and graphical methods. Each method could be explained in a separate article; ie "... on the command line" and "... with GNOME" and "... with KDE" and so on. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 2

[Bug 1101798] New: RFE: Captive portal
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1101798 Bug ID: 1101798 Summary: RFE: Captive portal Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Create a recipe for configuring a simple captive portal with Fedora that will require users to acknowledge a terms of use message before allowing connections to pass. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 1101796] New: RFE: NAT router
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1101796 Bug ID: 1101796 Summary: RFE: NAT router Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Create a recipe for using Fedora as a NAT router using Firewalld and NetworkManager. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 3

[Bug 1096394] New: RFE: Thin Client (Tracking Bug)
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1096394 Bug ID: 1096394 Summary: RFE: Thin Client (Tracking Bug) Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Fedora can be used as a server and client environment for a thin client deployment. Document the required procedures to do this. Because of the broad scope and number of procedures involved, this should be split up into recipes addressing component tasks. This bug will be used to track the overall progress; please block this bug with any new bugs created for the purpose. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 2

[Bug 1095945] New: RFE: disabling head parking on spinning drives
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1095945 Bug ID: 1095945 Summary: RFE: disabling head parking on spinning drives Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Some drives have aggressive APM, and the resulting frequent head parking can negatively impact access latency and produce an annoying clicking sound. Explain the theory, benefits, procedure, and risks of adjusting APM settings with hdparm. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 693536] New: How to increase the number of configured loop devices
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: How to increase the number of configured loop devices https://bugzilla.redhat.com/show_bug.cgi?id=693536 Summary: How to increase the number of configured loop devices Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: virtualization-guide AssignedTo: fedora-docs-list(a)redhat.com ReportedBy: apevec(a)redhat.com QAContact: nobody(a)fedoraproject.org CC: stickster(a)gmail.com, kwade(a)redhat.com, oglesbyzm(a)gmail.com Classification: Fedora Story Points: --- Description of problem: http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sec… Number of loop devices cannot be changed via modprobe.conf since loop is not a kernel module anymore: # grep DEV_LOOP /boot/config-2.6.34.8-68.fc13.x86_64 CONFIG_BLK_DEV_LOOP=y -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 7

[Bug 1198643] New: Append parameters to grub.cfg
by Red Hat Bugzilla 08 May '17

08 May '17

https://bugzilla.redhat.com/show_bug.cgi?id=1198643 Bug ID: 1198643 Summary: Append parameters to grub.cfg Product: Fedora Documentation Version: devel Component: virtualization-guide Assignee: docs(a)lists.fedoraproject.org Reporter: geanceretta(a)gmail.com 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 instructions[1] of how to append parameters to Grub's grub.config file is obsolete on recent releases of Fedora. The file /boot/grub/grub.conf doesn't exist anymore. The way to do it now is (tested on Fedora 20): 1 - Edit /etc/default/grub 2 - Append information at the line GRUBCMDLINELINUX=" ... console=tty0 console=ttyS0,115200 ... ") 3 - Regenerate the /boot/grub2/grub.cfg file with the command "grub2-mkconfig -o /boot/grub2/grub.cfg" Link: [1] http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr… Additional info: The documentation is refered to version 18 where it should work, but as we don't have a documentation in a most atual release of Fedora for that subject, you can write a note for the users of most recent releases of Fedora that came with Grub2, where the procedure is according with that listed above. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 4

[Bug 1079769] New: Broken link in Publican FAQ section about recognised <programlisting> languages
by Red Hat Bugzilla 09 Jan '17

09 Jan '17

https://bugzilla.redhat.com/show_bug.cgi?id=1079769 Bug ID: 1079769 Summary: Broken link in Publican FAQ section about recognised <programlisting> languages Product: Fedora Documentation Version: devel Component: publican-doc-el6 Assignee: r.landmann(a)redhat.com Reporter: mmurray(a)redhat.com QA Contact: nobody(a)fedoraproject.org CC: docs(a)lists.fedoraproject.org, r.landmann(a)redhat.com Description of problem: http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html… "Refer to http://search.cpan.org/~szabgab/Syntax-Highlight-Engine-Kate-0.06/lib/Synta… for the full list of languages that Syntax::Highlight::Engine::Kate supports, including their expected capitalization and punctuation." That link no longer works as 0.06 is no longer available on CPAN. Both 0.07 and 0.08 exist. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EShDEHLgig&a=cc_unsubscribe

1 5

Orphaning FreeIPA guide
by Martin Kosek 11 Aug '16

11 Aug '16

Hello all, FreeIPA project is already for some time without sufficient resources to revive and maintain our former long upstream user guide. We did not find enough manpower either in FreeIPA developer nor our users community, so we decided to stop maintaining it. Detailed justification including links to mail threads in: http://www.freeipa.org/page/Upstream_User_Guide I would like to avoid leaving any loose ends on Fedora Documentation project side, do you have any recommendation for us? I already closed respective Bugzillas and upstream Trac tickets with explanation. Should we also orphan the guide in https://fedoraproject.org/wiki/Docs_Project_meetings#Guides or on any other locations? For starters, I think we should close the "freeipa-guide" component of "Fedora Documentation" as nobody from our team would be responding there. Thanks for any advise. -- Martin Kosek <mkosek(a)redhat.com> Supervisor, Software Engineering - Identity Management Team Red Hat Inc.

5 10

introduction - Ryan
by Ryan Gough 27 May '16

27 May '16

Hi Everyone, I'm looking at getting involved in the project as I have been a long time user of Fedora (e.g. since Core 1) and would like to start contributing. My name is Ryan, I'm from Western Australia (GMT+8). I am an IT technician and have been using linux as a hobby since 2k4 (using RH9). I have also had the opportunity to work with RHEL in my job during a project as well as having worked with a couple of other distros. In my line of work I have often needed to produce documentation to a professional standard and I feel I can contribute this way currently. I believe I should be able to contribute 4 hours a week at this point in time. Regards, Ryan irc: _terminal_ FAS: t3rm1n4l

2 2

[fedora-badges] #259: Fedora Cookbook Contributions
by fedora-badges 28 Feb '16

28 Feb '16

#259: Fedora Cookbook Contributions -------------------------------------+------------------------------------- Reporter: | Owner: immanetize | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 1 | Concept approved (reviewers only): | 0 | Badge definition status: | Full, needs review | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: Contributing "recipes" to the Fedora Cookbook: 1 submission: Cookbook I: Commis - "You had a recipe published in the Fedora Cookbook. Appetizing!" 5 submissions: Cookbook II: Tournant - "You have published 5 recipes in the Fedora Cookbook. Tasty!" 15 submissions: Cookbook III: Grillardin - "You have published 15 recipes in the Fedora Cookbook. Delicious!" 30 submissions: Cookbook IV: Saucier - "You have published 30 recipes in the Fedora Cookbook. Scrumptious!" 50 submissions: Cookbook V: Sous Chef - "You have published 50 recipes in the Fedora Cookbook. Delectable!" 100 submissions: Cookbook VI: Chef de cuisine - "You have published 100 recipes in the Fedora Cookbook. Decadent!" 150 submissions: Cookbook VII: Gourmand - "You have published 150 recipes in the Fedora Cookbook. Beefy!" Badge names borrowed from http://en.wikipedia.org/wiki/Brigade_de_cuisine , suggestions for improvement on names and patter are welcome. Some dining-related artwork would be greatly appreciated. Submissions are reviewed and committed manually, so the badges will have to be manually awarded as well. Anyone in docs-writers should be able to award these badges. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/259> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 10

[Bug 1008149] New: Contraficting info about the need of shared storage for storing guest images to be migrated
by Red Hat Bugzilla 05 Nov '15

05 Nov '15

https://bugzilla.redhat.com/show_bug.cgi?id=1008149 Bug ID: 1008149 Summary: Contraficting info about the need of shared storage for storing guest images to be migrated Product: Fedora Documentation Version: devel Component: virtualization-getting-started-guide Assignee: dayleparker(a)redhat.com Reporter: jrodrigosm(a)yahoo.es QA Contact: docs-qa(a)lists.fedoraproject.org CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org Hi, In the Fedora 19 "Virtualization Getting Started Guide", section 2.2 ("What is migration?"), URL http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting_S… In the paragraph right before the 2.2.1 title, it is stated that "In Fedora 19, shared storage is not necessary for storing guest images to be migrated. With live storage migration [...]". But in the last paragraph of the page, right before the note, it is stated that "Shared, networked storage must be used for storing guest images to be migrated. Without shared storage, migration is not possible." These two statements seem contradictory to me. I just started learning about virtualization, so I am unable to propose an alternative. But I do think some clarification is needed. Thanks, Rodrigo -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=QwkGtwKvp5&a=cc_unsubscribe

1 3

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )
by Pete Travis 29 Jul '15

29 Jul '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-07-30 from 12:00:00 to 13:00:00 US/Mountain The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. Source: https://apps.fedoraproject.org/calendar/meeting/434/

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 26 Jul '15

26 Jul '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-07-27 from 14:00:00 to 15: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/371/

1 0

[Bug 578960] virtualization guide recommends non-existent package virtio-win
by Red Hat Bugzilla 24 Jul '15

24 Jul '15

https://bugzilla.redhat.com/show_bug.cgi?id=578960 Frediano Ziglio <fziglio(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|fziglio(a)redhat.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )
by Pete Travis 22 Jul '15

22 Jul '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-07-23 from 12:00:00 to 13:00:00 US/Mountain The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. Source: https://apps.fedoraproject.org/calendar/meeting/434/

1 0

Release Notes, and F23 Change list
by Zach Oglesby 21 Jul '15

21 Jul '15

Fedora 23 is just around the corner and it is time to buckle down and start working on the release notes. If you are interested in working on this, or you want an easy way to get more badges please take a look at the [wiki page][1] and sign up to write a beat for the release notes. If you have question on what a beat is or how to go about writing it please ask on the list, or in irc, or read the documentation on [how to write this documentation][2]. If you have worked on this in the past please visit the page and remove the asterisk (*) from your name to show that you want to work on that beat this time around. Now your [change log][3]: (Note: I did not add a synopsis for self contained changes) 1 Fedora 23 Accepted System Wide Changes Proposals 1.1 Harden All Packages Hardening is the process of securing a system/application by reducing its unnecessary functions, or restricting access. In Fedora 22 and before, it was up to the package maintainer to add %global _hardened_build 1 to their spec file to ensure their program was hardened. Beginning with Fedora 23 this will now become the defaults for all packages. 1.2 Mono 4 Update the Mono stack in Fedora from 2.10 to 4.* 1.3 Disable SSL3 and RC4 by default This change will disable by default the SSL 3.0 protocol and the RC4 cipher in components which use the system wide crypto policy. That is, gnutls and openssl libraries, and all the applications based on them. 1.4 Perl 5.22 A new perl 5.22 version brings a lot of changes done over a year of development. Perl 5.22 should be released 5/20/2015. See 5.21.11 perldelta for more details about preparing release. 1.5 Default Local DNS Resolver To install a local DNS resolver trusted for the DNSSEC validation running on 127.0.0.1:53. This must be the only name server entry in /etc/resolv.conf. 1.6 Fedora 23 Boost 1.59 Uplift This change brings Boost 1.58.0 or later to Fedora 23. We generally aim to ship 1.59.0, as that seems likely to make it (hence the Change name), but 1.58.0 is out and available now. 1.7 Glibc locale subpackaging This change should make it possible to install or uninstall locales individually. 1.8 SELinux policy store migration The newest SELinux userspace project release 2015-02-02 includes a change of the location of the SELinux policy store, which defaults to /var/lib/selinux/. 1.9 Two Week Atomic Fedora Atomic Host is an implementation of the Project Atomic pattern for a specialized operating system for the deployment of containerized applications. For the past two Fedora releases, we've included an Atomic Host cloud image as a non-blocking deliverable. However, upstream Atomic is moving very fast — by the end of the alpha, beta, final stabilization cycle Fedora uses, the released artifact is basically obsolete. Additionally, the Project Atomic team at Red Hat would like to do their ongoing development work in the Fedora upstream, and the six-month release cycle does not lend itself to that. 1.10 Unicode 8.0 support Unicode 8.0 got release on 17th June 2015. It includes 41 new emoji characters (including five modifiers for diversity), 5,771 new ideographs for Chinese, Japanese, and Korean, the new Georgian lari currency symbol, and 86 lowercase Cherokee syllables. It also adds letters to existing scripts to support Arwi (the Tamil language written in the Arabic script), the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other languages of Africa. In total, this version adds 7,716 new characters and six new scripts. 1.11 IBus 1.5.11 IBus 1.5.11 will have the features of XKB prefix language icons on the panel in KDE 5 and support $HOME/.XCompose file in all desktops. 1.12 Node.js 0.12 Fedora 23 will be updated to Node.js 0.12, the latest release of the platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. 1.13 jQuery jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. 1.14 Layered Docker Image Build Service Fedora currently ships a Docker base image, but Docker supports a layering concept. There are some applications like Cockpit which we would like to ship as layered applications. 2 Fedora 23 Accepted Self Contained Changes Proposals 2.1 Cinnamon Spin 2.2 System Firmware Updates 2.3 Cockpit GUI for Domain Controller Role 2.4 Containerized Server Roles 2.5 Frappe Framework 2.6 Cloud MOTD 2.7 Cloud Systemd Networkd 2.8 Local Test Cloud 2.9 RPM MPI Requires Provides 2.10 Sugar 0.106 2.11 ibus-libzhuyin 2.12 npm 2 2.13 Astronomy Spin 2.14 io.js Technology Preview [1]: https://fedoraproject.org/wiki/Category:Documentation_beats [2]: https://fedoraproject.org/wiki/Docs_Project_workflow_-_beat_writing [3]: https://fedoraproject.org/wiki/Releases/23/ChangeSet

5 8

Question(s) about a starting point
by Primoz D. 20 Jul '15

20 Jul '15

Hey, I've been away from Docs for the last couple of days, I am working on a project to get my VPS up and running. Yesterday I finally managed to get around to browse properly to the Docs section, and upon visiting this link: http://fedoraproject.org/wiki/Docs_Project_Review_Table It's under the section Help with Proof Reading, and it seems like this page is quote obsolete, as it is stated on it that F19 is drawing near, so I'm guessing that is kind of outdated with F20 being EOL-ed the previous month. So, the question here is, are there any other sections that need proof-reading? Or is there some other task that would be more suitable for a newbie to Linux? I see a request for a How-To wiki page for editing IP Tables, and while I maybe could search around for info on that topic, I don't think I'm capable of creating a How-To like that solely on my own (just yet). Any pointers and suggestions are very welcome, thanks. Primoz

2 1

Fedora Docs Weekly Meeting 20 July 2015
by Pete Travis 20 Jul '15

20 Jul '15

---------- Forwarded message ---------- From: <notifications(a)fedoraproject.org> Date: Jul 20, 2015 9:59 AM Subject: randomuser`'s meeting titled "Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings" ended in #fedora-meeting To: <meetingminutes(a)lists.fedoraproject.org> Cc: > ==================================================================================================== > #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings > ==================================================================================================== > > > Meeting started by randomuser` at 14:01:06 UTC. The full logs are > available at > http://meetbot.fedoraproject.org/fedora-meeting/2015-07-20/fedora_docs.2015… > . > > > > Meeting summary > --------------- > * Roll Call (randomuser`, 14:01:06) > > * New Writers (randomuser`, 14:11:40) > > * Release Notes Beats (randomuser`, 14:14:45) > * ACTION: randomuser to clear beats for F23 (randomuser`, 14:15:12) > * ACTION: randomuser to hand out badges for F22 beat writing, already > (randomuser`, 14:15:36) > * LINK: https://fedoraproject.org/wiki/Releases/23/ChangeSet > (randomuser`, 14:16:47) > * F23 Alpha Freeze is in just over a week (randomuser`, 14:17:11) > * ACTION: zoglesby to send Change summary to list, ask for Docs > Contacts (randomuser`, 14:17:49) > * LINK: > https://fedorapeople.org/groups/schedule/f-23/f-23-docs-tasks.html > (randomuser`, 14:18:47) > * LINK: https://fedorapeople.org/groups/schedule/f-23/f-23-docs.ics > (zoglesby, 14:19:49) > * ACTION: randomuser to make list of beat writers while assigning > badges and ask those people to keep beat writing (randomuser`, > 14:22:00) > * ACTION: randomuser to mail devel (devel-announce) after clearing > beats (randomuser`, 14:23:48) > > * Publishing (randomuser`, 14:26:47) > > * Guide Status (randomuser`, 14:28:50) > * smccann is fedora-izing the VADG (randomuser`, 14:34:07) > * VDAG -Virtualization Deployment and Administration Guide (lnovich, > 14:35:09) > * LINK: https://fedoraproject.org/wiki/Virt_Deploy_Admin_Planning for > VDAG planning (smccann, 14:37:02) > > * Outstanding BZ Tickets (randomuser`, 14:39:27) > * LINK: http://tinyurl.com/lbrq84 (randomuser`, 14:39:45) > > * Open floor discussion (randomuser`, 14:43:54) > * - office hours at 9AM EST Wed (lnovich, 14:53:22) > * - same on thurs (lnovich, 14:53:38) > * - Wed office hours will discuss the VDAG (lnovich, 14:54:02) > > Meeting ended at 14:57:05 UTC. > > > > > Action Items > ------------ > * randomuser to clear beats for F23 > * randomuser to hand out badges for F22 beat writing, already > * zoglesby to send Change summary to list, ask for Docs Contacts > * randomuser to make list of beat writers while assigning badges and ask > those people to keep beat writing > * randomuser to mail devel (devel-announce) after clearing beats > > > > > Action Items, by person > ----------------------- > * zoglesby > * zoglesby to send Change summary to list, ask for Docs Contacts > * **UNASSIGNED** > * randomuser to clear beats for F23 > * randomuser to hand out badges for F22 beat writing, already > * randomuser to make list of beat writers while assigning badges and > ask those people to keep beat writing > * randomuser to mail devel (devel-announce) after clearing beats > > > > > People Present (lines said) > --------------------------- > * randomuser` (77) > * grundblom (22) > * lnovich (17) > * bexelbie (17) > * zoglesby (15) > * smccann (10) > * zodbot (6) > * Capesteve (5) > * jjmcd (2) > * pbokoc (1) > * kirsti (1) > * pkovar (1) > > > > > Generated by `MeetBot`_ 0.1.4 > > .. _`MeetBot`: http://wiki.debian.org/MeetBot > > https://meetbot.fedoraproject.org/fedora-meeting/2015-07-20/fedora_docs.201… > > --

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 19 Jul '15

19 Jul '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-07-20 from 14:00:00 to 15: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/371/

1 0

Applying for membership in this group
by Primoz D. 16 Jul '15

16 Jul '15

Hello, My name is Primož, I'm 34 years old and reside in Slovenia, EU. I have a bachelor's degree in "Civil Engineering" (named differently here, but I was told that that is probably the most appropriate expression in English) and am currently unemployed. As far as my Linux experience goes, it is at novice level currently, even though my first clash with Linux was back in the late 90s when I installed Slackware on my computer, but back then, my main interest was mostly IRC, using BitchX, and wasting absurd amounts of time playing a MUD. After that, it was mostly Windows usage until a user on Freenode suggested Fedora to me, which I did install and tried out for a bit, but having to switch to Windows occasionally, the usage of Fedora dwindled down until I had to do a full Windows reinstall due to hard drive failure and never gotten around to installing Fedora alongside Windows again. A week or so ago, I managed to utilize my sister's laptop for testing purposes, and, after removing the obsolete Windows XP installation on it, installed Fedora 22 Workstation i386 and am now using the laptop and the OS for simple router usage, as well as learning about basic networking and various options that come along with that. Since I'm currently unemployed, the spare time amount is usually quite substantial, and after another user on Freenode in #fedora pointed me to making a Fedoraproject account to be able to "fix" a typo on a wiki page, I decided that I'll try and give something back, because just by running Fedora on the laptop enabled me to actually connect to the Internet at all, since Windows doesn't want to recognize my USB modem for some reason, and that alone is worth enough for me to return the "favor" back in any way I can. As far as English language knowledge goes, written (typed), grammar and spelling wise isn't really a problem for me, I consider myself fluent in the language, owing that to a big number of English books I've read since my late elementary school years. I'm not really sure how much activity is expected/required from someone new joining the Docs project/new wiki gardeners, but I'll try to do my best if I'm accepted and hopefully I can contribute to something else to Fedoraproject in the future. That's about it as far as basic introduction goes, if you have any other questions while considering the application, don't hesitate to drop me a line (wall). Until next time, if not sooner, Primož

1 0

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )
by Pete Travis 15 Jul '15

15 Jul '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-07-16 from 12:00:00 to 13:00:00 US/Mountain The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. Source: https://apps.fedoraproject.org/calendar/meeting/434/

1 0

Fedora Docs Workflow and Publishing Improvement Project
by Brian Exelbierd 14 Jul '15

14 Jul '15

I talked with randomuser about strategy moving forward. I have written up our conversation in an interview style. The primary goal is to start some conversation around these topics. Therefore: YOUR HOMEWORK: Send an email back with the questions this raised for you Our ulterior motive is to further inform our presentation at Flock. --- To understand where we are going, we have to know where that is. *What is the goal of the docs group and docs.fedoraproject.org?* The docs group as having two basic, related goals: assisting developers, and assisting users. Our current strategy does a reasonably thorough job of assisting users, but we don't do as well with assisting developers, or new docs contributors, for that matter. There's lots of new crazy code out there, and the large book strategy has a lot of inertia and can feel stifling when it comes to new additions and rapidly changing areas. *How do we fix this?* The high-level solution is to enable developers and experienced users to write about whatever they like to do. We would use a workflow that leverages the Docs Team's greatest strength, experience. People can work with seasoned writers to produce very high-quality work. The biggest problem Docs contributors have is finding something to do, so that workflow should provide a pipeline of requests working through clearly defined steps. a request could be from a user ie https://bugzilla.redhat.com/show_bug.cgi?id=1229560 or from a developer, ie the API reference discussion, or internally generated by the docs team as a need for an upcoming release. The focus of this process should be on the quality of content and the efficacy of addressing a specifically defined topic. Someone shouldn't have to worry too much about markup or tools unless they've specifically opted to work in a markup or with the tools. This goes beyond just telling people, "You can write whatever you want however you want and get help with the publishing." That's not enough. The scope of our books is really too big to facilitate focused topical writing. The cookbook is evidence of that; Randomuser has offered cookbook assistance to many people and few take the bait. The new strategy is to build publishing/site generation tooling that supports varied content. This way contributors can range from independently capable writers, to SMEs looking to share but not learn the specifics of publishing, to requesters, to those wanting to write but needing assistance to get there. Ideally, we reach a point where each specialty group/SIG has a set of articles covering their interests, in a format that they're able to maintain. The only real example of that we have is the Amateur Radio Guide. And this is is basically single-handedly maintained by jjmcd, despite there being many other Fedora contributors doing radio stuff. This isn't ideal, but it is working for today. Rather than try to fix a working process, let's try to get more folks on-board, for example the Astronomy SIG. *How are we going to implement the solution?* Implementation is a challenge. There are two aspects, **Community** and **Tooling**. On the community side, We don't have a well conceived plan (other than sharing and organic growth - which is slow and not guaranteed). This is critical as tools are not valuable if no one uses them. We can't grow our docs if maintenance consumes all of the folks involved. With regards to tooling, we have lots of bright people and lots of ideas around tooling. Tooling is solvable and being worked on. You can contribute to and follow the progress at https://github.com/immanetize/anerist . But beforewarned, it could be be better described. *How do you envision the workflow for a new content change/addition?* The system consists of a bunch of restricted commit repos containing large guides, collections of ReST articles, whatever. When a change is committed to a repo the tooling will see the commit and attempt to generate html from the affected files. If that succeeds, (and hopefully if it passes some validation tests, the strings in Zanata (Internationalization Tool) will be automatically updated to make the work available for translation immediately. The tooling will also extract some metadata from the document (title, subtitle, abstract, categorical information, etc.) and ultimately use that to generate a stage version of the docs site for verification before publication. An individual contribution comes in via a pull request workflow. This could be via a pagure.io solution or via a traditional git clone solution. Pagure.io has the benefit of bringing the fork/edit/PR process into a web-based format perfect for many contributors and for drive-by contributors. The merge starts the process just mentioned. Ideally we can support acls on a per branch and repository basis. This way a SIG, for example, could have control of their specific documentation by merging PRs. Members of the docs-writers group would have global commit capability. The branch structure can resemble many popular open source projects with a master that is clean and release branches for future maintenance. The system is branch-aware, so everything from 'master' goes to a draft area, things in f$n gets labeled as appropriate for f$n. *What are our big blockers today?* 1. Community Outreach and Growth Plan. 2. Website redesign for docs.fedoraproject.org - it is stalled on some decisions around older docs, etc. 3. Publishing is stalled on both design and the need to integrate legacy tools such as publican in a new paradigm with other formats that use other tools. These need to all roll to a common docs listing/Table of Contents.

4 4

Fedora Docs Project Meeting Minutes 13 Jul 2015
by Petr Kovar 13 Jul '15

13 Jul '15

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by pkovar at 14:10:31 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-07-13/fedora_docs.2015… . Meeting summary --------------- * Roll Call (pkovar, 14:10:51) * New Writer Check-in (pkovar, 14:13:17) * Publishing (pkovar, 14:16:36) * https://github.com/fedora-cloud is already on github (bexelbie, 14:25:07) * ACTION: bexelbie will look further into CentOS' GSoC efforts around a doc toolchain (bexelbie, 14:31:59) * ACTION: bexelbie will look further into CentOS' GSoC efforts around a doc toolchain (bexelbie, 14:36:13) * ACTION: bexelbie will look further into CentOS' GSoC efforts around a doc toolchain (bex, 14:37:20) * Guide Status (pkovar, 14:41:00) * https://github.com/fedora-cloud is already on github (bexelbie, 14:41:03) * Open Floor (pkovar, 14:48:31) Meeting ended at 14:53:10 UTC. Action Items ------------ * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain Action Items, by person ----------------------- * bex * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * bexelbie will look further into CentOS' GSoC efforts around a doc toolchain * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bexelbie (64) * pkovar (43) * smccann (16) * lnovich (16) * wdashley (9) * zodbot (8) * pbokoc (5) * haraldh (2) * kirsti1 (1) * Southern_Gentlem (1) * bex (1) * dgilmore (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 12 Jul '15

12 Jul '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-07-13 from 14:00:00 to 15: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/371/

1 0

MEGA Invitation
by MEGA 08 Jul '15

08 Jul '15

sheldon.corey(a)gmail.com sent you an invitation to join MEGA.\n\n"; --- Message from user: --- Hello, join me on MEGA and get access to encrypted storage and communication. Get 50 GB free! --- Please create your free MEGA account by clicking on the following link:\n\n"; https://mega.nz/#newsignupZG9jc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZ3ZAvM-cRAVt Best regards, Team MEGA

1 0

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )
by Pete Travis 08 Jul '15

08 Jul '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-07-09 from 12:00:00 to 13:00:00 US/Mountain The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. Source: https://apps.fedoraproject.org/calendar/meeting/434/

1 0

Getting Started Docker/Container Guide
by Glen Rundblom 08 Jul '15

08 Jul '15

Hello, So I was pretty excited to use docker, and thought it would be a good thing to make a getting started guide for docker and linux containers but, Docker's online documentation is excellent. I am not sure if it would be a good thing to make a guide that might be obsoleted quickly when such a good support resource exists. Thoughts? Thank you, -Glen

5 7

Publican Build Error on Fedora 22
by David Ashley 08 Jul '15

08 Jul '15

Please help. After installing publican and all the needed support pieces for producing a Fedora doc on Red Hat 6.6, I built several of the standard Fedora docs successfully. But when I try this on Fedora 22 I consistently get the same error on every doc I try to build. It complains the ID of the Preface chapter already exists and halts the build. This is consistent on two Fedora 22 machines with every doc I try. Is this a known error? Is there a work-around I need? Thanks, David Ashley

4 6

Fedora docs Meeting minutes - July 6th 2015
by Sandra McCann 06 Jul '15

06 Jul '15

For your viewing pleasure: http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2… Meeting summary 1. *New Writers* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:06:00) 1. Laura is now in the US, office hours will change - all new writers who need / want assistance should stay on the #fedora-docs channel after this meeting to arrange a new meeting time that better suits the US time zone (lnovich <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:07:32) 2. *Release Notes Beats* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:07:59) 1. please take a look at the upcoming F23 changes and find something to adopt for documentation needs (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:09:58) 3. *Publican/Publishing* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:12:13) 4. *Guide Status* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:13:57) 1. email discussion on whether we need getting started guide for docker... please go read and respond (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:15:53) 2. - docker has install notes for fedora (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:19:37) 3. https://docs.docker.com/installation/fedora/ (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:19:41) 4. we need to document fedora server (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:21:50) 5. https://getfedora.org/en/server/ (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:22:02) 6. - fedora server guide needs cockpit, server roles, etc (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:22:18) 7. https://git.fedorahosted.org/cgit/docs/fedora-server-guide.git/ ( zoglesby <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:24:45) 8. ACTION: randomuser and zoglesby to discuss fedora server guide plan (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:30:17) 9. decision made to use links to docker docs in RNs for now instead of rolling our own guide (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:31:02) 5. *New User Personas* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:31:37) 1. ACTION: all - look at the personas and we'll vote to approve them at the next meeting (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:40:04) 2. https://fedoraproject.org/wiki/Docs_Project_Focus (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:40:08) 3. for personas - consider an icon for each one that we can use in tips specific to a persona in the docs (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:42:25) 6. *Outstanding BZ Tickets* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:45:39) 1. http://tinyurl.com/lbrq84 (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:45:43) 7. *Open floor discussion* (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:47:14) 1. - we could reach out to the design team for help w/ icons (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:52:06) 2. https://fedoraproject.org/wiki/Design (smccann <http://meetbot.fedoraproject.org/fedora-meeting/2015-07-06/fedora-meeting.2…>, 14:52:10)

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 05 Jul '15

05 Jul '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-07-06 from 14:00:00 to 15: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/371/

1 0

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )
by Pete Travis 01 Jul '15

01 Jul '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-07-02 from 12:00:00 to 13:00:00 US/Mountain The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. Source: https://apps.fedoraproject.org/calendar/meeting/434/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs July 2015