[Bug 450331] New: lack of documentation on restoring from bare-metal (UUID problem)
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 report.
https://bugzilla.redhat.com/show_bug.cgi?id=450331
Summary: lack of documentation on restoring from bare-metal (UUID
problem)
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: docs-requests
AssignedTo: kwade(a)redhat.com
ReportedBy: czar(a)acm.org
QAContact: stickster(a)gmail.com
CC: fedora-docs-list(a)redhat.com
Description of problem:
ref: https://bugzilla.redhat.com/show_bug.cgi?id=449299
There is a lack of documentation on restoring a system from bare metal. I have
found (see reference) that restore the root ("/") is not as simple as as just
executing the restore command when running in rescue mode.
With the current emphasis being place on use of UUIDs in both Fedora and RHEL,
the whole business of UUIDs need to be better documented.
Version-Release number of selected component (if applicable):
Fedora 9
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
10 years, 5 months
[Bug 462147] New: Tracker bug for docs modules moved away from cvs.fpo
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: Tracker bug for docs modules moved away from cvs.fpo
https://bugzilla.redhat.com/show_bug.cgi?id=462147
Summary: Tracker bug for docs modules moved away from cvs.fpo
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: docs-requests
AssignedTo: kwade(a)redhat.com
ReportedBy: dimitris(a)glezos.com
QAContact: stickster(a)gmail.com
CC: fedora-docs-list(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
This is a tracker bug for documenting the process of moving projects from
cvs.fpo to fedorahosted.org.
It will also help us gradually update the projects' presence on Transifex as
well.
So far release-notes has been moved.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months
docs beat format
by Jens-Ulrik Petersen
Hi,
I was trying to clean up the docs beat hierarchy a little so that the the contents list looks right.
What should the default toplevel header be in a docs beat page? I mean level 1 ("= Beat Title =") or level 2 ("== Beat Title ==")? It looks to me like it should probably be "==" but some pages are using "=".
It would be nice to make it consistent to make it easy to browse the docs beats page and encourage more people to contribute.
Thanks,
Jens
14 years, 11 months
New language codes?
by Paul W. Frields
If the Docs Project is able to complete a transition to Publican for
the release notes for Fedora 10, many of our language codes will
change to ISO standards. This includes moving from en_US to en-US, as
in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the
distribution get updated to support both of these options. I would
suggest shifting them to use the ISO standard, en-US, first and the
try falling back to en_US. That way, if we fail utterly and have to
drop back to the old way of doing business, the results will still
land properly.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 11 months
F10 Beta release
by Paul W. Frields
Great job with the release this morning, guys. I know there were some
gremlins in a torrent or two, but overall very painless and you guys
made it look easy (as always). Hurrah, another milestone on the path
to Cambridge!
If anyone has any issues, we could plant them on a page for the next
release day planning group call.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 11 months
Re: F10 Documentation
by Asgeir Frimannsson
----- "Asgeir Frimannsson" <asgeirf(a)gmail.com> wrote:
> On Tue, Sep 30, 2008 at 3:13 AM, Dimitris Glezos <dimitris(a)glezos.com>
> wrote:
> > 2008/9/29 Paul W. Frields <stickster(a)gmail.com>:
> >> On Mon, Sep 29, 2008 at 05:19:14PM +0530, Ankitkumar Rameshchandra
> Patel wrote:
> >>> Dimitris Glezos wrote:
> >>>> 2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
> >>>>
> >>>>> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos
> wrote:
> >>>>>
> >>>>>> We'll need the usual steps followed to add these modules to
> transifex:
> >>>>>>
> >>>>>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
> >>>>>>
> >>>>>> The most important ones are having 'transif' added to the
> respective
> >>>>>> account system groups and notifying us with which <VCS root,
> module,
> >>>>>> branch> to use. One bug report for all moved Docs would be
> sufficient,
> >>>>>> and we can re-open it when a new module has been moved.
> >>>>>>
> >>>> All 7 docs projects have been registered and enabled [1] in
> Transifex.
> >>>>
> >>>> https://translate.fedoraproject.org/submit/module/
> >>>>
> >>>
> >>> Can we get all 7 docs projects enabled in DL as well?
> >>
> >> I think Dimitris mentioned earlier that Damned Lies won't support
> >> Publican's multiple POT files. It would be great if Red Hat
> I18n/L10n
> >> would collaborate with the community to help pave the way for
> >> statistics reporting for these repos. I don't know whether that
> means
> >> fixing part of DL, or simply accelerating the rate at which
> >> statistical support in Tx is written. I know Dimitris, Asgeir,
> and
> >> any of the other Tx developers would be thrilled to have some
> >> assistance with this.
> >
> > Patches are welcome with champagnes and fireworks, as always. :D
> >
> >> In the meantime, Dimitris also suggested a workaround using some
> sort
> >> of simple Python script. I doubt that's been written yet, maybe
> >> someone can help there?
> >
> > Here's a sample skeleton for such a script/scenario, for anyone
> who'd
> > like to actually code it.
> >
> > -----------------------
> > == Get the source ==
> >
> > First time:
> > $ project-list = ['about', 'release-notes']
> > $ for p in project-list:
> > git clone git://git.fedoraproject.org/git/{p}.git
> >
> > Later, to pull new changes:
> > $ for p in project-list:
> > git fetch && ...
> >
> > == Calculate statistics ==
> > $ wget http://.../fedora-docs-l10n-script.py
> > $ python fedora-docs-l10n-script.py pt_BR
> > pt_BR statistics:
> > about: 80% (115T, 40F, 10U)
> > release-notes: 80% (115T, 40F, 10U)
> > -----------------------
>
> If I remember correctly, publican actually has a 'genearate
> translation statistics' make target that can even generate HTML.
>
> Would it be ok If I set up a cron job that:
> 1) Puts translation statistics on a public web page (to make it
> simple, e.g. my fedorapeople web space)
> 2) Sends updated statistics to fedora-trans-list daily, or even after
> each 'submission' depending on how much we want to spam that list...
>
> In addition, we could add a link to this stats through the front page
> of translate.fedoraproject.org
>
> Comments on this workflow is welcome, but I'll try to make sure we at
> least have some statistics for our documentation SOON.
>
> I guess the fedora infrastructure is in 'freeze' mode, so I'm not
> sure
> how easy it would be to make the script run inside the
> infrastructure... But the main concern now is giving translators some
> statistics :)
>
> But first for some breakfast...
Could anyone review the attached script for converting release-notes to a publican-friendly PO structure?
Figured I'd learn ABC in bash scripting while I was at it...
I could send out a git patch, but it makes it a bit hard to see what I was doing...
cheers,
asgeir
14 years, 11 months
Tuning Documentation & Translation schedules
by John Poelstra
Thanks for being patient with me as I get up to speed with the different
tasks your teams perform and where they intersect. I am continually
refining the wording of each task so it is hopefully clearer exactly
what is being done. In the process I'm discovering more undocumented
tasks that need to be completed to bridge tasks already on the schedule
and also finding others that are unclear as to what they are. For
example we say "translations due" but we don't say which translations
they are... release notes, softare, documentation?
I am also trying to a better job of representing on each team's schedule
which tasks THEY perform. For example the Documentation schedule lists
only the tasks that docs is responsible for--not translation tasks too.
The overall schedule shows combined tasks for all the teams if you're
looking for a combined view.
On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby
instance to add more details and corrections to the Fedora 10
translation schedule. Feel free to join in. If this turns out to be
helpful I would like to do a similar exercise with the docs team if they
are so interested.
Translation schedule:
http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html
Docs schedule:
http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html
John
14 years, 12 months
structure for F10 final release notes
by Karsten Wade
If you look at the beats, think of them as topic-specific buckets of
content:
https://fedoraproject.org/wiki/Docs/Beats
Once converted to XML, we can reorder them at-will to get different
structures. We've discussed doing a radical overhaul in the past, but
have instead done a set of slow, steady evolutions. *yawn*
Here is a strawman proposal, meaning a thin structure to throw more
ideas against:
https://fedoraproject.org/wiki/Release_notes_structure_for_F10
Trying to cover the usual use cases, give it a tone people might relate
to, push up front some issues people care about (installer, bugs,
hardware support, etc.) I believe this structure covers all the Beat
content. To quote:
1. What's new in Fedora 10 -- Overview
2. What is new for installation and live images -- important
installer notes, live image instruction sets, pointers to more
docs
3. What's the latest on the desktop -- *all* GUI applications,
l10n, a11y
1. How has software installing and updating improved --
Add/Remove Software
2. Do you browse the web, read email, and create/edit
office documents?
3. What is to celebrate for musicians, artists, and other
creative types?
4. What is the new stuff for gamers, scientists, and
hobbyists?
5. Power users get what new features and fixes?
4. How are things for developers -- devel tools, -devel package
changes, i18n
5. What do system administrators care about -- services, daemons,
non-devel CLI
1. Are there cool new security features - SELinux,
firewall, hashes, new signing key details
6. What are the nuts and bolts of hardware support -- arch-specific
notes,
7. Are there hideous bugs and terrible tigers? -- known issues,
link to up-to-date bug page
8. Legal stuff and administrivia
--
Karsten Wade, Community Gardener
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
14 years, 12 months
Self-Introduction:
by Kam Salisbury
Hi, I'm Kam Salisbury. I live and work in Philadelphia Pennsylvania USA.
>What other projects or writing have you worked on in the past?
Several small articles and tips regarding using Linux to get real world
tasks accomplished. Some items are more suitable for other system
administrators or hobbiests.
>What level and type of computer skills do you have?
Over ten years experience supporting and using computer technology in
Windows, Novell and Linux environments.
>What other skills do you have that might be applicable? User interface
design, other so-called soft skills (people skills), programming, etc.
No published programs to claim fame to but definetly scripting capable -
shell, HTML/CSS, PHP, Java. As a network manager I am comfortable speaking
in front of groups.
>What makes you an excellent match for the project?
I want to help.
Kam Salisbury
kam(a)kamsalisbury.com
FAF1751E fingerprint = DC3A 73C0 199D 0C29 BDCD 9D2A 8014 9957 FAF1 751E
14 years, 12 months
Release Notes file renaming
by Paul W. Frields
When Publican -- the automated documentation building engine we're
trying to use for the Fedora 10 cycle -- creates references from book
titles, it expects equivalency between those titles and the file names
to which it refers when building. It uses underscores to represent
spaces when looking for those file names.
So for example the title "Release Notes" will cause it to search for a
base filename "Release_Notes". The final output documents will be
named similarly. Jesse, I'm worried that renaming these things in the
RPM %build process for fedora-release-notes will cause a whole chain
of further problems in OMF files, etc. Can your compose process be
set to look for "Release_Notes" instead of the former "RELEASE-NOTES"?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 12 months
