Setting up a weekly zikula test cycle
pcalarco at nd.edu
Mon Feb 8 20:20:17 UTC 2010
Hi Mel --
This is great news! I've applied for an account on the staging server,
and will start to play soonest. Comments below.
On 02/05/2010 02:35 PM, Mel Chua wrote:
> Hi, FWN! (Copying logistics as a FYI.)
> We're at the point where we have Fedora Insight (a.k.a. FI,
> https://fedoraproject.org/wiki/Fedora_Insight) up on staging
> (https://stg.fedoraproject.org/insight/) and ready to have a workflow
> and content put on it. The theme isn't done, nor is the URL schema, but
> everything needed to get content in and through it should be up and
> Our first target for production is to help FWN migrate its workflow from
> ttp://fedoraproject.org/wiki/FWN/WorkFlow to
> http://fedoraproject.org/wiki/FWN/FIWorkFlow - the latter being what
> Pascal and Dale came up with at FUDCON
> (http://fedoraproject.org/wiki/Zikula_hackfest). To figure out when
> we're ready to pull the switch, I'd like to propose the following weekly
> test cycle.
> 1. Every Monday, after FWN is published, we do a little sprint to take
> the just-published FWN content and "republish" it using the FI workflow
> as it's written at that time.
The easiest way to do this is probably to take the version that gets
sent to announce and news lists and chunk these as individual stories at
the beat level. The e-mail version is the most generic ASCII, which
will facilitate entering these into Xinhua in Zikula.
> 2. If we find a bug in the FWN FI workflow, report it (and FWN can fix
> it before the next sprint). If we find a bug in our zikula deployment,
> report it (and the deployment team will fix it before the next sprint).
> 3. Repeat.
> This way, once we flip the switch, we'll already have several back
> issues of FWN queued up on Insight, and a crew that's familiar with
> using the new software. What we need to be ready for this to happen (I
> think we have most of it already, but would like confirmation):
> 1. Making sure that the FWN workflow how-to instructions should be so
> clear that anyone can follow them - I will be there and helping, but
> need instructions to tell me what to do. ;)
> 2. Make sure that any setup (categorization, pagemaster-fu, etc.) needed
> is documented and done on the staging instance - again, this is a "FWN,
> tell us how you are setting up - this is your space!" thing.
I will go through all of the tickets I opened during FUDCon and verify
that these all have been addressed. The vast majority of what was left
after FUDCon was design/CSS-related.
> 3. Figure out who/what-roles from FWN should have what administrative
> privileges in zikula, and make (and hook-in) the appropriate FAS groups
> to make that happen. (I don't think we have done this yet - what would
> you like to do here?)
Two levels perhaps to start:
1) Beat writer: submits story to review/approval queue
2) FWN editor: check spelling, links, grammar, etc. and approve story
> Thoughts? Does this sound like a good next-step for getting started?
Yes. Let's start with this current issue that just went out, and I will
enter each beat in as a story on the staging server, and we'll see if
the tags and such work in terms of aggregating the beats into an issue
that can be subscribed to.
Mel, is there still a weekly Zikula IRC meeting (used to be Wednesday
evenings)? We might be able to meet there as needed to go over
reporting tweaks and such as we move though this, and fix on the fly.
We'll see what kinds of issue arise.
> news mailing list
> news at lists.fedoraproject.org
More information about the logistics