Looks like the inimitable David Nalley has the Zikula 1.1.2 package into testing for F-10/F-11/EL-5. The new package eliminates a bunch of bundled libs, fixes some Requires/BuildRequires stuff, and is generally awesome.
I think the publictest* machines are allowed to draw on the epel-testing repo, so it might be worthwhile to update to the new package, so we're testing the latest and greatest. I don't think I have the sysadmin-noc privs needed, can someone do that?
Thanks David!
On Mon, 2009-08-24 at 08:48 -0400, Paul W. Frields wrote:
Looks like the inimitable David Nalley has the Zikula 1.1.2 package into testing for F-10/F-11/EL-5. The new package eliminates a bunch of bundled libs, fixes some Requires/BuildRequires stuff, and is generally awesome.
I think the publictest* machines are allowed to draw on the epel-testing repo, so it might be worthwhile to update to the new package, so we're testing the latest and greatest. I don't think I have the sysadmin-noc privs needed, can someone do that?
As long as it doesn't pummel the theme work we've been doing! o_O (is there any risk of that? It's in /usr/share/zikula/themes/fedora)
~m
2009/8/24 Máirín Duffy mairin@linuxgrrl.com:
On Mon, 2009-08-24 at 08:48 -0400, Paul W. Frields wrote:
Looks like the inimitable David Nalley has the Zikula 1.1.2 package into testing for F-10/F-11/EL-5. The new package eliminates a bunch of bundled libs, fixes some Requires/BuildRequires stuff, and is generally awesome.
I think the publictest* machines are allowed to draw on the epel-testing repo, so it might be worthwhile to update to the new package, so we're testing the latest and greatest. I don't think I have the sysadmin-noc privs needed, can someone do that?
As long as it doesn't pummel the theme work we've been doing! o_O (is there any risk of that? It's in /usr/share/zikula/themes/fedora)It
We'll upgrade the FI zikula test instance on pt6 (https://publictest6.fedoraproject.org/zikula) to 1.1.2 asap. Blockers on doing so:
* Make sure we don't pummel Simon's fasauth module
* Make sure we don't pummel Mo's theme work.
* Give Robyn a chance to finish setting up the workflow (which the upgrade will provide a good chance to document - it's adding certain categories and tags and such, all from the web interface... not something we should have to package). This means we should wait until after tomorrow's Marketing meeting so that we don't interrupt her work.
The plan:
* make 3 separate repositories for the 3 packages we're dealing with: zikula-module-fasauth (Simon), zikula-theme-fedora (Simon), zikula-theme-insight (Mo), and make sure Simon and Mo are set up to work with them and that doing so will not be overtly painful. * Robyn demonstrates workflow at Marketing meeting tomorrow, we document it copiously. * upgrade pt6 * repopulate pt6 with modules/themes from repos as appropriate * carry on
--Mel
PS: Yea verily Mel now doth see the value of doing things Properly, with Repositories and Stuff. The more experienced amongst thee may now point and laugh and quoth "thou shouldt have Knoewn Bettar."
On Mon, Aug 24, 2009 at 11:49, Mel Chuamel@redhat.com wrote:
We'll upgrade the FI zikula test instance on pt6 (https://publictest6.fedoraproject.org/zikula) to 1.1.2 asap. Blockers on doing so:
Make sure we don't pummel Simon's fasauth module
Make sure we don't pummel Mo's theme work.
Give Robyn a chance to finish setting up the workflow (which the
upgrade will provide a good chance to document - it's adding certain categories and tags and such, all from the web interface... not something we should have to package). This means we should wait until after tomorrow's Marketing meeting so that we don't interrupt her work.
The plan:
- make 3 separate repositories for the 3 packages we're dealing with:
zikula-module-fasauth (Simon), zikula-theme-fedora (Simon), zikula-theme-insight (Mo), and make sure Simon and Mo are set up to work with them and that doing so will not be overtly painful.
- Robyn demonstrates workflow at Marketing meeting tomorrow, we document
it copiously.
- upgrade pt6
- repopulate pt6 with modules/themes from repos as appropriate
- carry on
--Mel
PS: Yea verily Mel now doth see the value of doing things Properly, with Repositories and Stuff. The more experienced amongst thee may now point and laugh and quoth "thou shouldt have Knoewn Bettar."
The auth and fedora theme should be installed via yum from the infra repo.
Mo: Is your work being added to the theme rpm?
--Eric
On Mon, Aug 24, 2009 at 07:25:28PM -0400, Eric Christensen wrote:
Mo: Is your work being added to the theme rpm?
I think we were working on that earlier; I saw her request for gitfedora-zikula go through a few hours ago, for example. It was wondering about clobbering her changes with the new Zikula instance that got Mel on the track of sorting that out.
So, pretty soon now Mo will be adding to the theme rpm, a specific one for FI if I read that correctly.
That is a good idea, since it's pretty clear that FI will have a separate instance of Zikula than Docs. If Zikula ends up under a few of our other web presences, the separate theme packaging is a Good Thing.
Since it's done in git, it might be interesting if we could have theme all source the same set of files in some way, with the different themes as branches, and different RPMs from each branch.
- Karsten
On Mon, 2009-08-24 at 16:46 -0700, Karsten Wade wrote:
On Mon, Aug 24, 2009 at 07:25:28PM -0400, Eric Christensen wrote:
Mo: Is your work being added to the theme rpm?
I think we were working on that earlier; I saw her request for gitfedora-zikula go through a few hours ago, for example. It was wondering about clobbering her changes with the new Zikula instance that got Mel on the track of sorting that out.
So, pretty soon now Mo will be adding to the theme rpm, a specific one for FI if I read that correctly.
I haven't done anything yet, so bling is still in risk of wipage :(
~m
On Mon, Aug 24, 2009 at 04:46:56PM -0700, Karsten Wade wrote:
On Mon, Aug 24, 2009 at 07:25:28PM -0400, Eric Christensen wrote:
Mo: Is your work being added to the theme rpm?
I think we were working on that earlier; I saw her request for gitfedora-zikula go through a few hours ago, for example. It was wondering about clobbering her changes with the new Zikula instance that got Mel on the track of sorting that out.
So, pretty soon now Mo will be adding to the theme rpm, a specific one for FI if I read that correctly.
That is a good idea, since it's pretty clear that FI will have a separate instance of Zikula than Docs. If Zikula ends up under a few of our other web presences, the separate theme packaging is a Good Thing.
That's true during the test phase, but during production we ought to be able to manage everything under one instance.
On Mon, Aug 24, 2009 at 10:27:24PM -0400, Paul W. Frields wrote:
That's true during the test phase, but during production we ought to be able to manage everything under one instance.
OK, I admit to not knowing how it's structured in terms of being able to handle multiple groups with multiple workflow methods and plugins enabled/disabled.
I presumed it worked like Wordpress or MediaWiki, where there is one auth structure for the whole site. What you describe sounds more like Wordpress MU, with multiple sub-sites within the overall site, and each sub-site can have its own auth structure.
- Karsten
- Make sure we don't pummel Simon's fasauth module
I committed my various fixes and enhancements for the fasauth module to the git repo, so no worries about this.
- Make sure we don't pummel Mo's theme work.
If Mo has been doing this the Zikula gospel way :) she shouldn't have touched any files outside of the theme's directory. In which case, if that theme directory is backed up we are ready to go.
- Give Robyn a chance to finish setting up the workflow (which the
upgrade will provide a good chance to document - it's adding certain categories and tags and such, all from the web interface... not something we should have to package). This means we should wait until after tomorrow's Marketing meeting so that we don't interrupt her work.
I talked with Mike about this - we can preserve the database from staging->production, meaning that basic setup work of this kind will only have to be repeated once we move to staging.
- make 3 separate repositories for the 3 packages we're dealing with:
zikula-module-fasauth (Simon), zikula-theme-fedora (Simon),
Zikula-theme-fedora I haven't touched in ages - Mo may have changed things here though.
I assume when upgrading the whole /usr/share/zikula filesystem gets blown away and replaced? Please correct me if I'm wrong :)
On Tue, 2009-08-25 at 03:24 +0100, Simon Birtwistle wrote:
If Mo has been doing this the Zikula gospel way :) she shouldn't have touched any files outside of the theme's directory. In which case, if that theme directory is backed up we are ready to go.
I haven't, I've been good! :)
But I'm still actively working on it - let me know when I should stop...
~m
I'm tracking the FI upgrade work on https://fedorahosted.org/marketing-team/ticket/23, check 'er out for the latest status (rapid progress == happy, yay!)
Everyone (particularly Mo) can keep on actively working on what they're working on, in the same way they've been working on it; we'll do the transitions individually (and very gently) so as not to interrupt things.
--Mel
logistics@lists.fedoraproject.org