Status of all Guides
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All guide owners,
Please let me know the status of your guide.
All guides should have POT files up and be setup in Transifex and
translations should be happening. The English versions, and whatever
languages are complete, should be uploaded to docs.fp.o at this time.
If you have any questions about this please let the list know so we can
help.
Thanks,
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMq4MnAAoJEDbiLlqcYamxbp0QAKwos/6H5lSOeJkg9yJn7wQv
MSX/X9lDzsnvZBKuYZkVdsVWdaI/zHQOAuPphtP1aVzr5AKpSq+cKiaOOhoafXuv
yO8iYDmnC11VKc0Hw5DNA1q1menbDT/sXgGD0+2JlWRjsRlEtAb6NsZFl/TOXX6W
hVAW+EWHuB8Q7J2KZQvGgM1RaTbxuY0lmnMNY7Pojywuo1TPkxgBXTGledu5idl9
PolD8t2ITaT47BhM/52CwYcy9hm0sm2dNA2+e4oHEakAqEHvAairb9P9QF9ScVu0
qu1eqLZjNYuYj92sfvXW+gMRpi7aAOea5qbBVIccm8e1jFpBwBW7Nbio05o48sfg
uIpqcL83uUxN9vsCtFfVT2Z/ee6buAy0RiBi/iiCh1QrDpvQX1Zk4f4gh6LY0VEt
6j0K+KYKDZk/rq2vk4YBksfA7KFC0kpliUReKv1LNwHWV6XHwC32L6EWTiUjuIrY
0uvcDeLZsJ4oANLECQJCiAEAv6LtRLskf6L+ycCEJ319OAsqjNapbwvtrRbM5PHt
pRmm7ZxFFizoBMvBgr4NPPXXdSbkB6GIS3k/BwpMIhvV8uKY+T2PcTB+SRX3K66A
0TnY6eazW5xiYOvQZuVgBm374KP6cJ5f3SQXxlsVAb7Et3JSGWT77zFO3OIJeWXg
rXqeR7A+uuZZOk54I4th
=LFyW
-----END PGP SIGNATURE-----
13 years, 6 months
Re: F14: what to do about pino / twitter
by Paul W. Frields
On Fri, Oct 01, 2010 at 11:48:07PM -0400, Matthias Clasen wrote:
> On Fri, 2010-10-01 at 16:44 -0400, Paul W. Frields wrote:
> > On Fri, Oct 01, 2010 at 01:19:52PM -0700, Adam Williamson wrote:
> > > On Fri, 2010-10-01 at 16:07 -0400, Paul W. Frields wrote:
> > >
> > > > > Yeah, if we want to ship one, gwibber is pretty much the only option,
> > > > > since it's most likely too late to fix pino before F14 is released. The
> > > > > big cons about gwibber, in my opinion is the fairly poor performance
> > > > > I've experienced with it (tho I last used it about 2 months ago) and the
> > > > > number of dependencies it would pull into the livecd.
> > > >
> > > > Doesn't post-Beta seem too late to do this? Better to have people
> > > > simply use their browser I'd think.
> > >
> > > well, we have to make *some* kind of post-beta change here, since as I
> > > said the current situation blocks the release. I don't think subbing in
> > > gwibber for pino is a particularly scary change, all we'd have to check
> > > is if it goes over the size limit, and if it works, which is about half
> > > an hour of effort.
> >
> > Right, the uncertainty I have is really around the functionality of
> > the new suggested default client, as opposed to "let's not do
> > anything." My preference would be a simple removal of pino for no
> > other reason than least disturbance of the Force.
>
> I agree that removing pino, together with a suitable note in the release
> notes, is the safest route at this point.
Adding the docs@ list to the cc so that they are aware of the need for
a release note for this. Docs folks, feel free to ask questions here
on desktop@ as needed to figure out the best text.
--
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/
Where open source multiplies: http://opensource.com
13 years, 6 months
PROPOSAL: All new BZ tickets assigned to the Docs List
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a proposal that will hopefully bring more attention to the
tickets we receive in BZ. If I change the default "person" that all
Docs tickets are assigned to to the Docs list. When this happens
everyone on the list will receive a message when a NEW ticket has been
generated. If you are interested in working on that ticket you would
just logon and "take" the ticket (assign it to yourself) and mark the
ticket as ASSIGNED.
Thoughts? Comments? Questions?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMqcvIAAoJEDbiLlqcYamxpHQQAKi+FlT1zt9i0czi0IdmREr6
ZkYn77L6L/NfmcGj4JZyx3MEFdd6pGbQeQCxoiWqWXywpIg60kiVwJSJudGJJ2KF
wIPe5SIl0xi+j26EZHuhbHfUmuZgBv1zuk25H+EBvHMNJxZhLP8xejNAXfY4DTEx
ZxYpPO5tO5nuFzc0zze4Y8xm+EOnlw14F9kO6ruzGiCnI0byffPq/49SUSeaFrfn
jQjnz4nACojsD7MqlxxHXYgF5eZlCeqP/3FEJxHY+A9FdbuPH1fZo3GodCokz0p1
h0IWfPtrCcEuBY9u5bPvHdzD5h59Oxo9oHmqNliI+/dQZFdGkHsieQ44kAWHrWRw
k2WnMrF1UyJxMECB8QU9sKe4GIYK1ZGkcl4JLnUhIsuSd97c/hR04tuxCO4EchnI
YNteGiNPhkUsV06YDRij6tYzxDPHSk3GTonrGEbB1VGy1AYwVZ+WsWfQXip7Yuo8
PK6CyKlQPQ/gsMGxKbIlSdWUCk+OrlHzS4DrJVi06gw76hYxryu+5qA2aYlDyQOt
ZAIO5l10LNis8rNPA60pyM52xUQ+4p4XMAge4Cb6ooksl93j1+kUeLbTutAGXWAP
+sRk/2a+Ktw4EKWf34rUdQg+EaQlvlMH50sai4NkzDsI2l5yTre999LkLR8hWGtk
/OtmeGqDNMr45LHtTVTR
=4t+H
-----END PGP SIGNATURE-----
13 years, 6 months
Re: F14: what to do about pino / twitter
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/04/2010 11:13 AM, Paul W. Frields wrote:
> On Fri, Oct 01, 2010 at 11:48:07PM -0400, Matthias Clasen wrote:
>> On Fri, 2010-10-01 at 16:44 -0400, Paul W. Frields wrote:
>>> On Fri, Oct 01, 2010 at 01:19:52PM -0700, Adam Williamson wrote:
>>>> On Fri, 2010-10-01 at 16:07 -0400, Paul W. Frields wrote:
>>>>
>>>>>> Yeah, if we want to ship one, gwibber is pretty much the only option,
>>>>>> since it's most likely too late to fix pino before F14 is released. The
>>>>>> big cons about gwibber, in my opinion is the fairly poor performance
>>>>>> I've experienced with it (tho I last used it about 2 months ago) and the
>>>>>> number of dependencies it would pull into the livecd.
>>>>>
>>>>> Doesn't post-Beta seem too late to do this? Better to have people
>>>>> simply use their browser I'd think.
>>>>
>>>> well, we have to make *some* kind of post-beta change here, since as I
>>>> said the current situation blocks the release. I don't think subbing in
>>>> gwibber for pino is a particularly scary change, all we'd have to check
>>>> is if it goes over the size limit, and if it works, which is about half
>>>> an hour of effort.
>>>
>>> Right, the uncertainty I have is really around the functionality of
>>> the new suggested default client, as opposed to "let's not do
>>> anything." My preference would be a simple removal of pino for no
>>> other reason than least disturbance of the Force.
>>
>> I agree that removing pino, together with a suitable note in the release
>> notes, is the safest route at this point.
>
> Adding the docs@ list to the cc so that they are aware of the need for
> a release note for this. Docs folks, feel free to ask questions here
> on desktop@ as needed to figure out the best text.
>
So pino needs to be removed and replaced by Gwibber in the Release
Notes? It will be tight but I think that change can be made. I'd
appreciate someone to come with the text that needs to be used for this
replacement.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMqlwzAAoJEDbiLlqcYamxeUYP+wej+K6pL2PMpaFVETxEpiPA
aXw/D945w1+UW+yZYtW04/e/k+Ray84b1vZODSUx9GhOKbSzU0Gfdf9qW7OKS9ro
8qLO4B385kyZObBk+MjDpqlTxwWat0Eo1KvYcSxLsXyNGILTUm6OO0LMfh07H35g
znn90fi/+tNXYR6YB1uwUCxPsbbt+jTW5EP8vz/M9HCM7c2TdZKpYC6ER3erQhFH
HiQCQ3kgcHCbzT1GA5XqJB8wL6+mF6WC0gETuX33Z76I51vYCPZsalJ5JFlC5Bbh
xeqwReuBrNrOCzxIpiMnMN4YGHKK5PHXrkOVHbrGLJRUPXvYSLwIh5LjD7dn5I9z
/9mIYFx5aVRgS7+hsWiXR8JVPHmORyRDXlSglG4i6fvpTIDt8KgcCpzUaaKfBEzD
b480Rr1dmIk24N9DVinN3u/OtBAwMoLV5N+71r/B4iUGiSppxvpFWn+6fii9Xrjo
VdMZ82miIvmQKVNRXeWLPAC6NPrcUgK9E1Va4ICGcovW+kuuE962BzO+LLlqxHzG
fEKSEdKp/eaUULLu/8UTmxt0seSZoWyDpkATVldtxSiIvjpktJGhtDVlCoAx/ni9
tUQ7VVaQTZGHjust6OK6stQVmc+dXRVQmI488bDaS8yWB4QF8CXdRKGDGRHmprO6
mVNg/yDUB9eTjQDtvk0Y
=NG81
-----END PGP SIGNATURE-----
13 years, 6 months
Addressing Tor in the Fedora Security Guide
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I was asked, earlier today, why Tor wasn't addressed in the Fedora
Security Guide. Anyone have any feelings on whether or not addressing
system would be appropriate for the SG?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMqiVJAAoJEDbiLlqcYamxBa4P/j6ESDXQqX5+qTYnaxuQlEBx
HHivV6cJN1ZPaoC33xAxDzijE/GDZsfC9agT6UvoDZCDfpmdkxlu0HVB50j6N2ry
mB3OmOj7nAIQRKj6Xv/UUnOw5nzXP4dLxXKOUsOJ6CiMm3wIvO00JuEmPNoRv7xM
zA8IpbdwCAggJTDq2iG9t9eDHJrITBSmVO92iHWjVYB3BHWRHHzot/dniEeypVBQ
3Jb2ahwI8Gj55sX8q3Mad0UEtVDm3HpLocqg3F9Kese8QqItalNR1u+pOopijnYD
t3DiWvOYRbtYH0bszliR8o7fVQeLaV1x5VMOhNlWWPIni0WnZMs9YUptGq8jVHKQ
pH1tmWTmMWkdm6R6LjT6fvS3Ti5l0+2UiCx/ewtLNpJ2fZ0y5VWjl/WUCUby60zz
1FOviyQK8JwPURy5QPpVsmj5/HB2Zx/ah0i33aPWOmAIAnGxCNqj8Ek9W1ZmNTsE
cxshDvkSy6m99r+r48PNcr88m3jc2Mr4R6TyYIb1cI3OPgoTUKyQPFKTZYPYsfT6
bA/ULeiQ9UVGpAv4FBKuy/D55qe3pfyMXiAlO96hHfrt9VyU3lIKBJFCksWNAwLW
N/vrN+Qb8cP6e8B5LA5Q2f84cIWuFvp1Wjwjr4wpQkokzvSMbfA6XzbFH3TFfr7s
rxDgmOFGbqtSUsfZy7Q4
=g/QQ
-----END PGP SIGNATURE-----
13 years, 6 months
jjmcd disappearing
by John J. McDonough
I need to be out of town on family business for an indeterminate period
of time, and I will probably be netless for long periods of time.
Fortunately, there aren't a lot of release notes tasks coming up, and
most are pretty straightforward.
I have been tracking the tasks on
https://fedoraproject.org/wiki/Release_Notes_schedule
If you can cover some of the tasks it would be helpful; be sure to note
them done on that page so someone else doesn't try to duplicate your
work.
10/4 Stop sending updated POs
I will arrange for this to happen by editing my crontab
10/6 Remind L10N no more POTs
Someone should send a note to trans(a)lists.fedoraproject.org reminding
them that updated POTs will cease for a week.
10/6 Wiki Freeze
This one is a little tedious, but easy. Go to each of the beats and
delete
{{Docs_beat_open}}
if it exists, then insert
{{Documentation_closed_beat|
http://docs.fedoraproject.org/release-notes/f14/en-US/html/sect-Release_N...
where sect-Release_Notes-Printing.html is replaced with the appropriate
section for the beat.
10/6 through 10/11
Go through the beats and update the XML as appropriate. There don't
seem to have been a lot of updates, but the devel list was reminded of
the freeze a couple days ago, so a rash of updates in the next few days
wouldn't be a huge surprise. I think we need to rework the systemd
stuff but I don't know what the actual status is, disappeared entirely
or testable. Perhaps stickster can help here. Rahul and Lennart have
been providing the information from dev. systemd is detailed in the
System Daemons section, but it also has a mention in Overview.
10/11
Review the document, make final edits, and make a final set of POTs for
L10N. Then let L10N know the POTs are available
10/12
Build GA htmls until 11-Oct This should still be happening, so no
action is needed other than checking fedorapeople to be sure updated
documents (or error logs) are continuing to appear
10/14 Remind L10N translation deadline - another note to trans-list
10/20 f-r-n.rpm - This actually needs to be done a few days earlier to
be ready for the compose, but as late as possible to capture as many
translations as possible. I hope to be back for this, but it is pretty
straightforward. Instructions are at
https://fedoraproject.org/wiki/Getting_the_release_notes_to_Bodhi
and
https://fedoraproject.org/wiki/Giving_a_document_karma
Stay in close touch with nb to be sure the package makes it into the
compose on time. Nick knows how to check where it is and how to move it
along.
If you have a language that is close to 100% but doesn't build, you can
often simply correct the error in the po file. Most commonly a
translator munged up a ulink tag, or removed the semicolon from a
&PRODVER; or similar symbol. Emacs is real smart about po files,
smarter than me, so I use gedit for this task.
Thanks for all your help.
--McD
13 years, 6 months
Re: Installation guide - ISO media and USB clarification
by mike cloaked
Paul W. Frields wrote:
> In cases where the user can't boot from a CD/DVD but wanted to use an alternative installation method, I thought the 'dd' tool was used with
> the 'boot.iso' minimal boot image to make a USB device, rather than 'livecd-iso-to-disk'.
> Can anyone confirm this? Is applying livecd-iso-to-disk to images *other* than our Live images really supported?
I have been doing some testing - and for me the dd method did not work
for the DVD iso for F14 beta.
I have reported a BZ using livecd-iso-to-disk as working to make a
usable, bootable usbkey for the DVD install iso, but the documentation
needs changing in some important ways:
https://bugzilla.redhat.com/show_bug.cgi?id=639718
I have only been testing the DVD install iso and not live isos - but
it would be better in my mind if there were two separate sections for
usbkey preparation - one for live usbkeys and one for a bootable
usbkey for installing the larger more complete DVD iso.
I hope this helps - and I hope there is still time to make the
necessary changes before f14 GA?
--
mike c
13 years, 6 months
