Here is this, such as it is.
<meeting>
<stickster> quaid: Yoo hoo
<quaid> oi
<stickster>
<quaid> sorry, alarm didn't go off (phone batter
died)
<stickster> D'oh!
<quaid> been deep in review of something
<stickster> I should have rung earlire
<stickster> *earlier
<quaid> s'aight
<quaid> hey, so, do our meetings suck now? since not
using the schedule
page all the time?
<quaid> and are we messing with our visibility?
<quaid> and does anyone care?
<stickster> I think the schedule page may be a bit
unrealistic... maybe
we need to concentrate on having a few top-tier things for
each meeting,
and concentrating on pummeling those
<stickster> Otherwise it's quite demoralizing :-(
<stickster> Just looking at the first item is an
indicator that our
process is overwhelming our workload
<stickster> quaid: I think one of our big ticket items
for today is that
we have people signing up to help with translations who need
access to
our CVS
<stickster> Which may conflict slightly with our
earlier policy
decisions
<quaid> hmm
<quaid> well, if we have an existing person in that
language, we have a
mentor
<quaid> sponsor, that is
<quaid> if we don't, we have some choices:
<quaid> * Ask another translator from another language
to be the sponsor
<quaid> i. Ask another translator from another
language to be the
sponsor
<quaid> ii. Ask a Red Hat translator to be the sponsor
<quaid> iii. Ask the new person to be the sponsor
<quaid> iv. ???
<stickster> Alternately we can ask the new volunteer
translator to
recruit a second from the translation project, right?
--> Sopwith (n=sopwith nat-pool-rdu.redhat.com)
has joined #fedora-docs
<stickster> Hi Eliot
<stickster> [sp] sorry
<quaid> stickster: yes
<quaid> that's a good point
<quaid> most important is to avoid the
solo-translators as we've had in
the past
<stickster> Yeah, agreed
<quaid> spread the resonsibility
* quaid pounces on Sopwith
<Sopwith> 'sup
<quaid> curious about MoinMoin upgrade loving.
<quaid> do we have to wait for the SoC project to be
completed? or can
we/should we do an interim update?
<quaid> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=
196961
<quaid> that's the request
<Sopwith> quaid: Sorry, I don't follow moinmoin
closely. skvidal and
nman64 would be the people t oask
<quaid> Sopwith: you might want to changethe default
assignee for that
component away from gdk, btw
<Sopwith> bleah, need to get rid of that bugzilla
product altogether
<Sopwith> OTRS is the best way to bug people about
infrastructure
<quaid> Sopwith: do you read this comment as skvidal
volunteering to do
this:
<stickster> Is OTRS available to non-RH Fedorans?
<quaid> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
id=196961#c2
<Sopwith> stickster: Yup
<Sopwith> https://admin
.fedoraproject.org/ticket/ I think
<stickster> cool... sorry I'm not familiar with it,
but I'll find it and
investigate it
<BobJensen> I think we have targeted a victim then
<Sopwith> quaid: I think he's making a suggestion at
that point, not
necessarily volunteering.
* stickster is evidence of "Yes, we'll even have a
lusers rep on the
Board"
<quaid> Sopwith: can you assign someone to it then?
<stickster> quaid: Onto toolchain then?
<quaid> yep
<stickster> OK... so the packaging as I originally
conceived it
(functionality wise) sucks eggs.
<stickster> Which makes it fortunate that I didn't
expose it to anyone
besides us
<quaid> Sopwith: would it help if I re-requested in
OTRS?
<stickster> I have better ideas now but I think
waiting until after
test2 freeze is prudent
<stickster> Is that sensible to everyone?
<Sopwith> quaid: It'd help keep it higher on the
radar
<Sopwith> <mmcgrath> I'll assign this to myself
and create an OTRS
ticket.
<quaid> ok
<quaid> stickster: agreed on prudence
<quaid> stickster: just wait until the ISOs are
approved, I reckon
<quaid> just in case we have to rebuild
<quaid> well
<stickster> quaid: +1
<quaid> we want to do the Web-only release first
<stickster> It can safely wait until after taht
<quaid> so ... that depends on schedule, but if
you'll know when that
point hits (web-only put up)
<stickster> *that
<quaid> s/if//
<-- mumumu__ has quit ("Leaving....")
<stickster> See release-notes module for a preview...
although the OMF
file also needs to move into the lang dir, along with
rpm-info as I
discussed with glezos on list
<stickster> We're going to get all the XML into the
lang directories for
max translation power
<quaid> cool
<stickster> I know this has been a long road but I
swear it will be
worth it ;-D
<stickster> I would like to recruit glezos to help
with some of the tool
buildouts
<stickster> He seems very clueful
<stickster> Silence gives consent?
<stickster> I'll check offlist with Tommy to make
sure he's cool with it
<stickster> Maybe he should consider himself already
recruited
<quaid> roger that
<stickster> Maybe we should consider this meeting over
:-\
<quaid> deadline fever, man
<aadil> gnite
<-- aadil (n=aadil ADSL-TPLUS-98-36.telecomplus.net) has left
#fedora-docs ("Going once,..")
<quaid> sorry to kill afternoon :(
<stickster> understood, call it
<quaid> </meeting>
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation
Project
Sr. Developer Relations Mgr. |
fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key:
AD0E0C41
//////////////////////////////////
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\
--
fedora-dsco-list mailing list
fedora-dsco-list redhat.com
https://www.redhat.com/mailman/listinfo/fedora-dsco-list
|