June 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 02 Sep '17

02 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 02 Sep '17

02 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 06 Nov '15

06 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

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

15 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

F23 Accepted Changes
by Pete Travis 30 Jun '15

30 Jun '15

Fedora developers are busy preparing for the Fedora 23 Release. At this point in the release cycle, major changes are planned using a scheme called a "Change". Changes are either "Self-Contained", where the impact is limited to the proposed packages and coordination with other developers or Fedora teams is minimal, or "System Wide", which affects a number of interrelated packages and requires coordination from other teams such as QA or release engineering. For both types, the Fedora Docs team will follow the development and implementation of each Change and summarize it for the Release Notes. Volunteer writers 'own' each change by taking the Docs Contact designation in the Change tracking bug, and coordinating documentation with the Change owners. Writing these up is a relatively straightforward, well defined task that's ideally suited for new Docs contributors. The proposals are discussed at length on the devel(a)lists.fedoraproject.org mailing list and in FESCo meetings. Some topics might be unfamiliar to you, but don't let that be a roadblock - the writing is targeting uninitiated readers, so your perspective is in a good place. Without further editorializing, I present the list of approved Changes so far. Please take the opportunity to get started early! Fedora 23 Accepted System Wide Changes Proposals These changes have been accepted by the Fedora Engineering Steering Committee <https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee> for the Fedora 23 Release as System Wide Changes. <https://fedoraproject.org/wiki/Category:SystemWideChange> Harden All Packages <https://fedoraproject.org/wiki/Changes/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. You can compare the security by running the following as root: Owners - Owner: Till Maas | Moez Roy | Florian Weimer - Release notes owner: Tracking - Last updated: 2015-02-12 - Tracking bug: #1215939 <https://bugzilla.redhat.com/show_bug.cgi?id=1215939> - Original tracking bug: #1199775 <https://bugzilla.redhat.com/show_bug.cgi?id=1199775> - Status: Change accepted Mono 4 <https://fedoraproject.org/wiki/Changes/Mono_4> Update the Mono stack in Fedora from 2.10 to 4.* Owners - Owner: Claudio Rodrigo Pereyra Diaz - Release notes owner: Tracking - Last updated: April 29, 2015 - Tracking bug: #1221559 <https://bugzilla.redhat.com/show_bug.cgi?id=1221559> - Status: Change accepted Disable SSL3 and RC4 by default <https://fedoraproject.org/wiki/Changes/RemoveSSL3andRc4> 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. Owners - Owner: Nikos Mavrogiannopoulos - Release notes owner: Tracking - Last updated: 2015-04-28 - Tracking bug: #1220679 <https://bugzilla.redhat.com/show_bug.cgi?id=1220679> - Status: Change accepted Perl 5.22 <https://fedoraproject.org/wiki/Changes/perl5.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. Owners - Owner: Petr Písař - Release notes owner: Tracking - Last updated: 2015-04-28 - Tracking bug: #1220680 <https://bugzilla.redhat.com/show_bug.cgi?id=1220680> - Status: Change accepted Default Local DNS Resolver <https://fedoraproject.org/wiki/Changes/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. Owners - Owner: P J P | Pavel Šimerda | Tomas Hozza | Petr Špaček - Release notes owner: Tracking - Last updated: 2015-05-28 - Tracking bug: #1182488 <https://bugzilla.redhat.com/show_bug.cgi?id=1182488> - Status: Change accepted Fedora 23 Boost 1.59 Uplift <https://fedoraproject.org/wiki/Changes/F23Boost159> 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. Owners - Owner: Jon Wakely - Release notes owner: Tracking - Last updated: 2015-06-07 - Tracking bug: #1229030 <https://bugzilla.redhat.com/show_bug.cgi?id=1229030> - Status: Change accepted Fedora 23 Accepted Self Contained Changes Proposals These changes have been accepted by the Fedora Engineering Steering Committee <https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee> for the Fedora 23 Release as Self Contained Changes. Cinnamon Spin <https://fedoraproject.org/wiki/Changes/Cinnamon_Spin> A Fedora Spin using the Cinnamon desktop environment. - Owner: Dan Book - Last updated: 2015-05-06 - Completed: no <https://bugzilla.redhat.com/show_bug.cgi?id=1225865> System Firmware Updates <https://fedoraproject.org/wiki/Changes/SystemFirmwareUpdates> This change is to add the ability to perform firmware updates on UEFI machines. - Owner: Richard Hughes - Last updated: 2015-06-03 - Completed: no <https://bugzilla.redhat.com/show_bug.cgi?id=1230554> Cockpit GUI for Domain Controller Role <https://fedoraproject.org/wiki/Changes/Cockpit_Domain_Controller_GUI> Provide a graphical mechanism for deploying a FreeIPA Domain Controller on Fedora Server through the Cockpit administrative console. - Owner: Stephen Gallagher, Stef Walter - Last updated: 2015-06-18 - Completed: no <https://bugzilla.redhat.com/show_bug.cgi?id=1233098> Containerized Server Roles <https://fedoraproject.org/wiki/Changes/Containerized_Server_Roles> Enhance rolekit to be able to deploy Server Roles using the Nulecule Container Specification. - Owner: Stephen Gallagher - Last updated: 2015-06-18 - Completed: no <https://bugzilla.redhat.com/show_bug.cgi?id=1233099> Frappe Framework <https://fedoraproject.org/wiki/Changes/frappe-framework> A full-stack web framework based on Python and Javascript to help you build powerful business apps and nifty extensions. - Owner: Eduardo Mayorga , William Moreno - Last updated: 2015-06-18 - Completed: no <https://bugzilla.redhat.com/show_bug.cgi?id=1233101> Category:ChangeAcceptedF23 <https://fedoraproject.org/wiki/Category:ChangeAcceptedF23> and Category:SelfContainedChange <https://fedoraproject.org/wiki/Category:SelfContainedChange> -- Pete

