[Bug 500153] New: Bad lock managment between CIFS and NFSv4 (kernel) access
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: Bad lock managment between CIFS and NFSv4 (kernel) access
https://bugzilla.redhat.com/show_bug.cgi?id=500153
Summary: Bad lock managment between CIFS and NFSv4 (kernel)
access
Product: Fedora Hosted Projects
Version: unspecified
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: Deployment_Guide
AssignedTo: mhideo(a)redhat.com
ReportedBy: meflah_kader(a)emc.com
QAContact: rlerch(a)redhat.com
CC: fedora-docs-list(a)redhat.com
Classification: Fedora
Target Release: ---
Description of problem:
client1 CIFS: lock SHARED range:16384-40959
client2 NFSV4: all lock SHARED succeed for any range and then unlock
but lock EXCLUSIVE range 8192-24575 succeeds instead of failure
Version-Release number of selected component (if applicable):
Fedora release 9
How reproducible:
I use a specific test with two clients (CIFS-NFS(via nfsv4 mount point))
Steps to Reproduce:
1. CIFS SHARED lock range:16384-40959
2. NFS (via v4 mount point): EXCLUSIVE lock range:8192-24575
3.
Actual results:
Second lock succeeds
Expected results:
Failure
Additional info:
1/ The is no NFSv4 lock operation conveyed via network traces
2/ The issue doesn't exist in Redhat Enterprise Linux Server release 5.1
(Tikanga)
3/ Here is the complete trace of client test
Client:1 Server:SX0305KA User:......................... UNICODE Negotiation
SUCCEEDED
Client:1 Share:\\SX0305KA\SVR5LOCKNO! ................ Tree connect
(Tid:0x003F): SUCCESS
Client:1 File:\\SX0305KA\SVR5LOCKNO\toto_25674\lockfile! openX Access_mode:RW
Share:DENY_NONE SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS open SUCCESS
Client:1 File:\\SX0305KA\SVR5LOCKNO\toto_25674\lockfile! lockX SHARED
range:0x4000-0x9fff : SUCCESS
Client:1 INFO :! Segment 7
(range:16384-40959)! is locked for Shared access
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 0-8191 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 0-8191 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 0-16383 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 0-16383 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 8192-24575 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 8192-24575 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 16384-24575 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 16384-24575 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 24576-32767 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 24576-32767 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 32768-40959 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 32768-40959 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 16384-40959 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 16384-40959 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 8192-49151 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 8192-49151 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 32768-49151 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 32768-49151 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 40960-57343 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 40960-57343 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock SHARED
range: 49152-57343 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 49152-57343 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock EXCLUSIVE
range: 0-8191 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 0-8191 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock EXCLUSIVE
range: 0-16383 : SUCCESS
Client:2 File /tmp/KADER/nolock/toto_25674/lockfile! NFS lock UNLOCK
range: 0-16383 : SUCCESS
Client:2 ERROR:? File /tmp/KADER/nolock/toto_25674/lockfile? NFS lock
EXCLUSIVE range: 8192-24575 : SUCCESS instead of "Resource temporarily
unavailable"
--
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.
14 years, 11 months
[Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]]
by Ruediger Landmann
-------- Original Message --------
Subject: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]
Date: Thu, 21 May 2009 11:16:56 +1000
From: Christopher Curran <ccurran(a)redhat.com>
To: Lana Brindley <lbrindle(a)redhat.com>
CC: Joshua Wulf <jwulf(a)redhat.com>, content-services-staff(a)redhat.com
References: <4A14A4D0.40207(a)redhat.com> <4A14A6E1.6040702(a)redhat.com>
Lana Brindley wrote:
> Joshua Wulf wrote:
>> Satya is doing a WYSIWYG docbook editor as a Google SOC project in
>> Fedora. He wants feedback on what tags to provide support for. Please
>> take a look at this list and give some feedback on tags that we use
>> that are not covered in it.
>>
>> - Josh
>>
>> -------- Original Message --------
>> Subject: Re: Proposal for Implementing a Docbook Editor
>> Date: Wed, 20 May 2009 21:47:25 +0530
>> From: satya komaragiri <satya.komaragiri(a)gmail.com>
>> Reply-To: For participants of the Documentation Project
>> <fedora-docs-list(a)redhat.com>
>> To: For participants of the Documentation Project
>> <fedora-docs-list(a)redhat.com>
>>
>>
>>
>> Hello,
>>
>> I have narrowed down to the following set of tags as the minimum that
>> Docbook editor will need to support for the initial stages of the
>> project. It would be great if the list could review them once and
>> suggest any additions/deletions.
>>
>>
>> tags:
>>
>> Top Level:
>> <article id="ID">
>> </article>
>>
>>
>>
>> Section:
>> <section id="ID">
>> <title></title>
>> </section>
>>
>>
>>
>> Block Tags:
>> <para></para>
>> <screen></screen>
> <programlisting></programlisting>
>>
>> <itemizedlist>
> <title></title>
>> <listitem>
>> <para></para>
>> </listitem>
>> </itemizedlist>
>>
>> <orderedlist>
> <title></title>
>> <listitem>
>> <para></para>
>> </listitem>
>> <orderedlist>
>>
>> <procedure>
>> <step>
>> <para>
>> </para>
>> </step>
>> </procedure>
>>
>> <important>
>>
>> <title></title>
>> <para></para>
>> </important>
>>
>> <tip>
>> <title></title>
>> <para></para>
>> </tip>
>>
>> <note>
>> <title></title>
>> <para></para>
>> </note>
>>
>> <warning>
>> <title></title>
>> <para></para>
>> </warning>
>>
>> <caution>
>> <title></title>
>> <para></para>
>>
>> </caution>
>>
>>
>>
>>
>> Inline:
>>
>> <firstterm></firstterm>
>> <application></application>
>>
>>
>> <command>
>> <option></option>
>>
>> </command>
>>
>> <package></package>
>> <filename></filename>
>> <systemitem></systemitem>
>> <computeroutput></computeroutput>
>
> Is this tag the same as <programlisting>? I don't know it.
>
programlisting is for a block of preformatted code. computeroutput is
for a single inline output snippet.
>> <userinput></userinput>
>>
>> <prompt></prompt>
>>
>>
>> <menuchoice>
>> <guimenu></guimenu>
>> <guisubmenu></guisubmenu>
>> <guimenuitem></guimenuitem>
>> </menuchoice>
>>
>> <guibutton></guibutton>
>> <guiicon></guiicon>
>> <guilabel></guilabel>
>>
>> <mousebutton></mousebutton>
>>
>> <keycombo>
>> <keycap></keycap>
>> </keycombo>
>>
>> <abbrev></abbrev>
>> <acronym></acronym>
>
> <abbrev> and <acronym> could both possibly be dropped
>
and in there place firstterm should be added.
>> <emphasis></emphasis>
>>
>> <quote></quote>
>>
>> <link></link>
>>
>> <subscript></subscript>
>> <superscript></superscript>
>>
>>
>> <action>
>>
>> <classname>
>> <constant>
>>
>> <errorcode></errorcode>
>> <errorname></errorname>
>> <errortype></errortype>
>>
>> <function></function>
>> <interface></interface>
>> <parameter></parameter>
>> <property></property>
>> <replaceable></replaceable>
>> <returnvalue></returnvalue>
>> <structfield><structfield>
>> <structname></structname>
>> <symbol></symbol>
>> <token></token>
>> <type></type>
>> <varname></varname>
> <remark></remark>
>
> Also, support for <!--comments-->
>>
>>
>> Regards,
>> Satya
>>
>
The only one I would say is seglist should be in the list of advanced
features to implement :)
I wonder why I didn't get the fedora-docs-list email about this...
Chris
--
Chris Curran
Content Author II
Phone: +61735148302 (UTC+10)
193 North Quay, Brisbane, Australia.
Red Hat, Inc.
14 years, 11 months
[Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]]
by Ruediger Landmann
-------- Original Message --------
Subject: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]
Date: Thu, 21 May 2009 10:57:05 +1000
From: Lana Brindley <lbrindle(a)redhat.com>
Organization: Red Hat Asia-Pacific
To: Joshua Wulf <jwulf(a)redhat.com>
CC: content-services-staff(a)redhat.com
References: <4A14A4D0.40207(a)redhat.com>
Joshua Wulf wrote:
> Satya is doing a WYSIWYG docbook editor as a Google SOC project in
> Fedora. He wants feedback on what tags to provide support for. Please
> take a look at this list and give some feedback on tags that we use that
> are not covered in it.
>
> - Josh
>
> -------- Original Message --------
> Subject: Re: Proposal for Implementing a Docbook Editor
> Date: Wed, 20 May 2009 21:47:25 +0530
> From: satya komaragiri <satya.komaragiri(a)gmail.com>
> Reply-To: For participants of the Documentation Project
> <fedora-docs-list(a)redhat.com>
> To: For participants of the Documentation Project
> <fedora-docs-list(a)redhat.com>
>
>
>
> Hello,
>
> I have narrowed down to the following set of tags as the minimum that
> Docbook editor will need to support for the initial stages of the
> project. It would be great if the list could review them once and
> suggest any additions/deletions.
>
>
> tags:
>
> Top Level:
> <article id="ID">
> </article>
>
>
>
> Section:
> <section id="ID">
> <title></title>
> </section>
>
>
>
> Block Tags:
> <para></para>
> <screen></screen>
<programlisting></programlisting>
>
> <itemizedlist>
<title></title>
> <listitem>
> <para></para>
> </listitem>
> </itemizedlist>
>
> <orderedlist>
<title></title>
> <listitem>
> <para></para>
> </listitem>
> <orderedlist>
>
> <procedure>
> <step>
> <para>
> </para>
> </step>
> </procedure>
>
> <important>
>
> <title></title>
> <para></para>
> </important>
>
> <tip>
> <title></title>
> <para></para>
> </tip>
>
> <note>
> <title></title>
> <para></para>
> </note>
>
> <warning>
> <title></title>
> <para></para>
> </warning>
>
> <caution>
> <title></title>
> <para></para>
>
> </caution>
>
>
>
>
> Inline:
>
> <firstterm></firstterm>
> <application></application>
>
>
> <command>
> <option></option>
>
> </command>
>
> <package></package>
> <filename></filename>
> <systemitem></systemitem>
> <computeroutput></computeroutput>
Is this tag the same as <programlisting>? I don't know it.
> <userinput></userinput>
>
> <prompt></prompt>
>
>
> <menuchoice>
> <guimenu></guimenu>
> <guisubmenu></guisubmenu>
> <guimenuitem></guimenuitem>
> </menuchoice>
>
> <guibutton></guibutton>
> <guiicon></guiicon>
> <guilabel></guilabel>
>
> <mousebutton></mousebutton>
>
> <keycombo>
> <keycap></keycap>
> </keycombo>
>
> <abbrev></abbrev>
> <acronym></acronym>
<abbrev> and <acronym> could both possibly be dropped
> <emphasis></emphasis>
>
> <quote></quote>
>
> <link></link>
>
> <subscript></subscript>
> <superscript></superscript>
>
>
> <action>
>
> <classname>
> <constant>
>
> <errorcode></errorcode>
> <errorname></errorname>
> <errortype></errortype>
>
> <function></function>
> <interface></interface>
> <parameter></parameter>
> <property></property>
> <replaceable></replaceable>
> <returnvalue></returnvalue>
> <structfield><structfield>
> <structname></structname>
> <symbol></symbol>
> <token></token>
> <type></type>
> <varname></varname>
<remark></remark>
Also, support for <!--comments-->
>
>
> Regards,
> Satya
>
14 years, 11 months
Zeroday change to release notes for Release Candidate?
by Karsten Wade
We are considering doing a change today that would replace a paragraph
of content with a new paragraph. We need your (L10n)
opinion/viewpoint.
You can view the change as it was made on the wiki:
https://fedoraproject.org/w/index.php?title=Documentation_Multimedia_Beat...
Our plan is to replace that paragraph of text before the
'fedora-release-notes' package goes in to the Release Candidate spin.
This new content is about a better way to adjust legacy ALSA mixer
levels using a GUI interface.
We're not sure if there will be time to translate the new paragraph.
The old content is 100% correct. However, the QA/Testing Team would
like to see people testing/using the alternative sound mixer GUI
instead of the text UI sound mixer. For the Docs Team, the GUI
alternative is a better solution for more users and we want to tell
people about it.
Note that the changes will be made on docs.fedoraproject.org anyway,
and the release notes point to that URL for latest information. That
means a break of string and translation % is *not* crucial.
Thanks for your consideration,
- Karsten, guy who happens to be in #fedora-docs :)
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
14 years, 11 months
Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]
by Ruediger Landmann
> It would be great if the list could review them once and
> suggest any additions/deletions.
>
Hi Satya!
A few more that I use very regularly or see very regularly in Red Hat
and Fedora docs:
<book id="ID">
<title></title>
</book>
<part id="ID">
<title></title>
</part>
<introduction id="ID">
<title></title>
</introduction>
<chapter id="ID">
<title></title>
</chapter>
<appendix id="ID">
<title></title>
</appendix>
<citetitle></citetitle>
<literal></literal>
<ulink></ulink>
<variablelist>
<title></title>
<varlistentry>
<term></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
<xref></xref>
The article, itemizedlist and orderedlist tags should also support
<title> tags under them.
At this early stage, I assume that you want to avoid <example>s,
<figure>s and <table>s, but of course, we make a lot of use of these as
well...
Good luck with the project!
Cheers
Ruediger
14 years, 11 months
Docs Meeting Summary 2009-05-20
by David Nalley
This was largely a status meeting due to the closeness to release.
*Release announcement
*Release Notes
** Status esp with regard to l10n.
** 0-day updates
*** Libguestfs
*Schedule review - noting the schedule slip and the affected items
*Brief discussion of the Docs FAD
* Discussion of new contributor on-boading.
14 years, 11 months
Docs Meeting Log 2009-05-20
by David Nalley
Summary to follow shortly
Prettified wiki: https://fedoraproject.org/wiki/Meeting:Docs_IRC_log_20090520
Raw text below:
20:00 < Sparks> <meeting id="Docs">
20:00 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting
- Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
20:00 < Sparks> Roll call...
20:00 * Sparks is here
20:00 * ke4qqq is here
20:01 * sk0rd is here
20:01 * jjmcd is somewhere
20:02 * rudi is here
20:02 * laubersm is here
20:03 * Sparks gives a few more minutes for everyone to show up
20:03 * laubersm goes to get a drink - brb
20:03 < ianweller> if you need me, ping me, i'll be distracted mostly
20:03 < Sparks> ianweller: We need you
20:03 < ianweller> *thud*
20:05 < Sparks> Okay... let's get started.
20:05 < laubersm> mmmm
20:05 < Sparks> ke4qqq: Can you handle the log for tonight?
20:05 < ke4qqq> sure
20:05 < Sparks> ke4qqq: Thanks
20:05 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting
- Release Announcement
20:06 < Sparks> Okay... This has been moved up to high priority.
20:06 * ianweller removes that pot from the back burner
20:06 < Sparks> https://fedoraproject.org/wiki/Release_Announcement_for_F11
20:06 < Sparks> I had writer's block over the weekend and I won't be
around this weekend.
20:07 < Sparks> Since the release has been pushed back by a week we
have a little breathing room...
20:07 < SgtDitt> here
20:07 < Sparks> however we need to get this done ASAP so the
translators can get on it.
20:07 < Sparks> Who can write up a draft that we can look at?
20:08 < Sparks> Don't everyone volunteer at once, now... I'd hate to
crash the IRC network
20:09 < Sparks> ianweller: Do you have some time to write an opening
paragraph for the announcement?
20:09 < rudi> Sparks - I can do it, but it will be a few days before I
get to it.
20:09 < ianweller> Sparks: "We're awesome."
20:09 < rudi> (over the weekend0
20:09 < ianweller> Sparks: but in all seriousness i could come up
withs omething and get it to the list tonight
20:09 < Sparks> rudi: Okay. The schedule says that we were supposed
to begin this today and have it done by Friday... that was before the
push
20:10 < Sparks> ianweller: put it on the wiki... that way it's already there
20:10 < ianweller> well, yeah. ping the list that i actually did it too
20:10 < Sparks> yeah
20:10 < ianweller> that was what i meant to say :P
20:10 < Sparks> :)
20:10 < Sparks> Cool
20:10 < Sparks> ianweller: rudi: thanks!
20:11 < sk0rd> I'll shoot for a draft on the page as well
20:11 < ianweller> so the rel announcement is gonna be i18n'd?
20:11 < Sparks> How is this presented to the "customers"?
20:11 < Sparks> ianweller: Supposedly
20:11 < Sparks> ianweller: which is confusing me because I'm not sure
how it's being propagated
20:12 < ianweller> Sparks: mailing list usually
20:12 < Sparks> Maybe we can get that answer when stickster_afk shows up.
20:12 < Sparks> ianweller: Yeah, that's what I was thinking. Maybe I
misread the schedule
20:13 < laubersm> I think we are reposonsible for an English
annoucement for emails. But a lot of locations like to translate and
tweak it for their regions
20:13 < laubersm> I do not think it has ever been a tranfix thing
20:13 < Sparks> I'm good with that.
20:13 < laubersm> but that may of changed...
20:13 < jjmcd> The instructions say to keep that in mind
20:13 < ianweller> yeah so write it as if it were to be translated
20:13 < Sparks> So should they be put somewhere and "translated" into XML?
20:14 < jjmcd> Some translated literally, other parts may be radically
revised in translation
20:14 < jjmcd> I don't think so. Sounds like most will be rewritten
for the target geography
20:14 < laubersm> Sparks, I do think we have in the past but we'll
have to check with our elders (quaid, stickster_afk )
20:14 < laubersm> opp
20:14 < laubersm> do NOT think we have
20:15 < Sparks> laubersm: Yeah, where are those old people?
20:16 < Sparks> Okay... looks like we have this moving
20:16 < Sparks> I appreciate it.
20:16 < laubersm> "Turn up the volume (if you can), select a mode for
video - the Lion roars as Fedora 11 arrives"
20:16 < laubersm> too snarky ?
20:16 < Sparks> Nope
20:16 < Sparks> :)
20:17 < Sparks> Okay, we'll talk about this more after the meeting...
20:17 < Sparks> any questions?
20:17 * jjmcd will be sure to be around to make jabs at ianweller
20:17 < Sparks> jjmcd: Much appreciated
20:17 < Sparks> Okay... moving on...
20:17 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting
- Status on Release Notes <-- ryanlerch & jjmcd
20:17 < Sparks> How are them there Release Notes coming?
20:18 * jjmcd hasn't caught up on all the cool stuff laubersm, rudi,
zoglesby, etc. did while he was playing at Dayton
20:18 < laubersm> jjmcd, yeah about that....
20:18 < Sparks> jjmcd: Oh there were many things that happened while
you were away
20:19 < laubersm> I think rudi was on top of adding the last minutes
items and getting a new pot
20:19 < rudi> Yep all done.
20:19 < laubersm> I assume everything else just goes on the wiki
20:19 < jjmcd> We do a 0-day RPM
20:20 < rudi> There were a couple of bugs filed overnight about
Section IDs and re-adding the Common Bugs section from F10
20:20 < jjmcd> Yeah, I saw that
20:20 < rudi> I've confirmed that we could do this with practically no
impact to L10N
20:20 < laubersm> jjmcd, from what is being translated now? or are we
pushing one more pot too?
20:20 < Sparks> I've noted a few messages on the list talking about updates
20:20 < jjmcd> If nobody else is making a bunch of changes I can go
ahead and add the id's
20:21 < jjmcd> We are scheduled to push a pot immediately after release
20:21 < jjmcd> seemd weird but
20:21 < laubersm> jjmcd, I think that one is to then update docs.fp.o
20:21 < rudi> jjmcd I've got them done and ready to push...
20:21 < jjmcd> yes, i think that is correct
20:21 < laubersm> no more rpms after GA - though we could push one
through updates if we wanted
20:21 < jjmcd> cool
20:22 * quaid is able to be here now for a short bit
20:22 < rudi> There was also a request to add a note about libguestfs,
but I think this is way too late now, yes?
20:22 * jjmcd is doing some reports for MSP, not going well, Eric's
writer's block is catching
20:23 < laubersm> if anything else comes in before we build the ga rpm
- then it sounds like we can add a link to the wiki info without
bothering the translators
20:23 < laubersm> is that true?
20:23 < quaid> translators? for release announcement?
20:23 * quaid is confused now
20:23 < jjmcd> We did get a week push back
20:23 < laubersm> then it is "in" the rpm for those looking there to
know there is more info "somewhere"
20:24 < jjmcd> quaid: previous topic
20:24 < sk0rd> can someone speak more to the push back? docs is my
only insight as to what's going on
20:24 < quaid> jjmcd: we need to revisit when we get a chance, there
is a misconception underway
20:24 < ke4qqq> sk0rd: we'll talk in #f-d
20:24 < quaid> sk0rd: release engineering in yesterday's meetings
declared a week slip in the schedule
20:24 < Sparks> quaid: I must have misread the schedule. There isn't
anything about translating the annoucement on there now
20:25 < quaid> Sparks: can I speak on that now? or wait until a topic
change soonest?
20:25 < Sparks> quaid: Go for it
20:25 < quaid> ok, I've tried to make this clear on some wiki page
that I can't find right now :)
20:25 < quaid> there are two deliverables --
20:25 < jjmcd> /Releases/Announcements
20:26 < quaid> 1. A set of clear top-five talking points for _others_
to use when constructing their own, native language, locale-specific
(humor, no humor, etc.) release announcement
20:26 < quaid> 2. A whimsical, English-only release announcement that
i) uses those same talking points (functionally similar to locally
written announcements), but ii) is not for
l10n itself because of idiomatic/culture specific content
20:27 < quaid> it is the latter that is the main need from Docs
20:27 < quaid> the former is more handled by Marketing, but $someone
needs to tell f-amb-l and f-trans-l
20:27 < quaid> that the points are ready for them to use for their own
locale-specific write-up.
20:27 < quaid> <eof>
20:28 < jjmcd> OK, that was mostly my understanding except it wasn't
clear that Marketing was handling the former, Docs the latter, nor was
the top-five clear
20:29 < jjmcd> Releases/Announcements makes it sound like some undefined body
20:29 < quaid> well, to be honest, I'm not clear if Marketing has that
former task on their schedule
20:29 < laubersm> that is even easier than what I said - I thought 1
came more from 2 ... but that it was still just a write up (no xml or
tx from docs).
20:29 < quaid> I sort-of dropped that ball this release, since I've
been the main driver on that for the last several
20:29 < quaid> laubersm: it's also honestly fun -- you should do it!
20:29 < laubersm> "Turn up the volume (if you can), select a mode for
video - the Lion roars as Fedora 11 arrives"
20:29 < laubersm> that was my attempt :)
20:30 < quaid> heh
20:30 < laubersm> seems a bit snarky even for the english version
20:30 < laubersm> :)
20:30 < jjmcd> laubersm, seems to me Fedora's image is a little
"corporate", snarky might be good
20:30 < quaid> https://fedoraproject.org/wiki/Release_announcement_template
20:31 < quaid> https://fedoraproject.org/wiki/Release_announcements
20:31 < quaid> there we go!
20:31 < sk0rd> the l10n reference is a bit obscure. With the art team
working on grecian references, why not duplicate the theme
20:31 < quaid> that has a link to all previous whimsical announcements
20:31 * laubersm notes it is only in a Marketing Category - no wonder
we we didn't have it here in docs...
20:31 < quaid> there is no pattern on theme duplication or ref. to
release name, although that is a popular theme.
20:32 * laubersm logs into wiki...
20:32 < quaid> um, [[Release_announcements]] is in [[Category:Docs Project]]
20:33 < laubersm> the template is not
20:33 < laubersm> or WAS not
20:33 < laubersm> :)
20:33 * laubersm also moved the [[Category: to the bottom where it belongs
20:33 < Sparks> laubersm: ianweller will thank you
20:34 < laubersm> :)
20:34 < jjmcd> hmmmm, reading the F10 announcement, I hope there was
an en-GB version
20:35 < Sparks> ?
20:35 < jjmcd> might work for nl, or even en-AU, but not the straight
laced Brits
20:35 * ianweller thanks laubersm
20:35 < Sparks> laubersm: See, I told you
20:37 < quaid> one other point, not sure if it is on that page ...
20:37 < quaid> but the whimsical announcement must be approved by the
sitting FPL, in this case, stickster_afk
20:37 < quaid> just give him ~24 hours heads up
20:37 < jjmcd> most of us would value his counsel anyway
20:38 < Sparks> most of us wonder why he bails on us these days
20:38 < jjmcd> Probably he has more to do than just chill on IRC, just guessing
20:38 < jjmcd> Isn't he about to head to Romania?
20:39 < Sparks> Probably
20:39 < Sparks> I don't know... haven't heard anything about Romania
20:39 < sk0rd> ok, next topic?
20:39 < sk0rd> ;)
20:39 < Sparks> Okay.. anything else on the announcement?
20:39 * quaid is done and has to vaporize now
20:39 < jjmcd> I thought I heard he was speaking in Bucharest this weekend
20:39 < Sparks> wow
20:40 < Sparks> Okay... anything else on the RNs?
20:40 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting
- Review http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html
schedule
20:40 < jjmcd> </rn>
20:40 < rudi> Just confirmation that we agree that libguestfs is too late?
20:41 < Sparks> too late for zero-day?
20:41 < rudi> Yeah
20:41 < jjmcd> The schedule saysfinal snapshot today and release
pushed back a week, so I would say no, not too late
20:41 < Sparks> yeah, I think we should take advantage of the push
20:41 < rudi> OK - but I guess we should get confirmation that L10N is
happy with that...
20:42 < jjmcd> I agree
20:42 < rudi> OK - I'll ask :)
20:42 < jjmcd> today = today zulu time
20:43 < rudi> Doesn't that mean that the translations would need to be
completed by today?
20:44 < Sparks> how many changes need to be fixed?
20:44 < jjmcd> It says build rpm 5/25
20:44 < jjmcd> Seems like there has been a flood of bugs today
20:45 < rudi> Sparks - the section IDs (fixed), the Common Bugs
section (fixed, but one problem), and the request to add libguestfs to
the RN
20:45 < Sparks> so... five lines?
20:46 < rudi> Checking...
20:46 < rudi> Yep
20:47 < Sparks> cool
20:47 < Sparks> that shouldn't be too bad to "repair'
20:48 < rudi> There are also requests for documentation of two bugs,
one in anaconda and one in libfprint, but I think they can go on the
Common bugs page on the wiki, yes?
20:48 < Sparks> I would think so
20:50 < Sparks> Anything else?
20:50 < rudi> Not that I'm aware of
20:50 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting - Guides
20:50 < Sparks> Okay, due to the hour I'm not going to go through all the guides
20:51 < Sparks> does anyone need anything for their guides or is
anyone having any problems?
20:51 * ke4qqq needs more time
20:51 < Sparks> for the IG?
20:51 < ke4qqq> but thankfully rudi is doing a great job of keep things moving
20:51 < Sparks> You have a week more!
20:52 < ke4qqq> lol wow - granted my wish :)
20:52 < rudi> ke4qqq - what needs doing?
20:52 < ke4qqq> rudi: I was talking about I need more time - as far as
I know the IG is in good shape, we probably need to get the final
release ready (get rid of draft tag) but we
can talk in a bit and not hold up the meeting
20:53 < rudi> OK - yep :)
20:54 -!- Sparks changed the topic of #fedora-meeting to: Docs Meeting
- Open Floor
20:54 < Sparks> Okay, anyone have anything they want to discuss?
20:54 < rudi> Translators have noticed a couple of glitches in the
big, merged PO files for both the IG and UG, but I've suggested we
wait until Transifex 0.6 is available rather than
do anything about these now
20:54 < ke4qqq> Me!
20:54 < jjmcd> Do I gather we have agreement on everything in Publican for 12?:
20:54 < sk0rd> I did, heck if I can remember.
20:54 < ke4qqq> https://fedoraproject.org/wiki/FAD_SELF <--- Docs FAD
20:54 < laubersm> jjmcd, I agree - but can we have less than everything ?
20:55 < Sparks> jjmcd: Not yet
20:55 < sk0rd> ah, new contributors, hand raised when ready.
20:55 < Sparks> jjmcd: I'd like to have a free minute or two to really
think about it. I didn't see anything objectionable, though
20:55 < Sparks> ke4qqq: Okay... go with your shameless plug
20:56 < ke4qqq> honestly I think we are in a poor place to make that
decision jjmcd - immediately before release - extremely busy with all
of that - might make for less than reasoned
look.
20:56 < ke4qqq> We have a docs fad at the above link
20:56 < ke4qqq> you should all attend
20:56 < ke4qqq> (And SELF the day before)
20:56 < ke4qqq> ianweller is going to teach packaging
20:56 < Sparks> ke4qqq: That's all you got?
20:56 < jjmcd> ke4qqq, I can buy that. I was just hoping to check one
more thing off the list :-)
20:56 < ke4qqq> and hopefully we can hash this out.
20:56 * Sparks is still contemplating on how to get down there
20:56 < ke4qqq> that is it from me
20:57 < Sparks> ke4qqq: how many Fedora hams are going to be there?
20:57 < Sparks> ke4qqq: Maybe a designated simplex freq?
20:57 * laubersm prods Sparks to get to the "new contributor" before
time runs out
20:57 < ke4qqq> 2 that I know of.
20:57 < Sparks> ke4qqq: ok
20:57 < ke4qqq> I'll add that
20:57 < Sparks> sk0rd: Go ahead!
20:58 < sk0rd> I've been really happy with the time that people have
spent with me, but I've noticed quite a few introductions and whatnot
through the mailing list
20:58 * jjmcd has been emailing applicants to get intros
20:58 < sk0rd> as far as getting people involved, does anyone have any
thoughts on improving the documentation on... joining documentation
and getting started?
20:59 < Sparks> sk0rd: We need to get on that as well. This is just a
really "bad" time to join as we are rushing to get everything finished
for the release
20:59 < laubersm> I think a lot of us have ideas but no one has
settled down enough to get it done.
20:59 < laubersm> sk0rd, I came in about this time one release ago to
the same issues
20:59 < Sparks> but we should make it a priority to be better with
being able to get new members on track early
20:59 < sk0rd> Sparks, it is so for senior contributors yes
21:00 < jjmcd> Sparks, gotta strike while the iron is hot, tho
21:00 < Sparks> Oh, I agree!
21:00 < sk0rd> perhaps I'll try and hit on it
21:00 < Sparks> There will be changes for F12.
21:00 < sk0rd> </comment>
21:00 < laubersm> sk0rd, no - any one - if there is something that
wasn't clear to you before and somehow is now - please jump in and
expand in the join docs!
21:01 < laubersm> I and others have been prodding quaid and
stickster_afk to go through and "fix up" the pages too
21:01 < laubersm> with their years of wisdom
21:01 < ianweller> ke4qqq: oh i am teaching packaging? interesting.
21:01 < Sparks> ianweller: You are now
21:01 < ke4qqq> by fiat
21:01 < jjmcd> you are our leading expert
21:01 < ke4qqq> :)
21:01 < laubersm> ianweller, the CMS is to be all packaged before you can sleep
21:02 < laubersm> the more people you teach, the more likely you will
get to sleep
21:02 * laubersm says knowing she will not be able to be there
21:02 < ianweller> looks like i'm getting no sleep
21:02 < ke4qqq> ianweller: I tried to get jds2001, but looks like he
is unavailable
21:02 < ianweller> ke4qqq: oic.
21:02 < ke4qqq> and then Max said sending you was 'the right thing to do'
21:02 < ke4qqq> :)
21:03 < ianweller> i saw that
21:04 < jjmcd> THat way you'll be all practiced up to teach at FUDcon
21:05 < Sparks> Okay, anything else?
21:07 < Sparks> I'd like to mention that I'll be helping my wife move
for the summer (summer internship) beginning tomorrow and I won't be
back until Monday. I won't have Internet
access during this time so I'm turning over the conn
to jjmcd for the weekend.
21:07 < laubersm> excellent!
21:07 * jjmcd will be around
21:08 < Sparks> Okay, anything else?
21:08 < jjmcd> Sparks, Does that mean you will be batching it for the summer?
21:08 < Sparks> jjmcd: pretty much
21:08 < Sparks> pizza and soda all summer long
21:08 < jjmcd> Ooooh, bad. Gotta fend for yourself
21:09 * jjmcd suspects Sparks needs time in .de to learn things that
go better with pizza
21:09 < Sparks> I have some projects to work on over the summer...
maybe that will keep me out of trouble.
21:09 * Sparks is too poor to go to .de...
21:09 < Sparks> okay, anything else?
21:09 < Sparks> 5
21:09 < Sparks> 4
21:10 < Sparks> 3
21:10 < Sparks> 2
21:10 < Sparks> 1
21:10 < Sparks> </meeting>
14 years, 11 months
Meeting today
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just wanted to remind everyone that we will have a Docs Project
meeting today at 0001 UTC in #fedora-meeting.
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
iEYEARECAAYFAkoUFf8ACgkQfQTSQL0MFMG19gCfZXwxBzg3nL52NznuInhEz3of
GFMAnRImSnBB3XKl3heNq15hpsPbquHj
=elVC
-----END PGP SIGNATURE-----
14 years, 11 months
FDSCo Meeting 2009-04-30 IRC log
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[29 Apr 20:00] +
[29 Apr 20:00] --- Sparks (n=sparks@fedora/Sparks) changed topic:
Welcome to the Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting
[29 Apr 20:00] +Roll Call!
[29 Apr 20:00] +
[29 Apr 20:00] * Sparks is here
[29 Apr 20:00] +
[29 Apr 20:00] * jjmcd est ici
[29 Apr 20:00] -
[29 Apr 20:00] * rudi is here
[29 Apr 20:01] +
[29 Apr 20:01] * Sparks waits a few more minutes before getting
everything kicked off
[29 Apr 20:02] +
[29 Apr 20:02] * jjmcd sees ke4qqq, quaid, radsy but they must be sleeping
[29 Apr 20:02] +
[29 Apr 20:02] * radsy is here
[29 Apr 20:04] +Isn't ke4qqq first up?
[29 Apr 20:04] +jjmcd: Yes
[29 Apr 20:04] +fwiw i'm mostly in lurk mode, in the middle of a few things
[29 Apr 20:05] +Well, while we wait...
[29 Apr 20:06] +I sent out a couple of messages earlier today. I'm
trying to organize the guides and such so if you are the lead of a
guide please take a look at those messages and help me out, please.
[29 Apr 20:07] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - Go over task table
[29 Apr 20:08] +The task table is located under the meeting agenda.
[29 Apr 20:08] +It needs to be updated.
[29 Apr 20:08] +
[29 Apr 20:08] * ke4qqq is late sorry
[29 Apr 20:09] +So please take a peek at it and see if you can either
1) update it or 2) join up to help it along.
[29 Apr 20:09] +Sparks, since my F12 questions overlap the Publican
topic, I will make a page outlining the steps and decisions we need to
make (after pot is out of course)
[29 Apr 20:09] +jjmcd: Cool
[29 Apr 20:09] +And that's all I have to say about the task table this week.
[29 Apr 20:10] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - Shameless plug for SouthEast LinuxFest +ke4qqq: Take it
away.
[29 Apr 20:10] +so firest the southeast linuxfest is June 13
[29 Apr 20:10] +s/firest/first/
[29 Apr 20:10] +second - is there any interest in having a Docs FAD
on the 12th or 14th?
[29 Apr 20:11] +I wouldn't mind that
[29 Apr 20:11] +I know a lot of the docs contributors are in the southeast
[29 Apr 20:11] +stickster is already confirmed to be there.
[29 Apr 20:11] +
[29 Apr 20:11] * jjmcd has to be here on the 13th
[29 Apr 20:11] +So I'd like to propose that we spend some time
hacking on our infrastructure - perhaps getting some packagers minted
as well.
[29 Apr 20:12] +ke4qqq: I'm PLANNING on being there...
[29 Apr 20:12] +That would be a good move. we need packagers
[29 Apr 20:12] +and I'd like a yes/no on the entire thing maybe
within a week or so.
[29 Apr 20:12] +jjmcd: you could participate remotely
[29 Apr 20:12] +ohhh yeah sparks is going to be there
[29 Apr 20:12] +Prolly Friday.
[29 Apr 20:12] +ke4qqq: Well... I stress the planning part...
[29 Apr 20:12] +
[29 Apr 20:12] * ke4qqq concludes his shameless plug - I'll send an
email to the list.
[29 Apr 20:12] ++1
[29 Apr 20:12] +Boston remote didn't work so hot
[29 Apr 20:13] +jjmcd: Yeah, but that was yankee land... we're down south.
[29 Apr 20:13] +Coulda done better on cw
[29 Apr 20:13] +Boston is a lot busier too
[29 Apr 20:13] +as well as the phones worked
[29 Apr 20:13] +yeah, the confusion was a lot of it
[29 Apr 20:15] +yep
[29 Apr 20:15] +ke4qqq: Anything else?
[29 Apr 20:15] +nothing on this subject
[29 Apr 20:15] +Okay...
[29 Apr 20:16] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - Review
[http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html
schedule]
[29 Apr 20:16] +I am here sorry for being late
[29 Apr 20:16] +Looks like a few things happened here recently.
[29 Apr 20:17] +Well, 34 in progress, 36 is Friday's task
[29 Apr 20:17] +jjmcd: You going to be able to build the RN RPM by Friday week?
[29 Apr 20:18] +I see no reason why not
[29 Apr 20:18] +We have work today and tomorrow
[29 Apr 20:18] +then we wait a while for the translators
[29 Apr 20:18] +Cool. I see that the translations are going well.
[29 Apr 20:18] +then we repeat last weeks steps
[29 Apr 20:18] +Would be good tho if I had a shadow
[29 Apr 20:19] +Right now I think I'm the only one who knows what is
actually going on there
[29 Apr 20:19] +jjmcd: Pick your victim
[29 Apr 20:20] +Dunno, Zach, how busy are you next week aroung task 37 time
[29 Apr 20:20] +ohhh bad, gotta be friday
[29 Apr 20:20] +I'm in Lansing Saturday, Alma Sunday
[29 Apr 20:21] +zoglesby, are you busy Friday?
[29 Apr 20:21] +no
[29 Apr 20:21] +would you like to learn how f-r-n.rpm goes together?
[29 Apr 20:21] +sure
[29 Apr 20:21] +good deal, lets do that then
[29 Apr 20:22] +that's Friday the 8th
[29 Apr 20:22] +ok, let me know what time is good for you
[29 Apr 20:22] +K, I'm an early riser so prolly noon-ish your time,
maybe a little earlier
[29 Apr 20:23] +thats great about when I get up
[29 Apr 20:23] +;-))
[29 Apr 20:23] +(I am on nights now)
[29 Apr 20:25] +
[29 Apr 20:25] * quaid arrives tardy
[29 Apr 20:25] +So are all the guide pots done?
[29 Apr 20:26] +?
[29 Apr 20:26] +task 32
[29 Apr 20:26] +IG pot is done
[29 Apr 20:26] +SG pot is done
[29 Apr 20:27] +believe UG pot is done
[29 Apr 20:27] +cool
[29 Apr 20:27] +obviously the RN pot is done
[29 Apr 20:27] +what others are out there?
[29 Apr 20:27] -UG pot is done
[29 Apr 20:27] +SELinux
[29 Apr 20:27] +I gather that "0 day" means final RN tweaks en-US
only until docs.fp.org updated in June?
[29 Apr 20:28] +I guess
[29 Apr 20:28] -IG pot still reflects a draft version (Task 24), with
a couple of small changes still to go for PR (will be done in the next
couple of hours...)
[29 Apr 20:29] +rudi: I have a conflict on the guide table for the
UG... https://fedoraproject.org/wiki/Docs_Project_meetings#Guides
[29 Apr 20:29] +Is the UG completely in XML now?
[29 Apr 20:29] +the selinux confined services guide won't be ready
for a while still, and it looks like it's about to have another
section added, so...
[29 Apr 20:30] -Sparks: UG completely in XML and building fine
[29 Apr 20:30] +rudi: Okay.
[29 Apr 20:30] +radsy: Understood. Anything I can help with?
[29 Apr 20:31] +should be fine, Sparks - it's taking shape, just
doubtful for f11
[29 Apr 20:31] +Sparks: rudi is a machine and moved UG to XML in what
seemed like a week.
[29 Apr 20:31] +radsy: Okay. Is it going to be release specific or
more like the SG?
[29 Apr 20:31] +radsy: chance it could branch off minus the confined
services content and be something available??
[29 Apr 20:31] +good but not yet perfect?
[29 Apr 20:32] *** You connected
[29 Apr 20:32] +not release specific
[29 Apr 20:32] +radsy: Okay. Whenever it's done let's get it up on docs.fp.o.
[29 Apr 20:32] +ke4qqq, the selinux user guide already exists, this
is more aimed at a smaller audience
[29 Apr 20:33] +radsy: Hmmm.... So there are two "SELinux" guides?
[29 Apr 20:33] +radsy: the last selinux UG I saw was for around fc5 -
have I missed an intervening one?
[29 Apr 20:34] +http://docs.fedoraproject.org/selinux-user-guide/ for
f10, mdious wrote it
[29 Apr 20:34] +wow - how did I miss that.
[29 Apr 20:34] +yep Sparks,
http://sradvan.fedorapeople.org/SELinux_Managing_Confined_Services/en-US/
is what I'm working on
[29 Apr 20:34] * stickster here late too as promised
[29 Apr 20:34] +radsy: Okay, the one mdious was working on is the one
I knew about.
[29 Apr 20:35] +radsy: is that one translated and ready to go or???
[29 Apr 20:35] +not sure what the story is with the user-guide, i
haven't touched it since mdious left
[29 Apr 20:36] +radsy: is it in fedorahosted?
[29 Apr 20:36] +still working on the confined-services guide
[29 Apr 20:36] +https://fedorahosted.org/managing-confined-services/
[29 Apr 20:36] +Okay.
[29 Apr 20:37] +Anything else for the schedule?
[29 Apr 20:37] +?
[29 Apr 20:37] +well i've dragged this off-topic
[29 Apr 20:37] +radsy: Not really.
[29 Apr 20:37] +Any other questions about the release schedule?
[29 Apr 20:37] +have we unknowingly dropped the SELinux guide?
[29 Apr 20:38] +and if we have, what are we doing now? does ECS have
an internal owner for the document or do we need to assume that
ownership or??
[29 Apr 20:38] +ke4qqq: Well... mdious didn't give me much view of the project
[29 Apr 20:38] +ke4qqq: We need to figure out where the source is and
see where the document is.
[29 Apr 20:39] +it's on fedorahosted
[29 Apr 20:39] +https://fedorahosted.org/selinuxguide
[29 Apr 20:39] +okay
[29 Apr 20:39] +and shows commits as recently as feb
[29 Apr 20:40] +Let's look at that after the meeting and see what we can do.
[29 Apr 20:40] +k
[29 Apr 20:40] +Anything else?
[29 Apr 20:40] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - Status on Release Notes +jjmcd: Where are you?
[29 Apr 20:41] +Obviously, RN's went into 11Pr.
[29 Apr 20:41] +Went through mails, about to add those to wiki, then
scrape wiki for xml changes
[29 Apr 20:41] +then build the pot for Fri
[29 Apr 20:41] +Not a lot of changes so I don't anticipate much prob
[29 Apr 20:42] +Trying to get philip_ equipped to help as a way to
break into the process
[29 Apr 20:42] +Cool
[29 Apr 20:42] +laubersm also indicated she might help some but I
don't think we have that much to do
[29 Apr 20:43] +Okay... anything else?
[29 Apr 20:43] +i don't understand RN or 11Pr or why 'scrape wiki'
[29 Apr 20:43] +RN = release notes, 11Pr -= Fedora 11 release notes
[29 Apr 20:43] +aaaah
[29 Apr 20:43] +11pr = fedora 11 preview
[29 Apr 20:43] +philip_: you will get the hang of it after a while
[29 Apr 20:44] +just went out this week with 99% of release notes there
[29 Apr 20:44] Did announcements go out to developers and greater
community to tell them about wiki freezing?
[29 Apr 20:44] +Does anyone know why yelp seems so much faster on F11
[29 Apr 20:44] It's just mo' betta
[29 Apr 20:44] +stickster: I don't know
[29 Apr 20:44] +jjmcd: because it goes up to 11
[29 Apr 20:45] +which is one more than 10
[29 Apr 20:45] +:)
[29 Apr 20:45] +It's faster on a VM on 11 than native on 10
[29 Apr 20:45] Sparks: It would be a good idea to make a note that
someone needs to be responsible for those reminders.
[29 Apr 20:45] +stickster: yes
[29 Apr 20:45] +we seem to be really lacking the reminder department overall
[29 Apr 20:45] +very little wiki activity lately to freeze
[29 Apr 20:46] +more concerned about L10n
[29 Apr 20:46] jjmcd: That could be due to the lack of reminders...
[29 Apr 20:46] +good point
[29 Apr 20:46] +zoglesby: Yes... I take responsibility for that as
I've been lacking here lately.
[29 Apr 20:46] How much time is left before freezing the wiki and port to XML?
[29 Apr 20:46] +XML port has to happen tomorrow
[29 Apr 20:47] Sparks: OK, let's stand back for a second.
[29 Apr 20:47] Oops, not just Sparks, sorry
[29 Apr 20:47] We know that's not enough time to give people a
heads-up about freezes.
[29 Apr 20:47] Yet it's about what we did before the freeze for Preview, right?
[29 Apr 20:47] So let's figure out what would help us *not* do that
in the future.
[29 Apr 20:48] +a calendar
[29 Apr 20:48] +with email reminders
[29 Apr 20:48] Is someone reading the release schedule tasks?
[29 Apr 20:48] +Well, more than that
[29 Apr 20:48] the ones that Poelstra creates, I mean
[29 Apr 20:48] +yes - they are our calendar effectively
[29 Apr 20:48] +One of us needs reminders on our calendar to post
warning about events on poelstra's calendar
[29 Apr 20:49] jjmcd: You're about 80% of the way there
[29 Apr 20:49] + and we really need to prolly add freeze
notifications to poelstras schedule
[29 Apr 20:49] What we really need is to have this *task* captured in
that schedule
[29 Apr 20:49] ke4qqq: DISCO!
[29 Apr 20:49] +good point
[29 Apr 20:49] +jjmcd: Google calendar?
[29 Apr 20:49] +Sparks: we can't use Google Calendar
[29 Apr 20:49] +I have a NASA calendar marked up on my wall
[29 Apr 20:49] +ke4qqq: no?
[29 Apr 20:50] So, I would humbly submit to you that the docs lead
should get with poelcat and figure out how to add these
public-notification tasks to that schedule
[29 Apr 20:50] +Sparks: we only use F/LOSS to create Fedora
[29 Apr 20:50] +ke4qqq: So is jjmcd 's NASA calendar open?
[29 Apr 20:50] +it's not software
[29 Apr 20:50] +lol
[29 Apr 20:50] +ke4qqq: It's a process
[29 Apr 20:50] +And it doesn't have the notifications on it
[29 Apr 20:50] +Ahhhh, *BUT*
[29 Apr 20:50] +Sparks: it's just caused flames before - just trying
to warn you - though I use Google Calendar personally
[29 Apr 20:51] +We don't have a solution in place that helps us with this.
[29 Apr 20:51] +We need to get the appropriate events onto the
appropriate person's PDA
[29 Apr 20:51] +what is this calendar for and what does it need to do?
[29 Apr 20:51] +ke4qqq: This isn't to put the word out to the
masses... it is being used to help organize already open data.
[29 Apr 20:51] Sparks: Waiting for the solution is not as big a
problem as making sure the right tasks are on the schedule to begin
with. Let's solve first things, first.
[29 Apr 20:51] +who wants a piece of me? ;-)
[29 Apr 20:51] +I will take up the reminders
[29 Apr 20:51] +I just need to figure out who and when
[29 Apr 20:51] +speak of the devil
[29 Apr 20:51] haha
[29 Apr 20:51] +the who is worse than the when
[29 Apr 20:51] poelcat: We were just discussing that there are tasks
missing on the Docs schedule -- not that they were omitted by anyone,
they've just not been captured correctly to start with
[29 Apr 20:52] poelcat: in particular, a task to notify the community
about wiki freezes well in advance
[29 Apr 20:52] or I should say, a task per freeze
[29 Apr 20:53] +where is this calendar?
[29 Apr 20:53] +send me email with: 1) name of task (should contain
verbs); 2) how many days it takes (or not); 3) what it depends on or
when it should start
[29 Apr 20:53] +philip_, poelstra.fedorapeople.org
[29 Apr 20:53] +i'll add it to the source file and then it will
magically be reported
[29 Apr 20:54]
+http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html
[29 Apr 20:54] +
[29 Apr 20:54] * jjmcd has it up an a different screen so couldn't cut and paste
[29 Apr 20:55] +Should someone (possibly docs) be responsible for
warning of all freezes? This isn't unique to Docs
[29 Apr 20:56] jjmcd: It's usually easier for each team to report
freezes since changes happen sometimes on a per-team basis, and
coordination would be tough
[29 Apr 20:56] But...
[29 Apr 20:56] There's no doubt that Zikula will help with this --
aiui there's a pretty rad calendar module
[29 Apr 20:56] +stickster: I thought we weren't going to use the
calendar in Zikula
[29 Apr 20:56] +every other group 'warns' re freezes
[29 Apr 20:56] +sometimes with not much notice
[29 Apr 20:57] Sparks: OK, s/Zikula/$FEDORA_WIDE_CALENDAR/
[29 Apr 20:57] +Isn't there also a shared evolution calendar or some such.
[29 Apr 20:57] +Sparks: there is a group in infra evaluating
calendars right now
[29 Apr 20:57] +Oh, cool
[29 Apr 20:57] doesn't matter what the implementation, as long as
it's being done openly somewhere
[29 Apr 20:57] ke4qqq: Thank you sir! (what he said.)
[29 Apr 20:57] +exactly
[29 Apr 20:57] +and if infra is working on it thats one less task for us
[29 Apr 20:57] +very true
[29 Apr 20:58] +Do we know what the status is on that?
[29 Apr 20:58] +They have narrowed it down significantly
[29 Apr 20:59] +Do you know if they have looked at Zikula?
[29 Apr 20:59] Sparks: An email to the appropriate list would be a
good way to poke people
[29 Apr 20:59] +dropping stuff that won't work or is Java etc.
[29 Apr 20:59] +they did
[29 Apr 20:59] IRC doesn't get seen by anyone not online.
[29 Apr 21:00] I was under the impression that Zikula was a
possibility, but I don't know that anyone has said, " will be the
calendar, and it will be set up by ."
[29 Apr 21:00] +no one has narrowed it down that far
[29 Apr 21:00] Anyway, I think we're spending a lot of Docs time on
calendars instead of docs at this point.
[29 Apr 21:01] +Well... the calendar will be a docs tool.
[29 Apr 21:01] Before we got on this topic, jjmcd was talking about
release notes status
[29 Apr 21:01] +how about for now we say personal calendars along
with whats avaliable will be used and its on us to remeber to do this
[29 Apr 21:02] +
[29 Apr 21:02] * Sparks should have put the freezes on his calendar a while back
[29 Apr 21:02] +
[29 Apr 21:02] * jjmcd had then on his calendar, but has been in his
own little hidey-hole
[29 Apr 21:03] Right zoglesby, people are welcome to use their own
tools personally, and for anything team-related we should use the
available Fedora capabilities
[29 Apr 21:03] +jjmcd: Anything else on the RN?
[29 Apr 21:03] +I think that's about it, other than the F12 topoc
[29 Apr 21:04] +jjmcd: Wanna talk about that now?
[29 Apr 21:04] +May as well
[29 Apr 21:04] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - Docs_decisions_for_F12
[29 Apr 21:04] +During F11, a number of questions came up
[29 Apr 21:04] +mostly aroung publican
[29 Apr 21:04] +We made some short term decisions to push through the F11 notes
[29 Apr 21:05] +but between now and F12, we ought to consider the right answers
[29 Apr 21:05] +I've listed some of them at Docs_decisions_for_F12
[29 Apr 21:05] +Over the next few weeks I'd like to see us talk about them
[29 Apr 21:06] +are we moving everything to publican?
[29 Apr 21:06] +FOr F11 we used Publican for the release notes
proper, but hammered it into looking the same as F10
[29 Apr 21:06] +So homework for next week's meeting is to review the
page and come back with input or questions.
[29 Apr 21:06] +ANd bleed on the page
[29 Apr 21:06] +maybe add more
[29 Apr 21:07] +zoglesby, that is one of the questions
[29 Apr 21:07] +
[29 Apr 21:07] * zoglesby needs to read that page...
[29 Apr 21:09] +Not sure we need to say much more right now
[29 Apr 21:09] +Okay...
[29 Apr 21:10] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - DocsProject wiki pages changes
[29 Apr 21:10] +Just wanted to touch on this real quick.
[29 Apr 21:10] +I worked on the Docs Project page earlier today.
[29 Apr 21:11] +I tried to clean up the language and will continue to
work on it this week to try to simplify what we are trying to say.
[29 Apr 21:12] +There is still some work to do.
[29 Apr 21:12] +Any questions or comments?
[29 Apr 21:12] +Due to the hour...
[29 Apr 21:12] --- Sparks (n=sparks@fedora/Sparks) changed topic: Docs
Project - All other business
[29 Apr 21:12] +Anyone have anything else?
[29 Apr 21:13] +i have a few things but they can probably be
discussed in the main channel
[29 Apr 21:13] +you guys going to be around for a bit?
[29 Apr 21:13] +radsy: I will be
[29 Apr 21:13] +wanted to clear up this selinux thing
[29 Apr 21:14] +Anything else?
[29 Apr 21:14] +i'm good
[29 Apr 21:15] +5
[29 Apr 21:15] +4
[29 Apr 21:15] +3
[29 Apr 21:15] +2
[29 Apr 21:15] +1
[29 Apr 21:15] +Thanks everyone for coming!
[29 Apr 21:15] +
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
iEYEARECAAYFAkoUlFQACgkQfQTSQL0MFMF/wgCgmA/naUqXDg1Vmuop78QoIHl9
XsEAnizmlUb4eaS5hO0q87097DEt/6hA
=k5wQ
-----END PGP SIGNATURE-----
14 years, 11 months
Self-introduction: Ben Cotton
by Ben Cotton
Greetings Fedora-docs-listers,
It recently occurred to me that it is time I gave something back to
the community. I started using Red Hat 8 in college, and eventually
switched to using Linux on my primary desktop. I now make a living as
a sysadmin for RHEL desktops and servers in a small department of a
large Midwestern university. Since I don't have much skill as a
programmer, I decided that the Docs group was a good place to start.
I don't have any formal project experience, but I do fancy myself a
passable writer. Among the accomplishments I'm most proud of during
my tenure as a sysadmin is the creation of an internal wiki for my
department's IT staff. When I took the position, the documentation
was whatever could be found in old e-mail messages. Largely on my own
effort, but with considerable help from the rest of the staff, our
wiki is now a valuable resource. The contents range from detailed
how-to guide to big-picture discussions of the system architecture.
My degree is in meteorology, so I do not have a great deal of formal
training with computers. Most of my knowledge comes from breaking my
computer and then getting it working again. I do have certifications
on Linux (RHCT) and OS X (ACSP), and I try to get training when the
opportunity and budget align. My primary technical skills are in
basic setup and administration: kickstarts, package management, NFS,
CUPS, etc. What I lack in technical skills, though, I make up for in
the ability to find contributors. I tend to bring in people outside
my department to help on specific tasks when their skills better match
the needs.
Here's my GPG key:
[1018 bcotton@boone ~ ]$ gpg --fingerprint AB46AA74
pub 1024D/AB46AA74 2009-02-14
Key fingerprint = B09D 841C 1347 091A 3BD0 759F D9CD 1319 AB46 AA74
uid Ben Cotton <bcotton(a)purdue.edu>
sub 2048g/4BB9F3C7 2009-02-14
I think that covers all I need to share. I look forward to working
with all of you and contributing to the project.
BC
--
Ben Cotton
14 years, 11 months