Docs Project Meeting Summary
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We had a meeting today, here are some highlights:
- - jreznik wants out input on the planning process at
https://fedoraproject.org/wiki/User:Mmaslano/Feature_process . Please reply to
his last mail to the list with any thoughts.
- - When we figure out how our publishing process is going to work, we will have
to document it.
- - The F19 schedule is out, and we are part of it. Please work it into your
personal calendaring solution.
- - We're getting closer to shipping RPMs in the user repos, but the best way to
do so is debatable.
- - Sparks is liberating a lot of security related articles and such.
- - Fedora Magazine is happening, somewhere.
The overview is at:
http://meetbot.fedoraproject.org/fedora-
meeting/2013-03-11/https:fedoraproject.orgwikidocs_project_meetings.2013-03-11-14.01.html
Logs and text in:
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-11/
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRPfkXAAoJEL1wZM0+jj2ZZrQH/jXY//mYa3xo/zS2dY171rbB
dLapLHKX6Z3/H8NrUvXAUltp9Ena2rAckoS4NIlBH1WiUAHUIAXmiy1TvNgaw492
Da+Ag6ovPryiqvWVhpYIMdMELTyCexFr+MSNck9yEP1Tn7mYa8qVAToevYj7e4Py
M2gz5ottEABaz2kjhn/LZ2RYNsFm8md3h6Nx/xIyQsFs+tHAkJJLP4Bm0BKF/wWH
1vjrawGZgAIG506mYQ69t8hREgv4HRHOtzHSKpMl9J44iU8BHdjlWek+PhtOY85K
6LGkWjaBm9ZtgH6P0NNDHKSrKuN3bAP0xsUqcRgKGpMPxk6eD71Cyu++QhYnmYM=
=N513
-----END PGP SIGNATURE-----
11 years, 1 month
Fedora Docs Meeting Reminder - DST Edition
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tomorrow's meeting of the Fedora Docs Project will be at a special new time,
1400UTC. There is no change for many of you, but myself and many others will
be living in a surreal world for the next week or so, and might need a
reminder.
The meeting, in #fedora-meeting on freenode, is at 1000EST, 0900CST, 0800MST,
0700PST. I hope this shift doesn't cause conflicts, and look forward to meeting
with you all.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRPXkfAAoJEL1wZM0+jj2ZkuoIAJ+ig1x4ZdVHQFHr4xP9NL49
jYFKhgYGimckDlXQPpMU62gjUVBY0fPT8MIuAQRWs7MzsAaYHIWWlB9eK63y6Ja9
gAjhgosNHtyjhbpONku9DSIBqVnCFa+Zbl/fKytC9wr3Xph7nDXsRfwLd0FQgJbL
iQfe6KzLCDuqDoxwAYI6fQRpBQr+BOtBCIRfy03LlmLN4PKk+oMUDdDJMgJlMBuF
vk9W1UEQyL4NJhzBsuEI25J9uiq2nUuJiBW1bVb82flbHt66SkbkGq8VW5vEwS7T
RlovudW6qev417+U5STXILjU8FD1SpFE0foNVt6TCjDI+AVmm08wRhb02opJV3Q=
=Qvsc
-----END PGP SIGNATURE-----
11 years, 1 month
[Bug 902500] Publican-based books in GNOME Shell
by Red Hat Bugzilla
Product: Publican
https://bugzilla.redhat.com/show_bug.cgi?id=902500
--- Comment #4 from Pete Travis <me(a)petetravis.com> ---
I have a spec file that does almost exactly that, and the Release Notes have
been using a javascript snippet for a while that redirect the user the the
appropriate documents. I'm writing something up on the process of using such a
spec file to package our docs now, and can post a link in this ticket for the
curious.
A few highlights:
- Localized files are in subdirectories
- Desktop file is localized at build time. The actual action line cannot be
localized, ie Exec or URI, but we can localize name and comment.
I'm intrigued by the idea of documentation as a search provider.
--
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=4F0DL3RXpT&a=cc_unsubscribe
11 years, 1 month
[Bug 902500] Publican-based books in GNOME Shell
by Red Hat Bugzilla
Product: Publican
https://bugzilla.redhat.com/show_bug.cgi?id=902500
--- Comment #3 from Jeff Fearn <jfearn(a)redhat.com> ---
Hi, it's highly unlikely this will get addressed by the Publican team. We'd be
happy to take patches though.
Note that you can use publican to build the HTML etc without using its
packaging mechanism, so there is nothing stopping anyone with a minimal
understanding of spec files from doing whatever they like with the output.
e.g. pop something like this in to a specfile
%build
publican build --langs all --formats html --publish
%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/usr/share/help/
for lang in 'en-US' 'de-DE'; do
olang=`sed -e 's/-/_/g';
install publish/$lang/Publican/3.1/html/Users_Guide
$RPM_BUILD_ROOT/usr/share/help/$olang/Publican;
done
Untested, but you get the idea, if you aren't happy with the way it packages
things just use publican like any other command line tool and forget it does
some automated packaging.
--
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=GjCzwvDjvS&a=cc_unsubscribe
11 years, 1 month
Contextualization for Software Localization
by Ankit Patel
Hi,
My blog post about "Contextualization for Software Localization"
Concept: Review and modify the source code of software applications in
order to add comments or references or context for the translatable
messages in order to make them more meaningful so that it could be
easily understood by translators that will help us get the best
localization in the industry!
and more here... http://www.ankit644.com/?p=296
Thought this would be good initiatives for i18n, testing and
documentation groups as it could be started under Fedora Special
Interest Groups!
Thanks
--
Regards,
Ankitkumar Patel
http://www.ankit644.com/
11 years, 1 month
Documenting Features
by Pete Travis
Hey guys,
I've been reading the Feature discussions on devel@ today, and an idea
came to mind. A process for documenting accepted Features would help
prevent major changes from slipping through the cracks. Here's what I
came up with so far; I think we can hammer it into something useful:
Accepted Features[1] will be listed in a table roughly analogous to that
used for Release Note Beats[2]. The table would have columns for the
Feature name, a docs volunteer, and developer contact, as well as others
reflecting the Feature documenting workflow.
A set of guidelines for the docs volunteer covering a feature will come
along with the table. The set of tasks to be juggled might include:
- Establishing an appropriate developer point of contact to aid in
documentation. Note that this isn't always the feature owner.
- Ensuring the content of the Feature is understandable by a
hypothetical average user.
- Working up a basic guide to implementing the feature, if applicable.
- Creating an entry for the Feature in the appropriate Release Notes
beat.
- Checking existing guides for impact caused by the new Feature, filing
bugs as needed, and assisting the guide owners in updating as
appropriate.
A defined process like this will help split up the workload caused by
feature churn and cut redundant efforts by providing new information for
multiple published works. Your thoughts?
[1]
http://fedoraproject.org/wiki/Releases/19/FeatureList#Fedora_19_Accepted_...
[2] http://fedoraproject.org/wiki/Category:Documentation_beats
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
11 years, 1 month
Fedora Docs Meeting Minutes
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A two for one summary today, as I catch up on sending you the minutes:
4 March 2013
- -------------------------------------
Meeting started by randomuser` at 14:01:57 UTC (full logs).
Meeting summary
roll call (randomuser`, 14:02:19)
ACTION: items (randomuser`, 14:06:00)
action items (randomuser`, 14:06:12)
Sponsorship of docs.fedoraproject.org (randomuser`, 14:07:13)
https://bugzilla.redhat.com/show_bug.cgi?id=611891 (randomuser`, 14:08:54)
Docs Infrastructure (randomuser`, 14:13:43)
Outstanding Bugs (randomuser`, 14:19:36)
http://tinyurl.com/lbrq84 (randomuser`, 14:19:45)
open floor (randomuser`, 14:22:17)
Meeting ended at 14:30:06 UTC (full logs).
Action items
items
People present (lines said)
randomuser` (31)
iambryan (6)
zodbot (3)
suehle (2)
zoglesby (2)
lnovich (2)
Sparks (1)
bcotton (1)
jjmcd (1)
Capesteve (1)
- ---------Full logs at http://meetbot.fedoraproject.org/fedora-
meeting/2013-03-04/https:fedoraproject.orgwikidocs_project_meetings.2013-03-04-14.01.log.txt
25 Feb 2013
- ------------------------------------------------------------
Meeting summary
Roll Call (randomuser`, 14:02:10)
Follow up on last week's action items (randomuser`, 14:08:37)
Docs Infrastructure (randomuser`, 14:09:26)
Beat Assignments (randomuser`, 14:14:22)
http://fedoraproject.org/wiki/Category:Documentation_beats (randomuser`,
14:14:28)
Docs Infrastructure (randomuser`, 14:17:56)
Outstanding Bugs (randomuser`, 14:22:04)
http://tinyurl.com/lbrq84 (randomuser`, 14:22:18)
Sparks' bug corner (randomuser`, 14:25:12)
http://tinyurl.com/agh4mg6 (randomuser`, 14:25:33)
ACTION: sgordon to mail docs list to begin discussion of sponsorship banners
at docs.fp.o (randomuser`, 14:40:08)
Open Floor Discussion (randomuser`, 14:42:44)
http://immanetize.fedorapeople.org/release-notes.spec (randomuser`, 14:53:37)
Meeting ended at 15:02:33 UTC (full logs).
Action items
sgordon to mail docs list to begin discussion of sponsorship banners at
docs.fp.o
Action items, by person
sgordon
sgordon to mail docs list to begin discussion of sponsorship banners at
docs.fp.o
People present (lines said)
randomuser` (72)
sgordon (39)
Sparks_too (12)
iambryan (9)
zodbot (6)
Sparks (4)
bcotton (4)
nb (1)
chuckf (1)
pkovar (1)
- --------Full logs at http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-25/fedora_docs_project_meeting_https:fedoraproject.orgwikidocs_project_meetings.2013-02-25-14.01.log.txt
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRNLeYAAoJEL1wZM0+jj2ZM3YIAIBfjyOnXet6VuncOYisYIbB
iteX9UDaqfEdG3yy+/0tgQEisakaeiVrFYMXIZb9v65WyNFnXkTXenxAZdywYlBU
CyaKhna5v2OECyJkH+S/0DuHUmI2xWP2X1gF0r19wqQ2vY6/L2xdpdhpKhim3YXI
YWKFBRBfo1x6MNuEJ9K+N2xWLDhoHjRkWLJPXr22cetxEsSklfqy5rG0lYleDreQ
346rFf7/ftumpLlY45M+5b/wMDsLshPg5OxvNMsdSp1/GVtl8ORhMpoI3w5ZbGCl
50ZnIXyGi16x+ewyOtlWTpZIB19/8RKs79qo4//V3PhKz/ZlqOMyKzZl+iIh0nE=
=ekgV
-----END PGP SIGNATURE-----
11 years, 1 month
Sponsorship logo(s) for docs.fedoraproject.org
by Steve Gordon
Hi all,
It's been brought to our attention [1] that unlike much of fedora's web presence the docs site doesn't currently list a hosting sponsor. If you look at fedoraproject.org this is the entity that is listed under "Hosting Sponsor" on the right hand side bar (if you CTRL+R a few times you will also see that it changes on each load depending on where the content ends up being served up from).
We discussed this in the docs meeting today and it seems like what is required is injection of some additional JavaScript into the publican-fedora brand and some HTML to use it in the side bar. There are potentially some issues with where that JavaScript comes from based on the responses from the web team on the bug but before proceeding any further those of us at the meeting just wanted to check if there were any objections to doing this?
Thanks,
Steve
[1] https://bugzilla.redhat.com/show_bug.cgi?id=611891
11 years, 1 month
Fedora Docs Meeting Reminder Mon 5 Mar 1400UTC
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There's a meeting coming up soon, please attend if you can. The Docs team
convenes at 1400UTC in #fedora-meeting on freenode.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRNEskAAoJEL1wZM0+jj2ZQmwH/22FSQXt+PUOxTUuz+qzgQe9
SsEwwInjSW4iEysd/w38hhbu6ws0Ci1a12sAInDQxMf1mzOnpzaqNWIuul/GpBTP
/L7B3R28K3nttQWsDESynSMoWd4tWTrIMndbtdWovwBVwS8ua7kx+M1wc2xk+abQ
rNJ2xcCFQyjqKEqZ56xwtq+U3y6qYOPKKhXm8p3yhPVt59qGRaf2mIH7cJedcWMc
Wuao4GW2ATJ8/ogrfe/BP+eyFWxvLF9J2rKV8xNsfv4BZXQTmhw9NzCTKx5R0wiK
ngwHPQfLDROfDeSPgCD2I5FiKqxofGxJ9nR2+vChskuDHpzbS8NxkyRtQqt4uZU=
=aMc2
-----END PGP SIGNATURE-----
11 years, 1 month
Fedora 19 schedule's new home & plans
by Jaroslav Reznik
Hi all! (and sorry for post to sooo many lists)
As we already have a final schedule (for a three weeks now) and we're
getting closer to release windmills - I'd like to make the schedule
easy to use for everyone (and that means for me too), to be sure
it makes sense etc. And inform you about recent changes I did to schedule
,plans but also I'm going to ask you for a little assistance.
These are a few changes/or requests for your feedback:
1. from F19, schedule moved to FPGM neutral site [1], you can get
there from standard wiki schedule page.
2. cleanup
Over the time, schedule got messy, some teams are even not aware what
a specific milestone means, why it's there, many times it's historical
relict and even collective memory does not work to remember what's
the reason to have it in schedule. On the other hand, I don't want
to remove anything people still relies on, based on my "common sense".
So please, take a look and let me know (some people already contacted
me and I work it in asap).
3. links in schedule
Thanks to Robyn, with her great TJ foo skillz, I'm now able to link
milestones in schedule to wiki and SOPs. Fedora QA asked for that,
I'll try to match as many as possible by myself but if you want to
link specific event to specific url, let me know.
4. future of scheduling, for F20+
For F19, we used a different way to schedule, based on the scope
of submitted features. It worked quite well from developers POV but
we completely forgot other teams and made the scheduling of theirs
tasks harder. I created a FESCo ticket [2], please take a look
(and comment it if you have ideas!). Also we would like to start
F20 as early as possible so the submission period should start
at F19 branch date (or shortly after) to let people propose the
ideas in advance.
5. new TJ3
And the main goal of the move, cleanups and so on is to jump on TJ3
board - I have initial port done, but a lot of changes are needed
and I'd like to start with TJ3 based schedule from a clean old one.
Btw. with any question, ping me, report ideas to schedule Trac [3]
and you know ;-)
Thanks
Jaroslav
[1] http://fedorapeople.org/groups/schedule
[2] https://fedorahosted.org/fesco/ticket/1092
[3] https://fedorahosted.org/fedora-project-schedule/
11 years, 1 month