2 1

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 29 Jun '15

29 Jun '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-06-29 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

Re: Virt getting started guide chapters (Glen Rundblom)
by Laura Novich 25 Jun '15

25 Jun '15

Hi Glen, Thank you for the great idea about Docker and Container virtualization. Yes we need to document it, but at the moment I would like to finish editing/auditing our current TOC. I am not convinced that containers should be in the same guide as virtualization Getting Started as it will make this guide bigger than it needs to be. I would love to discuss with you a manual on Containers/Docker so please drop in on my Office Hours on Wed @ 1300UTC Best Regards, Laura ==================== >I like the idea of a 'why to use virtualization'. This will be very handy >if we do put docker in that guide. >I'd like to see docker documented, the question I have (being a total noob >for containers) - would someone looking for docker go to a virtualization >guide?? >Sandra >On Fri, Jun 19, 2015 at 8:10 AM, Glen Rundblom <glen(a)rundblom.com> wrote: >> Hello, >> I was looking over the wiki page outline for the virtualization getting >> started guide, and thought two things: >> >> 1. Do we need a chapter (3) on why someone should use virtualization >> 2. I think we should include a chapter about Docker >> >> I was thinking about Docker because to overcome the publican problems in >> Fedora22 I built a Fedora21 image with publican so I can build the guides. >> It occurred to me that it probably should be in the guide as well. >> >> Respectfully, >> -Glen >> > -- > docs mailing list > docs(a)lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/docs

3 2

Initial commit and push for the Libvirt Application Development Guide Using Python
by David Ashley 25 Jun '15

25 Jun '15

All - I have made the initial commit and push for the Libvirt Application Development Guide Using Python document. You can pull it with git clone git://git.fedorahosted.org/git/docs/libvirt_application_development_guide_u… This is a straight up version of the docs I got from the libvirt team with some style changes that put them more in line with Fedora docs. Mainly I removed two chapters that will not be covered in this guide and modified a lot of the IDs and LINKEND links to be better references. The main content is unmodified. I will now begin the conversion process from a C guide to a Python guide. It will involve replacing all the C examples with Python examples and modifying the text to match that replacement. There are lots of blank spaces to be filled in that the libvirt team never got around to. After converting the existing stuff I will see what I can do about filling in those spaces. As always, if you have a interest in this guide feel free to jump in and help at any time. David Ashley

