On 5/20/19 1:14 PM, Ben Cotton wrote:
Hi folks,
You may have noticed the CommBlog WordPress dashboard says we need to
upgrade PHP on the host. I opened a ticket with the infra team[1] and
the options are basically:
1. Move communityblog into the wordpress cloud and have them manage it.
2. Move communityblog into a F30 container which would sit in the next
generation community openshift cloud.
3. Deal with it
Assuming any customization we've done (FAS auth, fedmesg, etc) can be
moved to a hosted WordPress, I'm inclined to say option 1. Assuming
the Council or CPE team will fund it, it's a good way to take one more
thing off the plate of the infra team and make sure we're always up to
date. Option 2 is also a decent choice. Option 3 works for now, but
we'll probably reach a point that it becomes a problem and when it
does, it wiil probably be pain. (Either options 1 or 2 are probably
not going to rise to the top of the stack for a couple of months)
Thoughts?
[1]
https://pagure.io/fedora-infrastructure/issue/7806
The Fedora Magazine has the same issue. Usually the CommBlog "follows"
whatever the Magazine does for its infrastructure since they are more or
less the same base configurations.
I prefer Option #1. I have a strong preference that infrastructure
components of the CommBlog are managed by a *paid* team whose
responsibilities include maintaining these sites. At least on the
CommBlog end, the responsibility separation between the community and
infrastructure was not defined and caused hiccups like deploying theme
updates to fix bugs taking a couple years and also how to manage
backups. I am not aware of a backup plan for the CommBlog but I might
not have looked closely enough.
I see this change enabling editors to spend less time being volunteer
sysadmins and more time focusing on the content being published.
--
Cheers,
Justin W. Flory
justinwflory.com
TZ=America/New_York
Pronouns: he/him/his