Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: typo in PV-Configuring_Additional_Devices
https://bugzilla.redhat.com/show_bug.cgi?id=755744
Summary: typo in PV-Configuring_Additional_Devices
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: virtualization-guide
AssignedTo: docs(a)lists.fedoraproject.org
ReportedBy: shaiton(a)fedoraproject.org
QAContact: nobody(a)fedoraproject.org
CC: kwade(a)redhat.com, oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Type: ---
>From the file available in transifex,
Now you can configure the new network interfaces using
<command>redhat-config-network</command> or Red Hat Enterprise Linux3 or
<command>system-config-network</command> on Red Hat Enterprise Linux 4 and Red
Hat Enterprise Linux 5.
that should be "on" Red Hat.
I could have corrected that now that I have git access, but this git is still
for F14… There were plenty of update about virt since F14, is it outdated?
http://fedoraproject.org/wiki/Docs_Project_meetings#Guides
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: How to increase the number of configured loop devices
https://bugzilla.redhat.com/show_bug.cgi?id=693536
Summary: How to increase the number of configured loop devices
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: virtualization-guide
AssignedTo: fedora-docs-list(a)redhat.com
ReportedBy: apevec(a)redhat.com
QAContact: nobody(a)fedoraproject.org
CC: stickster(a)gmail.com, kwade(a)redhat.com,
oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sec…
Number of loop devices cannot be changed via modprobe.conf since loop is not a
kernel module anymore:
# grep DEV_LOOP /boot/config-2.6.34.8-68.fc13.x86_64
CONFIG_BLK_DEV_LOOP=y
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=846864
Bug ID: 846864
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: docs(a)lists.fedoraproject.org
Assignee: laine(a)redhat.com
Summary: Need a list of toolsets and when they are appropriate
in the virt Getting Started guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: laine(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-getting-started-guide
Product: Fedora Documentation
The Getting Started Guide needs an overview of all the different toolsets, and
when each would be appropriate. In particular I'm talking about the following:
1) gnome-boxes
2) virt-manager
3) virsh, virt-install
4) ovirt
5) Should we point some people to OpenStack?
I will write up a first draft of this, and hand it to a qualified docs person
to edit and correctly place in the guide.
--
You are receiving this mail because:
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: docs.fp.o landing page needs 'Start here' note!
https://bugzilla.redhat.com/show_bug.cgi?id=627417
Summary: docs.fp.o landing page needs 'Start here' note!
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: nathan.thomas(a)peacenik.co.uk
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com,
nb(a)fedoraproject.org
Classification: Fedora
Description of problem:
We have a large variety of documentation guides serving a wide range of
different users. It may be difficult for users arriving at docs.fp.o to know
where to start, especially if they are new to Fedora/Linux and are unfamiliar
with some of the technical terms.
A note on the landing page suggesting a sensible starting point for new users
could help alleviate this problem. Eg:
"New to Fedora? You can try Fedora on your PC without touching your existing
installation by following the Live Image Guide."
The end of the Live Image guide helpfully points users to the Installation
guide if they want to install :)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: New Bugzilla component for Storage Administration Guide
https://bugzilla.redhat.com/show_bug.cgi?id=654484
Summary: New Bugzilla component for Storage Administration
Guide
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: r.landmann(a)redhat.com
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com,
nb(a)fedoraproject.org
Classification: Fedora
Target Release: ---
Please create a component for the Storage Administration Guide; default
assignee should be ddomingo(a)redhat.com
Cheers
Rudi
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=839625
Bug ID: 839625
QA Contact: docs(a)lists.fedoraproject.org
Severity: medium
Version: devel
Priority: medium
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com,
stickster(a)gmail.com
Assignee: nobody(a)fedoraproject.org
Summary: Configuring_an_IPA_Client_on_AIX instructs to
configure sshd with 'GSSAPITrustDNS' which causes sshd
to no longer start
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: chorn(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: docs-requests
Product: Fedora Documentation
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/17/html/FreeIPA_Guide/Configurin…
instructs to set 'GSSAPITrustDNS no' in /etc/ssh/sshd_config .
Version-Release number of selected component (if applicable):
current / fedora [15|16|17] instructions
How reproducible:
always
Steps to Reproduce:
1. access webpage
2. implement change
3. try to start sshd
Actual results:
sshd no longer starts
Expected results:
sshd should start
Additional info:
- GSSAPITrustDNS is a ssh client option
- its not mentioned in the manpage but recognized
-
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_…
mentions it as client option
- http://freeipa.com/page/ConfiguringAixClients looks like the most current
howto and does not mention the option at all. I think just removing the option
from the webpage is the most simple way to resolve this (recheck whole howto
with an AIX client for bonus)
--
You are receiving this mail because:
You are the QA Contact for the bug.
#5214: Setup koji tags and repo for Docs
-----------------------------+------------------------
Reporter: crantila | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 18 Alpha | Component: koji
Keywords: docs | Blocked By:
Blocking: |
-----------------------------+------------------------
Posted here as per [https://fedorahosted.org/fedora-
infrastructure/ticket/3320]
'''phenomenon'''
To support simpler and more robust updates to docs.fp.o, need to setup
koji to handle a new tag and repo for Docs.
'''implementation recommendation'''
<Sparks> What would be required to stand up a separate instance of koji
for Docs? <dgilmore> Sparks: why would you want a seperate instance?
<dgilmore> Sparks: i dont see any valid reason to do so <Sparks> dgilmore:
For the Docs website. Publican has the ability publish documentation from
packages (separate repo from the Fedora repo) for the website. We want to
replace the git repo that operates it now. <dgilmore> Sparks: and why does
that need a seperate koji? <Sparks> The git repo has gotten HUGE and is
becoming an issue. <dgilmore> Sparks: so, why does that mean a seperate
koji instance <dgilmore> Sparks: we could use a seperate tag and targets
in koji <dgilmore> i dont see why it would need its own koji <Sparks>
dgilmore: It's either that or try to get everyone setup as packagers.
<dgilmore> Sparks: get everyone setup as packagers <Sparks> dgilmore:
Except that they really won't be packagers. <dgilmore> Sparks: though you
dont need to be a a packager to get a koji cert <dgilmore> you just need
fas <dgilmore> Sparks: what would be the workflow? <Sparks> dgilmore:
Okay, and with that we can send packages through koji and tag them
separately? <Sparks> dgilmore: Basically we just tell Publican to build
the package and submit it to koji. The Publican software does all the
work. <dgilmore> Sparks: I still really dont know what your trying to do.
pretend im an idiot(not really that hard) and explain what it is and how
it should work <Sparks> dgilmore: I'm not far off... <Sparks> dgilmore: So
Publican will make an SRPM package, submit it to koji destined for a repo.
Our Publican backend will install those packages and publish the data to
the website. <Sparks> ...as I understand it <dgilmore> Sparks: so we would
need to set up seperate tags and tagets for it, defining a koji policy
allowing srpms to be built. likely we would add a new group to koji and
add people allowed to build docs to it and limit access to the
tags/targets to people in that group <dgilmore> Sparks: so its all doable
<Sparks> dgilmore: Well that's a lot easier. :) <Sparks> dgilmore: We
already have a group in FAS for people that should have access (docs-
publishers). Should I open a ticket? <dgilmore> Sparks: koji doesnt know
anything about fas <dgilmore> Sparks: please file a ticket. We wont be
able to make changes until after f17 is done <Sparks> dgilmore: That's
fine. We're not completely ready for the transition so after F17 would be
good. <Sparks> dgilmore: Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5214>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
https://bugzilla.redhat.com/show_bug.cgi?id=833223
Bug ID: 833223
QA Contact: docs(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com,
stickster(a)gmail.com
Assignee: nobody(a)fedoraproject.org
Summary: Adding lang_map to docsite-publican
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: kev.raymond(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: docs-requests
Product: Fedora Documentation
docsite-publican still not use the config_map syntax in .tx/config file.
See
http://fedoraproject.org/wiki/Setting_up_a_document_with_Transifex#Step_5:_…
--
You are receiving this mail because:
You are the QA Contact for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=450331
Summary: lack of documentation on restoring from bare-metal (UUID
problem)
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: docs-requests
AssignedTo: kwade(a)redhat.com
ReportedBy: czar(a)acm.org
QAContact: stickster(a)gmail.com
CC: fedora-docs-list(a)redhat.com
Description of problem:
ref: https://bugzilla.redhat.com/show_bug.cgi?id=449299
There is a lack of documentation on restoring a system from bare metal. I have
found (see reference) that restore the root ("/") is not as simple as as just
executing the restore command when running in rescue mode.
With the current emphasis being place on use of UUIDs in both Fedora and RHEL,
the whole business of UUIDs need to be better documented.
Version-Release number of selected component (if applicable):
Fedora 9
--
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, or are watching someone who is.
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
https://bugzilla.redhat.com/show_bug.cgi?id=857405
Bug ID: 857405
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: kwade(a)redhat.com, nathan(a)afternoondust.co.uk,
oglesbyzm(a)gmail.com
Assignee: docs(a)lists.fedoraproject.org
Summary: Readme Live Image isn't branched for F17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: shnurapet(a)fedoraproject.org
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: readme-live-image
Product: Fedora Documentation
The guide isn't maintained, it needs to be branched for Fedora 17.
--
You are receiving this mail because:
You are the assignee for the bug.
Hello,
this is in reaction to Pete's mail on fedora-announce-list. I am working
on an experimental fork of yum:
https://fedoraproject.org/wiki/Features/DNF
The package is available in F18 and I'd like it to be mentioned in the
release notes.
Many thanks,
Ales Kozumplik
On 09/18/2012 02:24 AM, Pete Travis wrote:
> Greetings!
>
> As the Fedora Documentation Project prepares the release notes for
> Fedora 18, we'd like to ask for your help. Each Fedora release marks
> the inclusion of new features and the retirement of others, and with
> the help of the development community, we won't skip a beat. The Docs
> team would like you to assign us some homework.
>
> The release notes are divided up into categories, or 'beats.' Each
> beat is kept by a volunteer who follows mailing lists, changelogs,
> announcements, and features in the space. Many beats also have a
> developer point of contact for technical questions and cooperation. We
> track these responsibilities with
> http://fedoraproject.org/wiki/Category:Documentation_beats , which
> includes links out to wiki pages for each individual beat. As we
> reach the end of the release cycle, developers and docs maintainers
> populate these pages, then they are converted from wiki markup to
> Docbook XML and published. With a little help, we can put out release
> notes that can't be beat.
>
> If you're working on something for Fedora, we'd like to make sure
> you get the credit you deserve. Leave us a quick note on a beats page,
> send it to our mailing list (
> http://lists.fedoraproject.org/mailman/listinfo/docs ), or join us in
> #fedora-docs. You don't need to worry about language and composition
> or even spelling - just let us know what you've been working on that
> you'd like documented and we'll take it from there.
>
> We *really* don't want you to beat yourself up about presentation.
> A simple "make sure you mention this new feature" is enough. We're
> happy to do the research and compose the prose. Knowing where to start
> writing makes the process considerably more efficient, just as a brief
> note on hundreds of features from each developer is more effective
> than a handful of docs maintainers trying to follow all of hundreds of
> features.
>
> Thanks for helping us represent your work to the users,
>
> Pete Travis,
> The Fedora Docs Team
> _______________________________________________
> devel-announce mailing list
> devel-announce(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel-announce
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
https://bugzilla.redhat.com/show_bug.cgi?id=853826
Bug ID: 853826
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: low
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: docs(a)lists.fedoraproject.org
Summary: Section 3.1 - suggest adding "Less Down Time" verbiage
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: joat(a)757.org
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-guide
Product: Fedora Documentation
Description of problem: In Section 3.1, of the Draft Virtualization Guide for
Fedora 18, suggest adding something similar to the following:
"Less Down Time
VMs can be copied or moved, configuration changes can be validated, and
software updates can be tested without impacting the users' online experience."
Version-Release number of selected component (if applicable): 18
How reproducible: Not a fault.
Steps to Reproduce: N/A
Actual results: N/A
Expected results: N/A
Additional info:
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=856116
Bug ID: 856116
QA Contact: docs(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com,
stickster(a)gmail.com
Assignee: nobody(a)fedoraproject.org
Summary: Please create the cloud guide component (+typo)
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: kraymond(a)shaiton.org
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: docs-requests
Product: Fedora Documentation
Hi there,
I wanted to report a typo but could not find the cloud guide component.
Could you create it please?
Also, here is the typo:
"argee" instead of "agree".
See
https://fedora.transifex.com/projects/p/fedora-cloud-guide/resource/AmazonE…
Thanks to eko ikhyar to have reported this on the l10n mailing list.
--
You are receiving this mail because:
You are the QA Contact for the bug.
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
Hi all,
My name is Fedora and I am a French ambassador. Since Fedora 16, I
write the announce in French for the new Fedora release.
The French team, who translate Fedora, found the release notes written
enough, too short and not suitable for public. It's difficult to
translate and understand these documents.
It is more a concatenation of all provided strings without so much flourish.
I think, the releases notes require to many skills in "data processing"
to understand the news in Fedora. For me, it's the official document to
communicate the changelog with the public and actually, it's not
possible with that.
With the French team, we thought to write the release notes in French
and translate that in English for others translation team.
If you are ok to this project, I can write the document before the 17th
September, it's sufficient for others translation in future.
That could be a Publican replacement for the usual Release Notes. I
don't master yet Publican but I am willing to learn.
In short, the idea is to provide the Release Notes for Fedora 18 in a
detail document avoiding the usual phrasing like bellow:
" Desktop - GNOME has been updated to the latest release XX;
- KDE has been updated to the latest release YY;
- Mate has been packaged for the first time in Fedora.."
The original document would be written in French but translated in
English throught Transifex. Of course, we would need English people to
proofread and improve our translation.
You can read my precedent work for that (Fedora 16 and 17) :
https://fedoraproject.org/wiki/User:Renault/Promotion/Fedora_17https://fedoraproject.org/wiki/User:Renault/Promotion/Fedora_16
It is more detailed, explained and written.Briefly, for a wide
dissemination.
Thank you for giving me your opinion on the subject.
Charles-Antoine Couret — Renault
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/29/2012 05:28 PM, Adam D. Ligas wrote:
> Hey Eric!
>
> I wrote a very tiny section of the security guide - the bit on
> 7-Zip - and I was looking to revisit it to make a couple updates
> since there has been some change in this space for F17+.
Yes, I noticed that you had made some changes to the wiki page.
Unfortunately is not current with what's in the Security Guide since
development has moved over to the XML files in git. I can make the
changes you've pointed out or you can do so, yourself, in git.
> The second update I want to make is to the navigation paths to
> Terminal. They need to be updated from:
>
> Applications -> System Tools -> Terminal to Activities ->
> Applications -> Terminal
Yeah, this would only be in GNOME 3 and I wonder what other changes
need to be made else where. I'm not sure how to really deal with the
difference between GNOME 3 and other desktop environments.
> The third update I wanted to do was add a new section for creating
> the archives via the GUI. This wasn't possible before, and I
> imagine it will be a lot easier for some folks. That one is
> longer, so I attached it to this email.
Got it. As I said above I can add it myself or you are welcome to do so.
> The last update I wanted to make was to update my credit. Given
> how much I've contributed it is almost silly that I'm credited at
> all, but it is certainly appreciated. If my email address could be
> changed to agent86(a)fedoraproject.org, that would be awesome. Then
> I'll look like everyone else, and it'll be easier for when my email
> moves in the future.
No contribution is too small (or too big!). I'll update your email
address in the author list.
> I'm not sure if it is a major no-no or not, but I also updated the
> wiki (https://fedoraproject.org/wiki/Archive:Security_Guide/7Zip)
> It looks like things have migrated into a new Fedora Documentation
> system I am unfamiliar with, but if nothing else, I thought the
> edits in the wiki might be easier for you to pull than the one
> attached.
Yeah, those wiki pages are dead and need to be removed (they are
already in Archive:). All SG development is in git.
>
> - Adam
>
Thanks for your updates! I've cc'd the Docs list so we have a public
record of the conversation and your contribution.
Just let me know if you would like to make those changes in git or
not. If you need some assistance just let me or someone else know and
we can help you out there.
- -Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQRfsTAAoJEIB2q94CS7PRkBkQALwTvqj2PqfZniqfE8FwNieQ
GXmPJO1SgoZzpbz13EAXql+cHxTmOSHhBYRmQjAWWV8y1kNncgRy7ln2YbIQmvSB
YnXG7BTe+gCznZyfL7qMaQUFMNWeOBEn39g27g49aR9cwz7JdaJSv/bqr1M0v5uU
SQnMa9OdgUbLHee/ZSS74mfedzu61SCAoB8SSdHr64dF8/IhJY+oDFE7kZ2EEKWX
Urzf12sNliVAh3ogl04pMH6hLqm1j2z4VT/hx7DAEughRUOIGlnnlvAXrN00MFWa
ZgpWqeeETCO0RlDb75fL3LfMcROr/zUKMZ6EGuzKbNM0N69Kh++FhQnUfkhZugQs
czxPNXmZxvZwQr8dukl+n8bSwlLVSZKOPi0ffuurwqVF09zoWOxiqB4QzN3qe4mi
Qr341nQDOwQ7gT4icKcs+ffqvsSDke+lt0/kfgK500J2ojEmtO+LqtHRvgTyP6v+
TEcBc0Q3z2BAMH/4Ich1iSude7dqPtPId+OcG9kLEWDMGZKCzCsTsptzL3Ry4Tp6
S6e72GTVfv8q/6g2UAxj2oTzkBz39+fnSbvMQO0NV2pU69Aidh7me5uDVdUKbJQo
+AgqBtm7GNVgGBUNb56e/JPDEGmZEhoJgJqVO8Wx9WVjz7QHLzJiewOEl4/sw+vJ
3QC5IBLoEW1G71vq7J64
=JT8W
-----END PGP SIGNATURE-----
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by bcotton at 14:00:14 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2012-09-03/fedora_docs.2012…
Meeting summary
---------------
* Roll Call (bcotton, 14:00:27)
* Follow up on last week's action items (bcotton, 14:05:15)
* ACTION: Sparks to add relevant git commands to QA procedures
(bcotton, 14:05:30)
* Release Notes (bcotton, 14:05:39)
* Alpha RN (one page) due 11 September (bcotton, 14:06:04)
* wiki beats due 19 September (bcotton, 14:06:22)
* HELP: There are still open beats that need to be written (bcotton,
14:07:07)
* LINK: https://fedoraproject.org/wiki/Docs/Beats (bcotton,
14:07:23)
* Fedora 18 schedule (bcotton, 14:08:44)
* LINK:
http://jreznik.fedorapeople.org/schedules/f-18/f-18-docs-tasks.html
(bcotton, 14:08:55)
* Alpha release date has slipped by a week again. (bcotton, 14:09:14)
* Guides scheduled to be branched 25 September (bcotton, 14:09:45)
* Outstanding BZ Tickets (bcotton, 14:11:59)
* LINK: http://tinyurl.com/lbrq84 (bcotton, 14:12:08)
* Open floor discussion (bcotton, 14:12:21)
Meeting ended at 14:14:11 UTC.
Action Items
------------
* Sparks to add relevant git commands to QA procedures
Action Items, by person
-----------------------
* **UNASSIGNED**
* Sparks to add relevant git commands to QA procedures
People Present (lines said)
---------------------------
* bcotton (29)
* zodbot (3)
* jhradilek (1)
* pkovar (1)
* jreznik (1)
* Capesteve (1)
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2012-09-03/fedora_docs.2012…
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2012-09-03/fedora_docs.2012…
Log: http://meetbot.fedoraproject.org/fedora-meeting/2012-09-03/fedora_docs.2012…
--
Ben Cotton
Fedora Docs Leader
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.