Orphaning FreeIPA guide
by Martin Kosek
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.
7 years, 8 months
introduction - Ryan
by Ryan Gough
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
7 years, 11 months
[fedora-badges] #259: Fedora Cookbook Contributions
by fedora-badges
#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
8 years, 1 month
[Bug 1008149] New: Contraficting info about the need of shared storage for storing guest images to be migrated
by Red Hat Bugzilla
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...
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
8 years, 5 months
[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide
by Red Hat Bugzilla
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.
8 years, 10 months
RFC: docs website layout demo
by Jeff Fearn
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_G...
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!
8 years, 11 months
Standardized documentation metadata
by Pete Travis
Hi all,
I'm working through the logistics of consuming arbitrary markup
formats. It would be helpful to have a standardized way to describe a
document. The example below is YAML, because it is easy to digest,
write, and read, and I think the structure covers the important
attributes without being cumbersome.
---
title: Example Document
stub: A representation of a document description standard.
abstract: >
This could be an example document.
It could explain example documents.
It could use examples to explain what a document is.
It is none of these.
author:
- Carlton Bentleby
- Vizek Glibensky
- Obvious Pseudonym
taxonomy:
theme: Contributions
scope: Documentation
track: Metadata
project: anerist
tags:
- yaml
- metadata
- proposal
- standard
---
title, stub, and abstract are self-apparent.
Author seems like a MAY item; for a standard to go further than our
group, it'll need that, but staking a line around a collaborative work
MAY discourage collaboration.
The taxonomy can be in any order, but in function it's hierarchical;
theme at a very abstract level, scope being more refined, track gets
down to a specific topic. The project differentiates between different
approaches to addressing a given topic (and hey, people _will_ look for
answers on a specific solution).
Tags give some SEO value, could help crossreferences, site search
features... all that stuff that tags do.
What do you think? How can it be better?
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
9 years
May not make the meeting today
by Glen Rundblom
Hello, I may not be able to make the meeting today, however I have made
some big strides on the Boxes part of the Virtualization getting started
guide. I would appreciate if anyone had the time to review it and
comment on my progress.
Thank you,
-Glen
9 years