1 0

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

25 Jun '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-06-25 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

Minutes from Laura's Office Hours
by Laura Novich 24 Jun '15

24 Jun '15

Minutes can be found here http://meetbot.fedoraproject.org/fedora-docs/2015-06-24/fedora-docs.2015-06… Thanks to all those who participated! -- Regards, Laura Novich ****************************************************** * Laura Novich * * RHCSA (Red Hat Certified System Administrator) * * * * Content Author, Platform Virtualization / KVM * * Customer Content Services (CCS) * * Red Hat EMEA, Ra'anana Israel * * * * Phone: +972 9 7692397 * * Direct:72397 * * Fax: +972 9 7692223 * * Mobile: +972 54 7693489 * * * * IRC: lnovich * * * ******************************************************

1 0

Virt getting started guide chapters
by Glen Rundblom 23 Jun '15

23 Jun '15

Hello, I was looking over the wiki page outline for the virtualization getting started guide, and thought two things: 1. Do we need a chapter (3) on why someone should use virtualization 2. I think we should include a chapter about Docker I was thinking about Docker because to overcome the publican problems in Fedora22 I built a Fedora21 image with publican so I can build the guides. It occurred to me that it probably should be in the guide as well. Respectfully, -Glen

2 2

[Bug 989059] New: PDF file content has been located at right half of page.
by Red Hat Bugzilla 22 Jun '15

22 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=989059 Bug ID: 989059 Summary: PDF file content has been located at right half of page. Product: Fedora Documentation Version: devel Component: virtualization-getting-started-guide Assignee: dayleparker(a)redhat.com Reporter: dmitry_orekhov(a)mail.ru QA Contact: docs-qa(a)lists.fedoraproject.org CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org Description of problem: All content has been located at right half of page. http://docs.fedoraproject.org/en-US/Fedora/19/pdf/Virtualization_Getting_St… http://docs.fedoraproject.org/en-US/Fedora/19/pdf/Virtualization_Security_G… http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Virtualization_Administra… http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Virtualization_Getting_St… http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Virtualization_Security_G… -- 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=VOIn7kVZqu&a=cc_unsubscribe

1 1

Meeting Summary Laura's Office Hours June 17
by Laura Novich 22 Jun '15

22 Jun '15

