PROPOSAL: Create docs-bug list.
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Any thoughts on having a docs-bug list where people can subscribe and
get a copy of all BZ tickets that are assigned for the Project?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM5qOGAAoJEDbiLlqcYamxl10QAIouhdWV68z/ID0aPWWuqsvE
JReX+nXd0z5rEp50GZGWfTBWfFrEf/jBuWPqJQm6gccWa7WWAFXTmHvDULRhQhCu
/unLXbqahZBjrPcz7qeEOn768E24XxPjfQb9FATH53MSs5VX7v5rL7B5uENSiNaS
RHsFsJ0mbxu3ghb2j+gVCpl5g9kmMDKZy78JQujbfxmgASh1wAnN1jASjR7mp7Ku
Aggi147d59QvkIgo0ua7sXC2xn4gL9ionfHgssNOCVssn3b43lhIK0bjLCqFhAoy
z6iY0d9mKqMQAGsCw1FSppk85nSC22VNwVPySepxDCY4Y6/JPP4sJa/V6XCbgaca
jGUbAFXscxTmGmG2XYgc59tGW3gErfSaLY2A4i0VqHIjkv4HSDnKUwCIFPYU+FA6
Q2/zoSp7PqE3kPLzFlyBnPLsS1dmuOY/4pngJ4ayP4YzzhZI9eG0zeTEgoNs1p8o
XNi4iyIqNfC7UTeaOC0cbwWBbDqD8lF++3fXVY2rGteJDpuy6XELpWW+Ks9PijXt
xfeZ9Jhj3ARabJcHSimLjmQvSu5b8D0QlL60ktSPUsVVFia7epNPrwoDL7r3OV9O
M3PuhzpK+Mzde45I93dSuFNQel2+8MSOmy8ODNHjTMaYj06C8yJijJlsxbXTPEvU
YmAAWWcJ90nEw23lCk7D
=P+4u
-----END PGP SIGNATURE-----
13 years, 5 months
Re: PROPOSAL: Create docs-bug list.
by Karsten Wade
We could set the bug/qa list as the QA field for all Documentation bugzilla
components. Then configure Mailman to allow mail from bugzilla.redhat.com.
For a long time we had a firehose of communication funneled to the
relnotes-content mailing list. It was a contact point for incoming
communication from other humans, too. (Not sure about it's status.)
This bug list can learn from that experience. While it becomes another
moderator queue to watch, we can easily add folks to the 'will accept email
from this address' list, such as keeping them able to be included on a
list-bound discussion.
Anyway, I'd like to remove myself from all those QA bug component spots, but
I need something reasonable to put in it's place. Would've
docs-bugs(a)lists.fedoraproject.org work for that?
- Karsten
13 years, 5 months
[Bug 513907] New: SRPMs fail to build in Koji
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: SRPMs fail to build in Koji
https://bugzilla.redhat.com/show_bug.cgi?id=513907
Summary: SRPMs fail to build in Koji
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: high
Component: publican
AssignedTo: jfearn(a)redhat.com
ReportedBy: eric(a)christensenplace.us
QAContact: extras-qa(a)fedoraproject.org
CC: jfearn(a)redhat.com, fedora-docs-list(a)redhat.com,
mmcallis(a)redhat.com
Classification: Fedora
Description of problem: SRPMs fail to build in Koji due to the following error:
Processing files: fedora-security-guide-en-US-1.0-16.fc12.noarch
error: Two files on one line: /usr/share/applications/Fedora
error: File must begin with "/": Projectfedora-security-guide-en-US.desktop
Version-Release number of selected component (if applicable): 0.44-0.fc11
Possible Fix: Remove the %{?vendoropt} from
desktop-file-install %{?vendoropt}
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop
or remove %{vendor} all together.
I'll be testing this soon to see if I can provide a patch.
--
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.
13 years, 5 months
Re: Fedora Elections Voting Period
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/22/2010 05:13 PM, susmit shannigrahi wrote:
>>>>> I have a draft, but prior to sending the final version out I'd like to
>>>>> make sure the following document is still correct / relevant / up to
>>>>> date:
>>>>> http://nigelj.fedorapeople.org/feg/
>
> Paul has the same one:
> http://pfrields.fedorapeople.org/documents/elections-guide/
The Docs Project has officially adopted this guide and has posted it to
the docs.fp.o website. If anyone sees any problems with this guide
please file a bug so we can work on it. I'll release the POT files soon
so that the guide can be translated.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM69mVAAoJEDbiLlqcYamxEasQAJaZIgpPycfY1DBTzA+l4JvT
uftjaOmm8eM3N6MDT5mZ2JbyG/FCdiNMuEBgOeahRTtHXxGP1KnwZqLQePPVAUNx
tMVtWqM+I9lWhYX5+k0TRTt3vjq6smWHpQs9bs3mR92kyo3vYe/NDkYc2zT1oKB1
vTOaIDGYCEB/p/W/f6GRYw8ocx5b2sPafKyRVmmNryAclZMf/WAQRzouL9bIY+MB
UqKRoNbWyf2czSOU9Kkq9kFC2/0zj5RJp3XKuy67FDVXpjOJ42Ds2KPg1VQ9pCRx
pY9ylYeeiT7GlXF7dYr/gQ9klnfYz0P7tWQt4NluQ2hK/H04mDP0ufemN5xZ5wz0
i8YYq2Oexu2wMHyLynhuuxlKX7vo+nypDfeJo2y+Q/GebrdQHkyh91962up3gZet
lG9j7CirTHHsqYJbRkQ4TEYWlbhDq54bJ+mInyRicrLGQoP4lByJfzBygf4KvG+l
Xu79jO93AkkGW9ZBwy+GXdRxkus0p3idPuqOf8yUbTY14SHT6kTlxPPHzXdIaLta
pubOhiMR1S3oB9/fKESNN0+s2iOrVbPptMadViVoSW9by+M8ihLf2Wb5xG+56cEc
OXi6pawCwksjahkUqeWvuBwbNwArQ1PX6bJL0KHNsJZRggtQZzPEpUaU5zKvMl0H
cztWw51AS1riV26ZEMkY
=ouhB
-----END PGP SIGNATURE-----
13 years, 5 months
Docs translations
by Misha Shnurapet
Hi.
The Russian translation team has finished translating the SELinux User Guide and are uploading updates to the Translation Quick Start Guide, how do we get the changes to show up at docs.fp.o?
Thank you.
--
Best regards,
Misha Shnurapet, Fedora Project Contributor
http://fedoraproject.org/wiki/User:Shnurapet
shnurapet AT fedoraproject.org, GPG: 00217306
13 years, 5 months
Removing all redirects from docs.fp.o
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
History:
When Fedora 13 was released we had just upgraded to the latest version
of Publican which changed all of our links on docs.fp.o. The search
engines hadn't had enough time to catch up with the new URLs so we added
links to act as redirects so the old URLs would still work.
Now:
The redirects are still pointing to F13 documents. I'd like to go ahead
and have those redirects removed from the docs.fp.o website as these
redirects are becoming problematic.
If you have any comments on this please reply here. We'll make a
decision during this week's meeting with a hopeful execution of the
following morning (or that's when I'll put in a ticket to have this work
done by Infra).
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM6Gw2AAoJEDbiLlqcYamxXL4P/iHfoa3COk04spROK0bRRCAn
xgyBZwYsjxUcLLTVX7Fm72X0Mp/D/3Fz6bRznuMnhaPrT5yw6yFNo6HTkphhBTTE
tAZxA4sgKp0OAyC96lHdv7bH8Grfz/JhnSdyNk1d0obSfvBbmECA+gCYPMy8Q4Dt
qj9QK+SMNoVQdeUXz1sCxYiTDKMCzdR2EuaXSW658sy3i96NQ2Fnf0fLCLOM+8e4
XFwTA3tskjgIkeGmmbkOdl4Fj2059sLX8DRPqszHCYmtmw6shm3JPoJRhyf4Vvpf
+qxLKnvY8LzE6oQlkMlhflNYq4nfkYq2fnN1bmds1oAbGrDZbOj694W/fbyMoJ/y
oUny58AzA6PCIm7Dhu4/S6U4caHW6rxl5Qrhvh1/NTWcomhLlw3wFXNi1ykv/qbD
gSqUUkkc5//tvV0DulnB0rMojOeS3e/DoAfsEM3u4m6Qark+ZlSgPBdHxGhdV/gg
HFn7UsBt0d8IgQF0esjqbU0j265w0ve7Ja+xKSO0XfjojUtVOYzpMu4QXiUgDxdA
787d3ECTjvo4j9J0ZhdNBWYW4vMTDomHu+XicQfmEx2ZJuIaklQ91fl9vUldD7af
0Rg6m48WKhTADnIASzWyeXKOR6oBKndDWEcn6PKhfiKB1v3H6wGWWlQy4c281Tes
UfLCQ09kczqIVJDnPGsT
=DWkl
-----END PGP SIGNATURE-----
13 years, 5 months
[Bug 655287] Fedora 14 release notes redirects to Fedora 13 release notes
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.
https://bugzilla.redhat.com/show_bug.cgi?id=655287
Eric Christensen <eric(a)christensenplace.us> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kwade(a)redhat.com,
| |stickster(a)gmail.com
Component|release-notes |docs-requests
AssignedTo|relnotes(a)fedoraproject.org |eric(a)christensenplace.us
QAContact|kwade(a)redhat.com |fedora-docs-list(a)redhat.com
--- Comment #1 from Eric Christensen <eric(a)christensenplace.us> 2010-11-20 19:13:22 EST ---
Rudi: I think this is a redirect error. Can we completely remove the
redirects, now? Of course this would prevent the smaller link from working at
all, correct?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
13 years, 5 months
