Meeting Minutes for 26 September 2011
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora_docs.20...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora_docs.20...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora_docs.20...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 13:00:20 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-26/fedora_docs.20...
.
Meeting summary
- ---------------
* Roll Call (Sparks, 13:00:28)
* Follow up on last week's action items (Sparks, 13:05:06)
* ACTION: jjmcd to send Project Wide-Final Release Notes Deadlines
(Sparks, 13:06:17)
* ACTION: zoglesby to send reminder to Trans that Final Guides POT
files are coming (Sparks, 13:06:36)
* F16 Schedule (Sparks, 13:06:49)
* LINK:
http://rbergero.fedorapeople.org/schedules/f-16/f-16-docs-tree-tasks.html
(Sparks, 13:06:57)
* jjmcd is having problems with Transifex and is unable to push
Release Notes POT files. (Sparks, 13:10:00)
* FUDcon Blacksburg (Sparks, 13:17:10)
* Docs is planning on holding a couple of classes at FUDCon Blacksburg
in January. (Sparks, 13:17:48)
* The first class will be an introduction to Fedora Docs and the
second will be an introduction to DocBook XML and Publican.
(Sparks, 13:18:21)
* Docs QA (Sparks, 13:24:53)
* ACTION: Sparks to send a message to the Docs list discussing the QA
discussion at OLF. (Sparks, 13:25:25)
* LINK:
https://lists.fedoraproject.org/pipermail/docs/2011-September/013736.html
(Sparks, 13:25:55)
* ACTION: Sparks to work on the Docs QA wiki page to start with goals,
then process, then tools. (Sparks, 13:31:59)
* LINK:
https://fedoraproject.org/wiki/Publishing_a_document_with_Publican#Publis...
(Sparks, 13:43:53)
* Guide Status (Sparks, 13:47:54)
* Security Guide has been published for F16. No major changes since
F14 version. Some chapters were rearranged. (Sparks, 13:48:22)
* Outstanding BZ Tickets (Sparks, 13:54:19)
* LINK: http://tinyurl.com/lbrq84 (Sparks, 13:54:33)
* 149 open bugs (Sparks, 13:56:17)
* Open floor discussion (Sparks, 13:56:40)
Meeting ended at 14:01:47 UTC.
Action Items
- ------------
* jjmcd to send Project Wide-Final Release Notes Deadlines
* zoglesby to send reminder to Trans that Final Guides POT files are
coming
* Sparks to send a message to the Docs list discussing the QA discussion
at OLF.
* Sparks to work on the Docs QA wiki page to start with goals, then
process, then tools.
Action Items, by person
- -----------------------
* jjmcd
* jjmcd to send Project Wide-Final Release Notes Deadlines
* Sparks
* Sparks to send a message to the Docs list discussing the QA
discussion at OLF.
* Sparks to work on the Docs QA wiki page to start with goals, then
process, then tools.
* **UNASSIGNED**
* zoglesby to send reminder to Trans that Final Guides POT files are
coming
People Present (lines said)
- ---------------------------
* Sparks (113)
* pkovar (57)
* jjmcd (31)
* jhradilek (17)
* suehle (6)
* zodbot (3)
* fnadge (2)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJOgIbpAAoJEIB2q94CS7PRxP8QAL/fwe8uY2BqAbVhkivYn8gl
y4H8PIZH914Sr2y010y6YPyJl+eq6CBKIhG7tii0lX7B9sw0IpW3EuOZbj8rXTN3
YKBsQrIxMVu5HMkpUN3Rul8+PsTDNmE0RVcos/21EACa4UIEHYhNB+hmGZdxhH7a
JTRSh5eNJ9tkPqZRMRG2zP1T8gEavHAj+ET904VI5KZPkx0D5Vv9TlX0kV0/kKIH
L3FTivthP/Wyouyvbq05XM2MQt1Fdi+XQOIR+7TIRVf4ZwdxvE+APoEZTFsxFq+K
LBr4JkIZ/MOMqj50s8D0AN2rmezQL89oooRdDYBfMCodYTfHHHp4HRtQnHCWHQ8Y
65wPoIlWD/GMqTst6/rqP3rrq1x+2eahU2YS2+p2SpYzt/c2OPXR7fj1P++6DHuX
M9O5AOOJp1HU+Pjc0x13/W/neasuE1QwPZ7gRKYhqZG/l/aiBxzB4F9xv6q9cWn0
1FLzLDM39pi378cGdpnG7f3horLywVDtKRU8lYUjqSH4iFaaIhG5ax4eQSqxJDt3
qYRTKFJkXoCAodwgME5BMbu6st2pCLc5hXxtilMav0nXwUPaS4s7C0X+htEZvcat
G2F/cq10vjeVFPDhpX6fddOJujJyYI80n/gDow0INvKk4b+R/4pNp+qGinZBgCLs
7TUc1JoPINI6eqv4q00F
=GeyM
-----END PGP SIGNATURE-----
12 years, 6 months
Common F15 bugs addition proposal: replace Gnome-Shell's Network Applet by old nm-applet
by Pedro Francisco
I believe that in the section "General buggy or missing functions in GNOME
Shell network applet<http://fedoraproject.org/wiki/Common_F15_bugs#networkmanager_shell>"
the text could be expanded.
«
----------------- EXISTING SECTION -----------------
GNOME Shell features an integrated NetworkManager configuration interface,
provided by an applet in the top panel and a configuration interface in
System Settings. However, as of Fedora 15 Beta, these tools have not yet
achieved feature parity with the configuration interface from GNOME 2,
provided by the old *nm-applet*. Some features are still missing and there
are known bugs with others. Major ones will be listed individually here, but
as a general principle, if you encounter problems or missing features trying
to configure your network using the GNOME 3 applet and System Settings
interface, you can run the standalone nm-connection-editor tool, which makes
all the operations not yet implemented in the GNOME 3 interface available.
You can launch nm-connection-editor from a console, from the alt-f2 Run
dialog, or from the overview (type *nm-connection-editor* or search for an
entry named *Network Connections*).
GNOME 3's fallback mode uses the old nm-applet, and is not subject to this
issue.
----------------- ADDED SECTION - minimal -----------------
If you wish, you may use the old nm-applet from GNOME 3's fallback mode on
GNOME Shell by running the following command as root:
# mv /usr/share/gnome-shell/js/ui/status/network.js
/usr/share/gnome-shell/js/ui/status/network.disabled
You may need to re-run this command after a GNOME Shell upgrade.
NOTE: nm-applet does not integrate well with GNOME Shell experience.
----------------- ADDED SECTION - expanded -----------------
Using the old nm-applet will fix the following issues:
- nm-applet will now remember 3G connections created on another sessions
- modem-manager will no longer require to be restarted after inserting
certain 3G dongles in order to function
- and some more issues.
»
What do you think?
Thanks in Advance
12 years, 7 months
FAD Report
by Zach Oglesby
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The following is a copy of the etherpad notes from the FAD with my notes included. Please provide feedback and ideas.
* Write an email to the legal@ list to propose:
* copyright attribution be to "Fedora Project contributors, as listed at the following URL: ____
* Update the license text on the Fedora publican brand to remove the HOLDER entity and instead have the wiki-link entity
* Spot add to Licensing page instructions on how to satisfy the attribution clause of the CC licensing (Sparks by 12 Sep)
* Propose how we should attribute back to our contributors (Sparks by 12 Sep)
We need to figure out how to give proper attribution to contributors and translators but doing so in the doc has lots of challenges. In order to fix this issue we are going to move the working of the license into the publican-fedora package and use a variable for the a wiki link that each doc will include.
* Design a QA process
* Author
* Author creates "significant" change to a document
* Create a bug assigned to Docs QA including a patch with the changed bit, and a link to the original document
* ** Wait for QA to review the patch **
* Apply patch and push to master
* Reviewer
* Review email sent to docs-qa list (We need to make docs-qa the QA contact for docs)
* Reviewer accepts bug and begins review
* Reviewer verifies content of patch for spelling errors and validity of information
* Reviewer merges content into original and verifies grammar and proper structure
* Note that the patch is good and assign the bug back to the writer
This was talked about in today's meeting and we are going to adjust this a little but keep it mostly the same. We are going to use a staging branch that is used to build draft docs, and each time you make the draft a patch will also be submitted to bugzilla including a link to the draft. Once QA looks and says the content is okay it can be moved to master.
* Document the translation process? (zoglesby 12 Sep)
* Propose change to translation process: that Translators own their translation and publish when ready
* Give translators commit and publish rights
* Bugs for a document that are against translations will be triaged by the Docs team and assigned to the appropriate translation team
We are going to start talks with the L10N team about them owning there own translations. This means that they have control of when and what is pushed to the web, and takes the guess work out for the docs team.
* Propose removing the Release Notes from the releases (RPM) and only provide this via the docs.fp.o website.
* To Docs list and to releng(a)fp.o and to blog (Sparks by 11 Sep COMPLETED)
We are talking about this on the list already.
- --
Zach Oglesby
http://zach.oglesby.co/files/public.key
https://fedoraproject.org/wiki/User:Zoglesby
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJObq3/AAoJENs2/YnyDEcH7zsH/2yoippKA1AXanHfStCX8DiT
1K6GnvDUA095ShAy6r7oLsCoFa5qgqYVfI28amhv73kcFEblkJem7Mgwbh8bNwU4
YydK99yoVR3/7/7UAPQJ/byhsOzNv/FmjaPb8l+/GB6sg6/BN1Cjinh3z1559xxV
N0SAViasnP66Ug8ZC4QudDpJMyeXl99WUbTjExHk/UB807e+iN9b115XE5mWG/qL
wm3Sc49dsdr/PZf+qdNv7/ApI2rtRwJ2Z3iMu2zO6m5yZW41zq199GfPwsWorSN6
DAWRZOGAFmLQDe8NUezZxOf1ymgPD1s5CMPL8SZfecw5dbscRVHOyoTd6zIK34g=
=U3UW
-----END PGP SIGNATURE-----
12 years, 7 months
Re: Fedora Cloud Guide sprint IRC log
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Sep 15, 2011 at 08:16:34PM -0400, Jared K. Smith wrote:
> On Thu, Sep 15, 2011 at 2:58 PM, Robyn Bergeron <rbergero(a)redhat.com> wrote:
> > Sparks and I and many others (thank you!) just chatted for an hour or so
> > in #fedora-cloud on IRC about plans for the Cloud Guide.
>
> I've taken many of the ideas thrown out in the meeting and added them
> to the outline of the Cloud Guide. If I remember correctly, they
> guide gets rebuilt every hour, so before too long you should be able
> to see the updated outline at
> https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/....
>
> If anyone else feels like helping flesh out various portions of the
> guide, feel free to let someone on the Docs team know. We'll be more
> than happy to help get your text in the proper format and so forth.
I just published the changes to the Cloud Guide (they should be available soon, look for version 16.3).
Thanks to everyone who helped get the information out yesterday. I'll try to start building on the information that was had and will get updates out soon.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJOc2bAAAoJEIB2q94CS7PRKY8P/23nILOHAKl9aTJnQ5UGowpb
eJWaSwt7MZezMnuSZ6/yiQ3FKhIBemaRP0DfwdH0G4/evAsdleobzxBJstz6P/Hc
U6v+iXRLPFgtnqmmzSBmhBioEa7AfpwQBM2lPssR7sQv8cY/gN1BT5Z/JRUe4XY9
0a53QcxdQdDI4enydZyeJcJHw6imCu+2e3VjgHBVHRh/98fUcmbk7uUM+081NZaF
GV+b0+ZlknNys7Z1S+QgO/Y8ckLd25beqoDchgzoPyB8lJLhpEcDAOriPJY9Ud3a
47VqLTx/L7ITp7RDbWuwO1L6+C1M27wuUUAKXxdSP6RdJ4LzQspWIRFJLhAQvjTH
Zp3laBygSu7IG5Xg+zMwsQmykJv4Nr3OPc86CvXxdmsaqDEyTCYAqAhClTjq62u4
bywi0w8UbRNFSFGjxUIg64tl1aChiK4YAZbM9FoDRROGPxuJ7b+Xc2971A9Prb9n
B1FH9x6MhaAbi0a+p9uCbAJZexeSKz2xKT5qtNs3aM2uahMqkiVq9oVYdCXZ33zs
iVQV8vxR8vv2tcjN1Tw15kDgZLEkxRQdwmvlgzVGEE5UrLp9alkF6sS8jhwEUl3X
kDjsfIhhzECpuM3cqtbIJgIcfBXGHwrXtIBKwg4BgXurtfSYf7vufzbPREjUOmNi
Qwua3pzT0tJyYU4u5rDW
=O+qH
-----END PGP SIGNATURE-----
12 years, 7 months
Branching and translations
by Nathan Thomas
Hi,
I've just branched the Live Image Guide for F16. Do we still file a bug
with L10N to request Transifex submissions to be switched to the new
branch, now that everything's moved to Transifex.net?
Thanks,
Nathan
12 years, 7 months
Re: [Fedora-trans-ja] Cannot edit Japanese translation of Fedora Musician's guide
by Noriko Mizumoto
Docs team
I am feeling that this can affect other languages or other books, thus
forwarding.
Someone could you please have a look at this?
(2011年09月19日 12:47), Noriko Mizumoto wrote:
> (2011年09月16日 23:16), Motohiro Kanda wrote:
>> To: Musician's guide maintainer, and Japanese translation team
>>
>> Hi,
>>
>> I logged in to Transifex and tried to translate one file from Fedora
>> Musician's guide here
>> https://www.transifex.net/projects/p/fedora-musicians-guide/resource/Ardour/
>>
>>
>> But, Translate Now button is in gray and I cannot edit the file in my
>> browser.
>> Download for translation button is also disabled.
>>
>> On the other hand, I can edit Japanese translation file for Fedora
>> Release notes here.
>> https://www.transifex.net/projects/p/fedora-release-notes/resource/Amateu...
>>
>>
>> The difference is, on Musician's guide, the dialog box says
>> Fedora Musicians' Guide » Ardour » Japanese (Japan) (ja_JP)
>> and Release note says,
>> Fedora Release Notes » Amateur_Radio » Japanese (ja)
>>
>> There seems to be a ja_JP team and ja team. Which is correct?
>>
>> Noriko-san, is this what you said in "Removing duplicate teams" mail
>> on June 21st?
>
> Yup, I've requested the merge of 'ja' and 'ja-JP', and am
> understanding that it was done.
>
>> Mr Antila, if ja is the right team, can you please move ja_JP po
>> files to ja?
>
> Chris and Dimitris,
>
> 'Fedora Project / Translation Teams' has now only one Japanese (ja)
> team [1].
> 'Team' for Fedora Musicians' Guide has correctly been set to 're-use
> Fedora Project' [2].
> However, as he said above, the member 'kandamotohiro' of Fedora
> Project Japanese (ja) team is unable to translate this guide. Also I
> 'noriko' tried same and am unable to translate as well. It says 'you
> need to be logged in and a member of Japanese (Japan) team'.
> Could you please look at this?
>
> [1]:https://fedora.transifex.net/projects/p/fedora/teams/
> [2]:https://www.transifex.net/projects/p/fedora-musicians-guide/teams/
>
> noriko
>
>
>> --
>> Motohiro
>> --
>> trans-ja mailing list
>> trans-ja(a)lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/trans-ja
>
12 years, 7 months
PM Guide Update for F15
by Jaroslav Skarvada
Hi guys,
could anybody help me to get the updated Power Management
Guide (F15 version) online? I am devel and I don't know the
docs team processes. Thanks in advance
regards
Jaroslav
P.S.: The F16 version is being worked on.
----- Forwarded Message -----
> From: "Jaroslav Skarvada" <jskarvad(a)redhat.com>
> To: "Ruediger Landmann" <rlandman(a)redhat.com>
> Sent: Monday, August 22, 2011 10:32:16 AM
> Subject: PM Guide Update for F15
> Hi Rudi,
>
> is it possible to update the PM guide for F15? I created
> updated draft:
>
> http://jskarvad.fedorapeople.org/doc/power-management-guide/
>
> There is also the GIT patch. Feel free to change/improve
> the wording, I am not the native speaker ;) but all
> important up-to-date information should be there
>
> Thanks & regards
>
> Jaroslav
12 years, 7 months
Removing the Fedora Release Notes from the releases.
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Twice a year the Fedora Docs team runs around with their hair on fire trying to get the Release Notes bits put together, translated, and packaged. The packaging requirement puts a lot of strain on the process, though, as thousands of lines of code go into the documentation, they are all new every release, and most of the time are only available at the last minute based on changes to code in other programs.
To reduce the strain on the process I'd like to propose that the Release Notes not be packaged (in RPM) and included in the releases and only be made available on the Fedora Docs website.
Comments, questions, remarks?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJObNehAAoJEIB2q94CS7PR9DIQAKc54kYHQHa128NKpee9OrdU
yWSZ8xs9+BKDP3MGveP7oy7iLjSNS/uefpEhTNhowgewncZ8h7hm9Qwlx97q9YL+
OZYWiMR3sp9+ebHpM9sOIFDV7sCbWeiwHDJtTlDvu8zENv27PXBjfjvKmhUHXGG6
vy6xx5eUjK7u79XzvZ+KbNL/jm9fc8ZE+8gWvBsLG7EPbrloYpy+IgtmF5EiaNVF
P2ACVAvhnpDfBKPCjIriLcHbz874xTUDtoX+ubFQppW4jwaKva6PShepnfbbzdsy
fV1stZWRBYqEGurxWfp9hHguhnYYJtfQyqYaitvfGDe+GEN9j04ztjXMOlta9q61
whGc3/6WSz+k82JcSj7Qmk2MgsSmkur+nAXU1F7VnEf5/PTzhADKpfTXiWjuumTM
wLfe1Plb2u6ygAC0ZyxjreNkWGjh7nMzyJx0QreDKPbKWIMJ9+x1MoSMQeClQpf7
z6rp/JR2pLB3Gx9+JAc58PaI7EjKhgHe9c0Acgm7kCwUJLdm/NEMQYRepbHVBBWo
e3KFwb7VDvGx2BXACjhQZZNAumrmLyqEIOADri2MJZrqxFxpgWrPQxWHyd0U/L4o
2/mCOPK6n2EVwfKhfod5BaaZozR3MJ6M9bJOYzOfroA60G1nzwgK0da7C9PyLrGW
X38vHBgaZ/j9jKz1QPtM
=vFkE
-----END PGP SIGNATURE-----
12 years, 7 months
