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, 10 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
Release Notes, and F23 Change list
by Zach Oglesby
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
8 years, 9 months
Question(s) about a starting point
by Primoz D.
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
8 years, 9 months