Meeting Minutes 6-Apr-11
by John J. McDonough
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2011-04-06/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2011-04-06/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2011-04-06/fedora_docs.20...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 23:02:18 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2011-04-06/fedora_docs.20...
.
Meeting summary
---------------
* Roll Call (Sparks, 23:02:23)
* Follow up on last week's action items (jjmcd, 23:05:53)
* ACTION: jjmcd to contact shell maintainer about a Documentation
category in shell (jjmcd, 23:06:36)
* Fedora 15 Schedule (jjmcd, 23:07:17)
* Release Notes (jjmcd, 23:11:53)
* Guide Status (jjmcd, 23:27:57)
* Outstanding BZ Tickets (jjmcd, 23:35:55)
* LINK: http://tinyurl.com/lbrq84 (jjmcd, 23:36:03)
* Open floor discussion (jjmcd, 23:38:33)
Meeting ended at 23:42:07 UTC.
Action Items
------------
* jjmcd to contact shell maintainer about a Documentation category in
shell
Action Items, by person
-----------------------
* jjmcd
* jjmcd to contact shell maintainer about a Documentation category in
shell
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jjmcd (92)
* rudi_ (10)
* Sparks (8)
* sgordon (8)
* zodbot (4)
* jhradilek (3)
* rbergeron (1)
* dmaxel (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
13 years
Release Notes draft
by John J. McDonough
Please review release notes at
http://fedorapeople.org/groups/docs/release-notes/en-US/
I will shortly be making an RPM. I will make an en-US RPM that will end
up in the wrong place on XFCE/LXDE and have no index entries. Those
will have to wait for later. The notes haven't even been branched yet,
let alone translated.
A lot of folks made last minute contributions to the beats. I thank
them for their efforts. We've been running late this entire release and
every little bit helps a lot.
--McD
13 years
Re: Docs QA
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello:
I absolutely agree with the need for a better QA process, and I also support
the proposed actions here. This particular process would also make it easy for
people to contribute when they have time/interest, and let other people pick
up the slack when they don't have time/interest.
Christopher
> Message: 10
> Date: Sun, 3 Apr 2011 16:59:52 -0400
> From: "Eric H. Christensen" <sparks(a)fedoraproject.org>
> Subject: Docs QA
> To: docs-qa(a)lists.fedoraproject.org, docs(a)lists.fedoraproject.org
> Message-ID: <20110403205952.GA26169(a)christensenplace.us>
> Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
>
> Not enough information to check signature validity. Show Details
>
> A while back we discussed putting together a group of editors that would
> review changes and guides to make sure they were correct and written
> well. Since then little has happened. The biggest issue has been extra
> cycles in peoples' day and I can appreciate that. This is an important
> task that anyone with a little time can help out with. It's especially
> good for newbies that want to become involved but aren't familiar with
> DocBook and the like as they can see what we are writing and how we are
> writing.
>
> With that said, I'd like to propose the following:
>
> 1) We change the QA on all components in BZ to docs-qa(a)l.fp.o so interested
> QAers can subscribe to that list and see when QA is needed. We also need
> to setup docs-qa in BZ and maybe have it send a message only when the the
> ticket is set to MODIFIED and ON_QA (I think this is possible).
>
> 2) Create a wiki page outlining the purpose and mission of docs-qa and
> provide guidelines for what to check for.
>
> 3) Create a wiki page outlining the guidelines for QA in the bug-handling
> process.
>
> Thoughts?
>
> --Eric
>
> End of signed message
> ------------------------------
>
> --
> docs mailing list
> docs(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/docs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQEcBAEBAgAGBQJNml7oAAoJEInCktGVqZ8VBOIIAIVe/FiTKAnD7/k+mwcaMv7T
pq7e6wH+QLEtD2IHI82wUTy6I4Svr87XaxwDhhwTWcxszQm5LWi1eX2UiLo5c+qY
2SSqu0AFI+AhSKrrHcr/Uq4VzpKcqvZEyRoyXwo9LEjRWQUjfkOkKYs74kxIERvZ
JZG0911ceUPIVzfMa4nkA87mpwZFrXCmD/A+XubhwmiQpLn3r2rDZdTo8FzOlXqY
6/4qx5nUun8r4PJWk5jS5xmNk96uB1x2OXQAY3qs3T94Za5tJZ0XG3h8qdY/vD7i
KuzDJBFSdl4VmXyhGeOMjNzNFzVzJ5w+rU0s2PBhZTS6IZpLwjTTzYm62ZH8kWw=
=tzto
-----END PGP SIGNATURE-----
13 years
Do we need a documentation application?
by John J. McDonough
In GNOME 3 the whole concept of menus is gone. This means, among other
things, that there is no Documentation menu. There are a number of
categories:
Accessories
Games
Graphics
Internet
Office
Others
Sound & Video
System Tools
There is also an 'All' category, but this only includes applications
that are in one of the other categories. An application must be
specifically placed in the 'Other' category to appear there.
I could see putting the Release Notes in "System Tools", but it doesn't
seem to me that documentation in general belongs there. Yelp is in
"Accessories", but that category is already cluttered, and I can see
"System Tools" getting pretty cluttered, too.
To further complicate the matter, previously GNOME, XFCE and LXDE could
all share a .desktop file. It looks as if now a unique file will be
required for GNOME.
Were we to have some sort of Documentation application we could then
have something like update-desktop-database that would run on install.
This would allow us to have single-language RPMs and still maintain
consistent Fedora-like language behavior. I can't say I'm really
thrilled with this, but it is an alternative.
Another alternative would be to go back to installing a separate set of
documentation for Yelp, and let it deal with all the GNOME weirdness.
Or, perhaps we can press shaunm to get Yelp working smoothly for html
documentation. I have to admit I haven't played much with Yelp on
Fedora 15, and I know there has been substantial work done.
--McD
13 years
Docs QA
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
A while back we discussed putting together a group of editors that would review changes and guides to make sure they were correct and written well. Since then little has happened. The biggest issue has been extra cycles in peoples' day and I can appreciate that. This is an important task that anyone with a little time can help out with. It's especially good for newbies that want to become involved but aren't familiar with DocBook and the like as they can see what we are writing and *how* we are writing.
With that said, I'd like to propose the following:
1) We change the QA on all components in BZ to docs-qa(a)l.fp.o so interested QAers can subscribe to that list and see when QA is needed. We also need to setup docs-qa in BZ and maybe have it send a message only when the the ticket is set to MODIFIED and ON_QA (I think this is possible).
2) Create a wiki page outlining the purpose and mission of docs-qa and provide guidelines for what to check for.
3) Create a wiki page outlining the guidelines for QA in the bug-handling process.
Thoughts?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAk2Y38cACgkQU03aaJDMNEUHewD/SQZbVNfwXFNId48nkeEw1VCR
F1M3emNRYTtrKfk9pKIA/1p56T+fNpmoi3gUGWwZQOO/oOQXzltOkW4wAY7efSQC
=SVzt
-----END PGP SIGNATURE-----
13 years
Talking about seahorse in OpenSSH guide.
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I was working on a couple sections of the OpenSSH guide and I wondered if it would be useful to discuss seahorse in that guide for the PKI key management or if that should go somewhere else.
Thoughts?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAk2YnQsACgkQU03aaJDMNEVvxAD9HrttHJYVkK+ido2U+73VJKui
zF+lwTXvoX1FqDHPDOcBAJwS49LYs4iAT/ajK+OHMCcK4EhuOgTtLSsw201Roaw0
=gY8K
-----END PGP SIGNATURE-----
13 years
OpenSSH Guide in need of love
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I just found an OpenSSH guide that Scott (Radsy) started almost a year ago that already has some really good work in it but needs a little love to finish it off. Perhaps someone with a few extra cycles could take a look?
The book is on Fedora Hosted[0] and can be downloaded from the SVN repo.
[0] https://fedorahosted.org/openssh-guide/
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAk2Xuu4ACgkQU03aaJDMNEXuegD/VCmCZuUt1WEjQb3BHFw7OsCf
8Q8W/i9sny1ciF5g4E8A/3izNokpOMzSDP+LjcIjbwEsMN+HTlD1dOe75tJ/pEiv
=zotf
-----END PGP SIGNATURE-----
13 years
SVN Permissions
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Earlier today nb and ricky helped me with a permissions error on the Security Guide's SVN. Apparently the new group "docs-writers" didn't get propagated to the SVN guides. This has been remedied now and includes a fix to openssh-guide, wireless-guide, accessibility-guide (already moved to git?), Deployment_Guide, selinux-faq, and selinuxguide. If you work on these guides please make sure you can still access these repositories.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAk2XtwcACgkQU03aaJDMNEWyZQD/SlHJmloi9NYKtDMQdNwhI0uO
Ed68BQGJWoLXB6Z1ye4A/0vyyXJAUoi3i5R2d8CDb6Nf1QBgc0mxfqHrx5FavKyq
=QLlk
-----END PGP SIGNATURE-----
13 years
Release Notes Beats closing
by John J. McDonough
I will be converting the remaining beats tomorrow. If there are any
last minute additions, get them in now.
--McD
13 years
