[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, 4 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, 9 months
[Bug 627417] New: docs.fp.o landing page needs 'Start here' note!
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: docs.fp.o landing page needs 'Start here' note!
https://bugzilla.redhat.com/show_bug.cgi?id=627417
Summary: docs.fp.o landing page needs 'Start here' note!
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: nathan.thomas(a)peacenik.co.uk
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com,
nb(a)fedoraproject.org
Classification: Fedora
Description of problem:
We have a large variety of documentation guides serving a wide range of
different users. It may be difficult for users arriving at docs.fp.o to know
where to start, especially if they are new to Fedora/Linux and are unfamiliar
with some of the technical terms.
A note on the landing page suggesting a sensible starting point for new users
could help alleviate this problem. Eg:
"New to Fedora? You can try Fedora on your PC without touching your existing
installation by following the Live Image Guide."
The end of the Live Image guide helpfully points users to the Installation
guide if they want to install :)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
9 years, 2 months
[Bug 654484] New: New Bugzilla component for Storage Administration Guide
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: New Bugzilla component for Storage Administration Guide
https://bugzilla.redhat.com/show_bug.cgi?id=654484
Summary: New Bugzilla component for Storage Administration
Guide
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: r.landmann(a)redhat.com
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com,
nb(a)fedoraproject.org
Classification: Fedora
Target Release: ---
Please create a component for the Storage Administration Guide; default
assignee should be ddomingo(a)redhat.com
Cheers
Rudi
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
9 years, 3 months
Re: Release notes have a launcher - maybe we should remove that
by Pete Travis
On Aug 28, 2014 3:05 PM, "Elad Alfassa" <elad(a)fedoraproject.org> wrote:
>
> Hello all.
>
> As you may know, we ship a launcher called "Release Notes" in our
> default install.
> During the F18 Launcher Purge[1] Allan asked the docs team to remove
> it from the default install, but his request was rejected[2].
>
> But now we have guidelines[3], and the guidelines state:
> * An "app" is an application as defined by the GNOME 3 HIG[4]
> * An app launcher SHOULD Launch software that is an actual app - see
> the GNOME 3 HIG for the exact definition
>
> And the release notes, well, are not an app (per the definition in the
> GNOME 3 HIG).
>
> Moreover, I don't really think users expect to find release notes
> inside the OS itself - no other OS does that.
>
> We can link to the release notes in our download page, our help page
> on the website (which will be linked from start.fpo once I finish
> implementing the new designs we got), and a bookmark in Firefox
> (pointing to a local copy of the release notes) - so the release notes
> won't exactly be invisible or inaccessible.
>
> We could also go the extra step (of craziness) and copy the release
> note PDF into the liveuser's Document directory (in the kickstart),
> where it will be indexed by tracker and thus accessible via documents
> and people who search for "release notes" in the shell would be able
> to find it (why would they do that? I don't know). It's possible, but
> for me it seems extremely crazy and unnecessary.
>
> While I'm aware what I'm suggesting here might be a little bit
> controversial, I do think it is something which we should consider.
>
> [1] https://fedoraproject.org/wiki/Design/F18_Launcher_Purge
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=846316
> [3] https://fedoraproject.org/wiki/User:Elad/Draft_app_guidelines
> [4] https://people.gnome.org/~tobiasmue/hig3/application-basics.html
> --
> -Elad Alfassa.
> --
This seems like [another] case of "we want to show all available desktop
files without filters, but that looks cluttered, so all other packages
should change so we don't have to add filters." I appreciate the work
you're putting into the details on the default install, really, but as has
often been pointed out it will be really easy to gain that clutter back
with Software. Two things can change here; *all* packages shipping
desktop files, or the *one* displaying them.
Okay, backseat developer hat off, docs hat on. Yeah, I'd like to be free
of the fedora-release-notes RPM. It's a little extra work - really just a
spec bump and rebuild at that stage - I wouldn't have to do.
That said, users *should* have Release Notes, by default, offline, and
discoverable. Fedora changes a lot between releases, and I sincerely
believe that taking the extra measures to expose users to this
documentation helps alleviate frustration and prevents dissatisfaction when
something doesn't work as expected. What seems obvious in context isn't
always so apparent to those on the outside of your process. A measurable
portion of users will look for the reasoning and recommended remedies for
unexpected things they encounter.
Not everyone will simply think "oh, I can install that firewall config tool
with Software, I'm just going to accept that and not question it or look
for more information." Some will look for RNs, some will look for
speculative forum posts, some will look for blog posts, and some will look
for *you* to *personally justify* your actions. Our goal is to provide all
of these people the information they need to understand the behavior they
encounter and achieve the behavior they want. It's a service provided by
the Docs team to both users *and* developers. The benefits outweigh the
pain of having an icon that you aren't that interested in.
As a maintainer of that package, I'd welcome specific suggestions or
requests to improve presentation.
--Pete
9 years, 6 months
Re: Release notes have a launcher - maybe we should remove that
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/30/2014 10:42 AM, Michael Catanzaro wrote:
> On Sat, 2014-08-30 at 19:22 +0300, Elad Alfassa wrote:
>> I really don't undertand why "not installing the release notes" is
>> such a big change we need to wait for the next cycle to implement.
>> It's really just a one line change. And if we want to install them but
>> not provide a launcher (so they could be opened by a bookmark in
>> Firefox) than I'd happily provide a patch to split the launcher to a
>> subpackage.
>
> Eh, I'm just picking my battles here. A Release Notes launcher that
> starts Firefox is not good and we should get rid of it, but it's not
> very bad either and if the release notes people want another cycle to
> rethink how to present the release notes, well why not let them have it?
>
> Another thing we could do is add it as a default web app. GNOME Software
> requires "epiphany-runtime" which is all of Epiphany except the desktop
> file, so that it can install and remove web apps. Well, why not make the
> release notes a web app -- then the release notes team gets to keep the
> desktop launcher, and we are happy since it's a real application.
>
>
Someone had proposed that in #fedora-docs late yesterday, I like it.
I'm working on some copy right now, and will go for an ephiphany web-app
style presentation in GNOME for the next RPM.
For the record, the collaboration part of my arguments here are *far*
more important to me than the actual inclusion of a Release Notes RPM.
It's a valid discussion, and I would much rather start on that basis,
instead of potentially missing a discussion about a design philosophy on
a SIG list, then finding out about the impact when I learn that an RC
isn't meeting release criteria because of my package.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUAgFYAAoJEL1wZM0+jj2ZfXYH/A6jnJh2qnZMqMcggGjamzg4
k2tQQoT/Imx9HF3ZEebs2WlS1w2b8HVg/WBFx0joGXMV9iER8TeFQSOLndy7Col1
vmO44BtWCUJfHG6valf+g+mnXuMMeVLsPy707axSKR/glctRakD1msXiyqpz/IxF
CxFJGennU4f2ypXAPszk6SS26MkIJuY+nyB/5CDN1NAW5yWgPQ8xTH/xxPt6Imnm
KycuexVq4MrmtPO7R0VdThavxJLf9GaAR0Exv/HqJXuEhKrxsAmTMOsPsxKWyZR3
aNPGb5XDfeIz3eAkUdI7goKTxYDaeVD5sW0KxXDBBdTKnbyCK7MSpjoI3wDfB5k=
=0JZ2
-----END PGP SIGNATURE-----
9 years, 7 months
Example of what Leslie thinks is important.
by Leslie S Satenstein
Perhaps I am a nitpicker, but for a while I earned my income as a contract technical writer. I wrote, I edited my stuff and then I passed my writings to an editor. He sometimes responded with tiny touchups, and at times he was cruel. But the objective from both of us was to have a succinct clearly written document.
I would like to illustrate the editing that I did to the following posting
>From the https://fedoraproject.org/wiki/Fedora_Join_SIG
Background
We're looking to reduce the learning gradient that new folks need to
hike up when they look to contribute to Fedora. Users looking to give
back to the community is amazing. We need to go out and give them as
much help as we can. The importance here is that most of them will be
new to the work flows, SIGS, teams and processes that Fedora community
uses. Quite a few of them will be new to Linux even. For these novices,
learning all that is required to become contributors is a daunting task. However, what is important is that all of them have the *potential* to
make awesome contributors!
After a primary edit.
We're looking to reduce the learning gradient that new folks need tohike upachieve when they look to contribute to Fedora. Users looking to give
back to the community is amazing. We need to go out and give them as
much help as we can. The importance here is that most of them will be
new to the work flows, SIGS, teams and processes that the Fedora community
uses. Quite a few Some of them will be new to Linux even. For these novices,
learning all that is required to become contributors is a daunting task. However, what is important is that all of them have the *potential* to
make awesome contributors!
The edited version has the word achieve to replace the "hike up" slang. Words removed are in red, words inserted are in bold. One task of the editor is to reduce wordiness. (Quite a few --> Some). The word "even" was redundant.
The absolute final after editing follows.
We're looking to reduce the learning gradient that new folks need toachieve when they look to contribute to Fedora. Users looking to give
back to the community is amazing. We need give them as
much help as we can. The importance here is that most of them will be
new to the work flows, SIGS, teams and processes that the Fedora community
uses. Some of them will be new to Linux. For these novices,
learning all that is required to become contributors is a daunting task. However, what is important is that all of them have the *potential* to
make awesome contributors!
I have offered to edit stuff that you write, if you so desire. Is there an need for an English language editor?
Regards
Leslie
Mr. Leslie Satenstein
SENT FROM MY OPEN SOURCE LINUX SYSTEM.
9 years, 7 months