Meeting about Virtualization in Fedora Documentation (04:07:15 PM) lnovich: I'm here (04:07:59 PM) lnovich: i am not sure how to start a meeting, so let's begin? (04:09:11 PM) grundblom: neat, I think we were discussing the virtualization guide, I pulled it down and I see the last commit from June 1 2014 by Pete Travis, do I have the correct one? (04:09:27 PM) ruigo_ [rgouveia@nat/redhat/x-ulytgqsqbmktyizi] entered the room. (04:09:30 PM) lnovich: need to distinguish with a brief history (04:09:45 PM) lnovich: there is more than one virtualization guide (04:09:53 PM) suehle left the room (quit: Ping timeout: 255 seconds). (04:09:58 PM) ruigo left the room (quit: Read error: Connection reset by peer). (04:10:23 PM) grundblom: sure: (04:10:24 PM) lnovich: so we need to be specific. - I created a guide about a year ago called the virtualization deployment and administration guide (04:10:44 PM) lnovich: it WAS up to date for Fedora 19/20 (04:11:02 PM) lnovich: and should have been published at the time - it was left in draft state (04:11:14 PM) lnovich: then there is the virtualization guide (04:11:20 PM) lnovich: which should be much older (04:12:08 PM) lnovich: what Pete did I don't recall (04:12:42 PM) grundblom: Oh, so I might be looking at the wrong guide (04:13:09 PM) lnovich: i kind of pulled out of the project so I am not sure what happened during my absence (04:13:18 PM) p_ondrejka [peter@nat/redhat/x-sczvefygzvjhkrdl] entered the room. (04:13:54 PM) lnovich: randomuser would /should know (04:14:01 PM) grundblom: So in the last docs meeting, we were discussing focusing attention on it right? or did I misinterpret that? (04:14:02 PM) grundblom: or at least on one of them.. (04:14:11 PM) lnovich: yes (04:14:12 PM) mccann [4281f10a(a)gateway/web/freenode/ip.66.129.241.10] entered the room. (04:14:30 PM) lnovich: that was right we were discussing adding new content (04:14:49 PM) lnovich: I haven't seen this content and don't know where it has been discussed to add it (04:15:01 PM) ruigo_ left the room (quit: Ping timeout: 265 seconds). (04:15:27 PM) mccann left the room (quit: Client Quit). (04:15:46 PM) smccann [4281f10a(a)gateway/web/freenode/ip.66.129.241.10] entered the room. (04:15:55 PM) grundblom: Well the virt-getting-started guide has had some updates, smccann and I have been working on it.. I think that is some of the new content (04:16:03 PM) lnovich: ok (04:16:12 PM) lnovich: that is an excellent place to start (04:16:26 PM) smccann: sorry to join late (04:16:30 PM) lnovich: have the changes been committed? (04:16:46 PM) lnovich: do you have an outline somewhere on a wiki page? (04:18:03 PM) grundblom: that I do not know, I myself did not make an outline, my last commits to the virt-getting-started guide were just before F22 release (04:18:19 PM) lnovich: nevermind found the guide (04:19:37 PM) grundblom: I was hoping to bring some of the boxes content from the virt-getting-started guide to the virt guide, but, I am now wondering which guide it would be appropriate for (04:19:58 PM) lnovich: understand your confusion (04:20:11 PM) Capesteve: lnovich: check the branches, I think smccann has been committing to a branch (04:20:15 PM) lnovich: let's first of all take a look at the getting started guide (04:20:21 PM) smccann: his changes and mine were published with F22 (04:20:40 PM) smccann: Capesteve - I graduated to master branch before the f22 release :-) (04:20:57 PM) lnovich: ok back to what I was saying? (04:20:59 PM) smccann: So what's out on the web is the latest/greatest on the virt getting started (04:21:06 PM) lnovich: yes (04:21:14 PM) lnovich: it should be (04:21:26 PM) Capesteve: oh, good news :) (04:21:41 PM) jreznik left the room (quit: Quit: Konversation terminated!). (04:21:50 PM) lnovich: the getting started guide needs some more revisions to change it into something better (04:22:14 PM) smccann: ok feedback always welcome! (04:22:46 PM) lnovich: this is no fault to you, but we should decide how this guide is going to be planned (04:22:53 PM) lnovich: what information is to stay/ leave (04:22:58 PM) lnovich: and what needs to be addede (04:23:00 PM) lnovich: added (04:23:33 PM) smccann: what's the best way to track your recommendations? bugs? wiki page? email list? (04:23:34 PM) jreznik [jreznik@nat/redhat/x-zwxsnhnkkvemkwte] entered the room. (04:23:39 PM) lnovich: if this is a getting started all it needs is 1 a brief intro and 2 a quick start (04:24:03 PM) lnovich: HOWEVER - if this is to become an Installation guide - that is something else all together (04:24:15 PM) lnovich: that choice is up to you (04:24:29 PM) smccann: i'd like to keep it a getting started - for the newbie who just wants to bring up a VM and use it. (04:24:50 PM) lnovich: the virtualization deployment and admin guide is much more comprehensive (04:25:05 PM) lnovich: ok so a newbie needs more info (04:25:22 PM) lnovich: chapter 2 is in need of several things (04:25:46 PM) lnovich: we need to explain what a hypervisor is (04:25:55 PM) ruigo_ [rgouveia@nat/redhat/x-whkerbzuyeoftdor] entered the room. (04:26:00 PM) lnovich: what guests/hypervisors are supported (04:26:15 PM) lnovich: and what the possibilities are in combination (04:27:04 PM) lnovich: we should also explain how devices are emulated (04:27:30 PM) smccann: hmm... does a newbie wanting to bring up a VM really need the emulation details? (04:27:44 PM) lnovich: no but they won't know it is possible to do so (04:27:56 PM) lnovich: not the nitty gritty details (04:27:59 PM) smccann: k so just a brief intro to it (04:29:16 PM) lnovich: we should probably put these ideas into a wiki page somewhere (04:30:14 PM) smccann: yeah I'm taking notes I can move to a wiki but how do I decide where to put it? (04:30:43 PM) lnovich: I'll set up a page (04:31:10 PM) smccann: kk (04:31:10 PM) grundblom: Thats what I was thinking, I didnt know if there were Fedora wiki guide change pages.. (04:33:25 PM) mnavrati left the room (quit: Ping timeout: 264 seconds). (04:37:50 PM) grundblom: smccann does the current virt getting started guide build for you? (04:38:39 PM) smccann: it did before I upgraded to f22. I noticed it didn't after that, but wondered if I'd messed up my upgrade. I haven't gone back to check (04:39:06 PM) smccann: and I'm not on that machine right now. IF you are also having issues, then it wasn't my upgrade that messed it up. I'll poke at it later (04:39:09 PM) grundblom: Yeah it does not build on my F22 box, I did a nuke and pave install.. (04:39:26 PM) ***randomuser sips coffee (04:39:37 PM) smccann: hmm. there was something somewhere about publican perhaps having issues in f22... sound familiar to anyone here? (04:39:42 PM) randomuser: there is a known libxml2 bug affectiong f>21 (04:40:01 PM) randomuser: the spelling is at the bottom of the mug (04:40:09 PM) smccann: randomuser - so we should continue to build on F21 only? (04:41:49 PM) grundblom: hrm, I missed that bug.. (04:41:59 PM) pbokoc: you could make a VM :) (04:42:05 PM) pbokoc: or a container (04:42:30 PM) randomuser: CC yourself on https://bugzilla.redhat.com/show_bug.cgi?id=1199396 to start (04:42:36 PM) smccann: AAAHAHAH!!! (04:42:42 PM) grundblom: We could make a F21 box in our F22 install to make documentation for F22 (04:42:58 PM) randomuser: I've been using yelp to preview and a vm for proofing (04:43:02 PM) smccann: yes, pbokoc and grundblom, we could! (04:43:20 PM) grundblom: I am going to need more hard drive space and ram... (04:43:41 PM) randomuser: but really, get on that bug. The package maintainer gets a notification every time, often more CCs is treated as an escalation (04:43:51 PM) bexelbie: consider using a docker container to run publican (04:44:00 PM) bexelbie: yruseva, almost has a container completed ^^ (04:44:23 PM) ***bexelbie does it with some other publishing tools that are "fragile" or want a crap-ton of dependencies I don't want on my main box (04:45:14 PM) smccann: erm.. new to docker, where do we document that for fedora? :-) (04:45:22 PM) p_ondrejka left the room (quit: Quit: Leaving). (04:46:39 PM) pbokoc: Docker documents that for Fedora :) https://docs.docker.com/installation/fedora/ (04:46:58 PM) lnovich: nested virtualization is working in F22? (04:47:18 PM) mnavrati [milan@nat/redhat/x-qzmvvzhysisrczbg] entered the room. (04:48:15 PM) randomuser: iirc you have to do something extra to make it work, lnovich, but it's been a few years since I've tried (04:48:42 PM) Corey84: nested as in vm in a vm ? (04:48:52 PM) lnovich: Corey84: yes (04:49:11 PM) lnovich: otherwise you won't be able to install a vm on a vm (04:49:22 PM) bexelbie: docker is installed by default (04:49:25 PM) p_ondrejka [peter@nat/redhat/x-oeefiklypuszmtut] entered the room. (04:49:30 PM) bexelbie: in F21 and F22 iirc (04:49:32 PM) smccann: there was something in BIOS to check/change i think (04:49:54 PM) grundblom: Ok, so for my take-aways I have: 1. Install Docker and get the publican tools from F21 working so I can build again, (04:50:25 PM) lnovich: ok so something more to add to the guides (04:50:30 PM) bexelbie: grundblom, if you are going to get the tools working you can use a VM and not have to learn Docker - in the future yruseva should have a container we can use (04:50:30 PM) grundblom: lnovich is making a wiki page for an outline on what we need to do for the virt-getting-started guide to be able to bring its content to a more comprehensive guide.. (04:50:36 PM) ***bexelbie may be able to push her a bit this week :D (04:50:46 PM) lnovich: push who? (04:51:01 PM) Corey84: i've recently done docker with vm but not vm in vm (04:51:03 PM) lnovich: you better have very long arms.... (04:51:27 PM) lnovich: randomuser: do you have a suggestion where to put this wiki page? (04:51:45 PM) kamdard [~kamdard(a)pool-173-74-70-108.dllstx.fios.verizon.net] entered the room. (04:52:23 PM) randomuser: hmm? what wiki page? (04:52:37 PM) bexelbie: push yruseva (04:53:05 PM) lnovich: randomuser: (04:50:30 PM) grundblom: lnovich is making a wiki page for an outline on what we need to do for the virt-getting-started guide to be able to bring its content to a more comprehensive guide.. (04:53:33 PM) randomuser: ah (04:54:02 PM) randomuser: call it, erm, "Virt Getting Started Guide Planning" ? (04:54:12 PM) lnovich: no i mean where as in url (04:55:00 PM) p_ondrejka left the room (quit: Quit: Leaving). (04:56:04 PM) randomuser: https://fedoraproject.org/wiki/Virt_Getting_Started_Planning (04:56:19 PM) randomuser: fp.o/wiki/page_name (04:56:28 PM) lnovich: ok works for me! (04:56:30 PM) lnovich: thanks (04:58:36 PM) smccann: should we create one for the virt deploy guide as well and start collecting ideas there too? (04:58:45 PM) lnovich: sure (04:59:14 PM) mnavrati is now known as mnavrati_mtg (04:59:24 PM) slevine [~slevine(a)c-68-47-109-163.hsd1.mn.comcast.net] entered the room. (05:01:23 PM) smccann: https://fedoraproject.org/wiki/Virt_Deploy_Admin_Planning (05:01:32 PM) lnovich: nice one smccann! (05:02:02 PM) smccann: it's my first created wiki page... I wonder if I get a badge for this! (05:02:14 PM) ***smccann collects badges for motivation (05:02:14 PM) lnovich: smccann++ (05:02:20 PM) zodbot: lnovich: Karma for smccann changed to 2: https://badges.fedoraproject.org/tags/cookie/any (05:02:42 PM) grundblom: Well done! (05:03:34 PM) smccann: aw shucks... thanks :-) (05:03:34 PM) kushal [~kdas(a)103.249.88.135] entered the room. (05:03:44 PM) kushal left the room (quit: Changing host). (05:03:44 PM) kushal [~kdas@fedora/kushal] entered the room. (05:04:16 PM) lnovich: ok listen - i have 2 more meetings back to back and need to grab a drink before I go to the meeting room (05:04:26 PM) lnovich: i will start the wiki page. (05:04:56 PM) smccann: okay thanks for all the help! (05:04:59 PM) lnovich: please put your comments in as a different color so i can track them (05:05:14 PM) lnovich: or mark who it is making the comment /change (05:06:21 PM) grundblom: Great, thanks lnovich and smccann! (05:06:38 PM) lnovich: next wed, same bat time same bat channel? (05:06:56 PM) smccann: sounds good (05:07:03 PM) grundblom: Sounds like a plan (05:07:15 PM) ***lnovich waves good bye -- Regards, Laura Novich ****************************************************** * Laura Novich * * RHCSA (Red Hat Certified System Administrator) * * * * Content Author, Platform Virtualization / KVM * * Customer Content Services (CCS) * * Red Hat EMEA, Ra'anana Israel * * * * Phone: +972 9 7692397 * * Direct:72397 * * Fax: +972 9 7692223 * * Mobile: +972 54 7693489 * * * * IRC: lnovich * * * ******************************************************

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 22 Jun '15

