Beta Release Readiness Meeting - Thursday, Apr. 19, 1900 UTC (3pm Eastern)
by Robyn Bergeron
date: 2011-04-14
place: irc.freenode.net #fedora-meeting
time: 19:00 UTC (3 PM Eastern/ 12 PM Pacific)
This Thursday, April 14, we will meet to make sure we are
coordinated and ready for the public release of the Fedora 15 Beta
release on Tuesday, April 19, 2011.
https://fedoraproject.org/wiki/Release_Readiness_Meetings
This meeting works best when we have representatives from all of the
teams so we'll be looking for the following people to attend or send a
representative.
Ambassadors -- Pierros Papadeas
Design -- Máirín Duffy (likely need an alternate here - Emily?)
Documentation -- Zach Oglesby
FESCo -- Kevin Fenzi
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Jared Smith
Infrastructure -- Kevin Fenzi
Marketing -- Robyn Bergeron
Quality -- James Laska
Release Engineering -- Dennis Gilmore
Translation -- Noriko Mizumoto
Websites -- Ricky Zhou
See you Thursday!
-Robyn
13 years
RE: Fedora Weekly News 270
by Pascal Calarco
Done, thanks, Paul!
https://fedorahosted.org/fedora-infrastructure/ticket/2726
- pascal
________________________________________
From: Paul Frields [stickster(a)gmail.com]
Sent: Tuesday, April 12, 2011 10:06 AM
To: news(a)lists.fedoraproject.org
Cc: Pascal Calarco
Subject: Re: Fedora Weekly News 270
On Mon, Apr 11, 2011 at 9:16 AM, Pascal Calarco <pcalarco(a)nd.edu> wrote:
> FWN 270 is available now on both staging and publictest09:
>
> http://insight.stg.fedoraproject.org/fwn/270
>
> http://publictest09.fedoraproject.org/drupal/fwn/270
>
> Paul, there is one difference between how these two are laid out. On pt09, the beats are in the correct order; on staging, the beats are rearranged in alphabetical order of the beat name. Otherwise, looks great!
>
> - pascal
Sorry about that Pascal.
We should probably talk again about the "too many places" problem --
we probably need to blow away the staging host so things will be less
confusing. You are now able to publish news directly on
insight.fedoraproject.org -- you don't need to stage or test FWN
because we've delivered that capability now.
If you find the ordering problem on the production site (insight.fp.o)
please file a ticket and we'll get it fixed pronto!
Paul
13 years
Insight status during the beta freeze.
by Stephen John Smoogen
The insight staging servers are not under the current freeze so if
people want to make changes, updates things like that they are free to
do so. The insight production server does not technically fall under
the freeze but in spirit should get +1 from website people and +1 from
sysadmin-main for any changes done to it.
--
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
13 years
[Insight] Database snapshots
by Paul W. Frields
Smooge et al.,
If we wanted database snapshots to be deposited somewhere, so we could
pick them out and import them on the upcoming insight.dev host, how
should we go about that? Should we have it simply email the dump to
members of, say, cmsadmin-members(a)fp.o? Or is there somewhere we
could have an unattended job write that DB?
Note that we'll exempt the 'users' table in the DB from being dumped.
That will prevent the only password in the DB -- the one belonging to
Drupal uid=1 (the app admin) -- from being sent or stored anywhere
else. We'd also leave out 'users_roles' since it wouldn't match on a
different box anyway.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Red Hat Summit/JBossWorld -- Register now! http://.theredhatsummit.com
13 years
[Insight] Eureka!
by Paul W. Frields
Our current Flexifilter module for FWN has several drawbacks:
* It only handles a few simple cases (headings, emphasis, bold, links)
* It's very difficult to customize thanks to an unpleasant interface
* It also requires us to use the Footnotes module just so we can
handle <ref> in wiki text
Tonight, because I needed it for another project, I figured out how to
use the mediawiki_api module, and it works perfectly against the
Fedora wiki. It allows the writer to use basically any markup our wiki
allows, and converts the text to HTML internally. Whenever the user
previews or saves changes, it calls the MediaWiki API to convert the
text.
I'm putting in a ticket so we can move to this module, because it
eliminates some custom work we otherwise have to maintain (the
flexifilter) and extend upon request.
--
Paul
13 years
