docs February 2015

docs@lists.stg.fedoraproject.org

15 participants
30 discussions

[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

[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

[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

RFC: docs website layout demo
by Jeff Fearn 06 May '15

06 May '15

Hi, Rudi asked me to do a demo of how Fedora could make a rebuilt docs website look, so I've made a demo site & tweaked it a bit. Before I spend too much effort on it I thought I'd open it up for input. I wanted to get a bit more done before the weekend, but time slipped away. I wanted to get it out for some feedback over the weekend so I can do some more on Monday, so I'd thought I'd just put it out there and hope people can understand it is only half baked. Some of the stuff I did for this I liked so I've started migrating the template changes back in to publican, leaving this site with just some colour changes on what a default web_style 2 site will look like. I'll update my fedora people site next week so show what a default site will look like. I've made a script to pull out most of the docs packages from git, and run through a bunch of branches per book, and try to build them with the latest publican. I'll make the script available next week for people who want to build their own copy. It should be useful to QA the process as it spits out a log file out for each repo and branch so you can get a good list of what's broken and what's not. I'll also put those up on my fedora people site next week ... If I have any quota left :D Demo site is https://jfearn.fedorapeople.org/fdocs/en-US/index.html I think this is a pretty good layout https://jfearn.fedorapeople.org/fdocs/en-US/index.html#Fedora Colours are hard :-/ Note if you click a group, below the versions, then it filters out all the other groups. Note that in the "System administration" group for Fedora 20 there is an external link "The Ways And Means Of Pants" which is a fake URL, if you have a couple of examples of real external links you'd like in that group, or any other group, I'd be happy to swap out the fake one. I haven't changed the brand XSL for the html payload, I'd like to remove the old left and right logos at the top of the pages. They aren't really needed given the menu content. e.g. https://jfearn.fedorapeople.org/fdocs/en-US/Fedora/20/html/Installation_Gui… bah I just noticed a bug on that page, the first two items in the navigation menu are swapped ... :( I'm sure there are lots more :} I've built html, html-single, epub & pdf. The site is only in en-US, it's 417M and I'm not sure the hosting people would be happy if I hosted more languages :) Anyway, it's Friday evening and the wine is calling, please reply if you have any ideas or feedback, beware that I'm currently hacking on the publican devel branch, so I might steal any really cool ideas for publican.next ;) Cheers, Jeff. P.S. All the RSS feeds on there should work, but you probably do not want to sign up for that site!

6 23

[Bug 1090755] New: Getting Started with OpenStack needs updating to F20
by Red Hat Bugzilla 04 Mar '15

04 Mar '15

https://bugzilla.redhat.com/show_bug.cgi?id=1090755 Bug ID: 1090755 Summary: Getting Started with OpenStack needs updating to F20 Product: Fedora Documentation Version: devel Component: virtualization-guide Assignee: docs(a)lists.fedoraproject.org Reporter: nuonguy(a)yahoo.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org, lnovich(a)redhat.com, zach(a)oglesby.co http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_18 So far I see that references to these might need to change: openstack-tempo mysql-server -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 3

The State of Publishing Documentation in Fedora
by Pete Travis 26 Feb '15

26 Feb '15

Hi all, I've given a lot of thought to our publishing situation. The current solution, using an unmaintained version of Publican on an unsupported Fedora release, is untenable. The site we have been maintaining in web.git is incompatible with current versions of publican, besides being massive and prone to breakage. We have been working towards a replacement, slowly. The proposed successor to web.git is an RPM based system where Publican creates SRPMs of the guides, Fedora's koji buildsystem builds packages from the RPMs, and a VM instance installs the package to build the site. Creating the SRPM would be analagous to the `publican build --embedtoc ...` from the old process, and when the VM installs the package, it does the `publican install-book` step of the process. We currently have the koji infrastructure in place, a mostly viable way for newly built packages to automatically be installed on the VM, and a functional but mostly vanilla site frontend. Along the way, I've identified a few caveats to this method, to which I'll add some general observations: - Each language of each release of each guide is a unique package. To publish anything new, we must coordinate with releng to have the package defined in koji. Releng is already overburdened. - Each language must have a separately maintained revision history. - The buildroot shared by koji and the VM required updated versions of publican and publican's dependencies, and now must be maintained there (which is currently not happening afaik). - None of the breakage problems we've dealt with in web.git will go away. Unusual language codes, bad draft procedures, wonky *_Info.xml issues, and whatever black magic that ends with my manually running sqlite invocations against the site db - that's all still there. - The site frontend needs to be completely redesigned from the ground up, and we have not demonstrated the motivation to see that through. There are intricacies here that we didn't discover from a straightforward following of the publican user's guide, and many subjectively frustrating surprises. - A publican website can only publish publican-friendly content. To the best of my knowledge, that means docbook only. Our contributor base is declining, and prospective contributors have consistently demonstrated a lack of interest in writing docbook. - A publican website does not provide an effective presentation of many smaller articles. I've been disagreed with on this point, and will concede that it's definitely possible to have 200 things under that F21 category, but I maintain that presentation in that way would be inimical to reader browsing. With all this in mind, I've decided to be honest with myself, and you, in saying that I'm not motivated to make the publican website frontend work. Something must be done to deal with our site's incompatibility with current Publican, but from a usage perspective, I feel like there's a very high upfront investment - and a moderate continuing investment in maintaining the el6-docs koji repo - with no substantial gain in the product delivered. For normal usage, we've simply replaced `publican build;publican install-book` with `publican package;koji build`. Rudi had initially volunteered to do *all* of the setup to make this work, but he's a busy guy and it really isn't fair to expect him to deal with that level of implementation for us. We've tossed around ideas in #fedora-docs, and in discussing it, I've developed a wishlist for an improved publishing platform: - We use release-based branches to maintain content for a given Fedora release. Anything committed to these branches is intended for publication, so that should happen automatically. - It should be simpler to make drafts available. If we can automate publishing on release branches, we can do the same with master. - We don't do as good of a job as we should with pushing and pulling strings from translation. Pushes and pulls could be automated. - There should be an effective way to publish and organize sundry articles. - The publishing platform should be able to process arbitrary markup formats. I think docbook is great, and publican does a good job with it, but there will be room for more contributions if that isn't mandatory. - The frontend of the site should be adaptable. docs.fp.o would ideally use the same design elements as other official Fedora sites for a more unified appearance. - Some validation on commits would be nice. The working theory at this point is to use a continuous integration system like Jenkins to automate builds. I've had a Jenkins instance running locally this week, with new builds triggered via fedmsg signals generated by our commits. This part works smoothly, with the exception of a fedwatch bug that I've crudely worked around, but triggers using python-fedmsg really wouldn't be too difficult. The infra folks are also working on a Jenkins setup, so there's potential to share experience and buildslaves. Turning that into a browseable frontend is more immediately viable than you might think; http://sourceforge.net/projects/jenkinscat/ is designed just for that and can be customized for our needs. Jenkins plugins to cycle strings from Zanata, or some other method, could come down the road. There's room for other enhancements, too. The CI idea is something I'm excited about, and motivated to work on. I'd love to spend that time working with others, if you're interested. --Pete -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

8 18

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

25 Feb '15

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

Need help getting running with git on virtualization getting started
by Sandra McCann 24 Feb '15

24 Feb '15

Hi Folks - I recently volunteered to help out with the virtualization getting started guide. After a bit of help in chat today, I learned i needed to ssh not https:// to clone the guide. When I do this, I get an error that I could not read from the repository and should check my access rights. A bit more poking and it looks like I need to be in the doc-writers group but I'm not. my FAS account is under mccann2. Can someone help with that, or let me know if there's something else I should be doing? I used the following: git clone ssh:// mccann2(a)git.fedorahosted.org/cgit/docs/virtualization-getting-started-guide.git/ (with and without the mccann2) and got the access error both ways. Thanks, Sandra

3 2

Docs Project Meeting Minutes 23 Feb 2015
by Petr Bokoc 23 Feb '15

23 Feb '15

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:01:02 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-02-23/fedora_docs.2015… . Meeting summary --------------- * Roll Call (randomuser, 14:01:02) * New Writers (randomuser, 14:06:02) * Publishing (randomuser, 14:09:30) * ACTION: everyone elaborate on personas and appropriate documentation at https://fedoraproject.org/wiki/Docs_Project_Focus (randomuser, 14:28:52) * ACTION: randomuser to draft server list (randomuser, 14:30:07) * ACTION: pkovar to add env-and-stacks list (randomuser, 14:31:00) * ACTION: lnovich to write general user list (randomuser, 14:32:39) * LINK: https://fedoraproject.org/wiki/Marketing- see projects (bexelbie, 14:34:21) * ACTION: bexelbie will reach out to Marketing about their userstores (bexelbie, 14:34:37) * it would be great if someone could develop cloud personas (randomuser, 14:38:45) * Release Notes & Schedule (randomuser, 14:40:41) * LINK: https://fedorapeople.org/groups/schedule/f-22/f-22-docs-tree-tasks.html (randomuser, 14:40:49) * HELP: claim your beats! (randomuser, 14:41:38) * LINK: https://fedoraproject.org/wiki/Category:Documentation_beats?rd=Docs/Beats (randomuser, 14:42:23) * to take ownership of writing about a change, assign yourself as the "Docs Contact" on the change tracking bug (randomuser, 14:44:00) * LINK: https://fedoraproject.org/wiki/Releases/22/ChangeSet#Fedora_22_Accepted_Sys… (randomuser, 14:46:34) * LINK: https://fedoraproject.org/wiki/Releases/22/ChangeSet#Fedora_22_Accepted_Sys… (randomuser, 14:46:40) * https://fedorapeople.org/groups/schedule/f-22/ has calendar files you can import to your favorite scheduling solution to track the release schedule (randomuser, 14:50:19) * Open Floor Discussion (randomuser, 14:53:22) Meeting ended at 15:00:25 UTC. Action Items ------------ * everyone elaborate on personas and appropriate documentation at https://fedoraproject.org/wiki/Docs_Project_Focus * randomuser to draft server list * pkovar to add env-and-stacks list * lnovich to write general user list * bexelbie will reach out to Marketing about their userstores Action Items, by person ----------------------- * bexelbie * bexelbie will reach out to Marketing about their userstores * lnovich * lnovich to write general user list * pkovar * pkovar to add env-and-stacks list * randomuser * randomuser to draft server list * **UNASSIGNED** * everyone elaborate on personas and appropriate documentation at https://fedoraproject.org/wiki/Docs_Project_Focus People Present (lines said) --------------------------- * randomuser (86) * bexelbie (55) * lnovich (31) * apatel_ (19) * pbokoc (5) * smccann_ (5) * pkovar (5) * zodbot (4) * jreznik (4) * jsmith (3) * rkratky (1) * bara_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs February 2015