22 Jun '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-06-22 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

Code Examples in Documents
by David Ashley 22 Jun '15

22 Jun '15

All - In the past when creating a new document that will contain code examples in C/C++ or Python I always placed the examples in separate files from the main XML. This way it would be easier to test those examples to make sure that they work as intended. Being new to the Fedora Docs team I have looked at some of the current documents and they do not seem to separate the code from the document itself. So I am wondering if I should follow that convention or separate the code from the XML like I have done in the past? Please provide some guidance. David Ashley

4 7

Publican fails the mass rebuild
by William Moreno 22 Jun '15

22 Jun '15

Looking at the mass rebuild process in koji looks than publican build is failled :( http://koji.fedoraproject.org/koji/taskinfo?taskID=10140653 William Moreno Reyes http://about.me/williamjmorenor

2 1

Starting Point for the Python libvirt Application Development Guide
by David Ashley 19 Jun '15

19 Jun '15

All - I got permission from the libvirt team to use a document they started some years ago but never finished. I took the source as-is, except for changing the brand to fedora, and compiled it into a PDF. You can review it by downloading the PDF at https://fedorapeople.org/groups/docs/libvirt-0.9-Application_Development_Gu…. I propose to use and extend this document (using Python instead of C examples) to produce a document that can be maintained by the Fedora Docs team as well as the libvirt team. The libvirt team would be willing to review and supply patches for the new document as needed. Please take a look at the document and post your comments on the mailing list. Thanks, W. David Ashley

1 0

[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide
by Red Hat Bugzilla 18 Jun '15

18 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=846864 Bug ID: 846864 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: unspecified Version: devel Priority: unspecified CC: docs(a)lists.fedoraproject.org Assignee: laine(a)redhat.com Summary: Need a list of toolsets and when they are appropriate in the virt Getting Started guide Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: laine(a)redhat.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: virtualization-getting-started-guide Product: Fedora Documentation The Getting Started Guide needs an overview of all the different toolsets, and when each would be appropriate. In particular I'm talking about the following: 1) gnome-boxes 2) virt-manager 3) virsh, virt-install 4) ovirt 5) Should we point some people to OpenStack? I will write up a first draft of this, and hand it to a qualified docs person to edit and correctly place in the guide. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

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

18 Jun '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-06-18 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 15 Jun '15

15 Jun '15

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

Next Guide to work on
by Glen Rundblom 14 Jun '15

14 Jun '15

Good evening everyone, I have missed the last couple of meetings. Pete you mentioned that I could help with the multi-boot guide, is that still the guide you would like me to work on? Any points or directions you would like me to go with it? Thanks! -Glen

3 3

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

11 Jun '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-06-11 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 08 Jun '15

08 Jun '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-06-08 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 04 Jun '15

04 Jun '15

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2015-06-04 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

Membership Application
by David Ashley 02 Jun '15

02 Jun '15

Please add me to the docs group. David Ashley (Fedora user wdashley)

2 1

My Introduction
by David Ashley 01 Jun '15

01 Jun '15

Hello everyone - My name is David Ashley and I want to contribute to the Fedora Docs Project. I have been creating and maintaining documentation in DocBook for over 10 years and I have been using Publican to publish those works for about five years. I have a small amount of experience with MediaWiki but that was a few years ago. A lot of the documentation I have been a part of is available online and I am willing to share the URLs when asked. I also have the following skills: - average C/C++ programmer - average Python programmer - average HTML and CSS coder (web site maintainer and Apache admin) - KVM/QEMU admin for 50 VMs on a single server - maintaining a production system for nightly builds of both docs and program RPMs/DEBs on multiple operating systems - ex-Project Lead for the ooRexx Project (www.oorexx.org) I have also been using Fedora almost continuously since the first release. I also have experience with Red Hat, Suse, CentOS, Ubuntu, Linux Mint, and a few other distributions. Obviously I am looking for a sponsor and something to start work on. I am flexible and have a fair amount of time to contribute. Please let me know what I need to do to get started. Thanks, David Ashley (Fedora user wdashley)

2 2

Re: [Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 01 Jun '15

01 Jun '15

On May 31, 2015 8:00 PM, <immanetize(a)fedoraproject.org> wrote: > > Dear all, > > You are kindly invited to the meeting: > Fedora Docs Weekly Meeting on 2015-06-01 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/ > > -- I have a conflict and will not be able to attend this meeting. Can someone who is attending please guide it through the agenda? --Pete

1 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by Pete Travis 01 Jun '15

01 Jun '15

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2015-06-01 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

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 June 2015