With the recent update to Askbot, there has been a number of offlist
discussions related to Ask Fedora and I wanted to summarize what I think
needs to be done and some points to discuss
* Multi-language support:
This is a very commonly requested feature. Need to set
Requires Django 1.4 or higher. I assume the Django modules that Askbot
depends on needs to require Django 1.4 as well.
* Enable sub groups aka meta.ask.fedoraproject.org
We need to test this in the staging instance first
* Local user support
A few users don't want to use openid. Should we enable local user? What
are the security implications of that?
* Integrate FAS support:
Currently its not obvious that one can use their FAS account to login
and we need to make this a prominent option
* Fedora theme:
I don't know the status of this.
* Tinymce Django module is broken. It will be nice to get this fixed
If anyone wants to work on bugs and feature requests, I have a whole
bunch of them. Upstream is looking for help
Some of them like the ability to mark a particular question as duplicate
of another is sorely needed
We lost access to internetx01 earlier today. No response from serial
console. No idea what the problem is. Please reboot or let us know
what issues may be involved
internetx01.fedoraproject.org has address 220.127.116.11
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me." —James Stewart as Elwood P. Dowd
At FUDCon when we opened the fedora-infra GitHub group account, we
checked what was available and both fedora & fedoraproject were already
taken, but unused. At that time I took the liberty of contacting GitHub
to see if they were OK to give us back the handle for fedoraproject,
since it had no repos.
They just got back to me and deleted the fedoraproject account, so I
could open a new one. I've added the usual suspects as group admins.
I don't know if you want to move repos over to this account (it should
be pretty easy, just create the repo, change the remote and push), but
in any case I think it's good that it now belongs to us.
http://aurelien.bompard.org ~~~~~~ jabber: aurelien(a)bompard.org
This mail is displayed with recycled electrons.
The upstream ansible folks have been discussing a 'best practices' doc
and I have been pondering how we want to setup things on our ansible
instance before we add a bunch more things to it.
So, some outstanding questions for comment/discussion:
a) I think I like the idea of splitting out per role trees for things.
But we need to decide what level of granularity a 'role' is.
For example, mirrormanager in puppet is a single module.
However, it's really:
mirrormanager proxy setup files
mirrormanager mirrorlist server web app
mirrormanager web app (the admin part)
mirrormanager backend scripts (crawler, creating lists, etc)
So, for our purposes should we have mirrormanager all in the same
'role' tree? or should we split it out by functionality?
Many roles won't have this issue, as they will be simpler.
b) What would be the workflow for staging with ansible?
Ie, I want to make some config changes only in staging and iron them
out and then merge them back to production when ready. Do we copy the
role and modify? Do we require only changing vars and seperate files?
Will be thinking on it more, but input welcome.