Hi
(cc'ing Ankur since he has expressed interest in helping with the admin tasks)
* Form for local login is still shown in the login page even though this is disabled. This continues to cause confusion among new users and the fix is upstream
https://fedorahosted.org/fedora-infrastructure/ticket/3761
We need to pull this in as a hotfix and test it.
* FAS openid doesn't seem to be working for some people. I am unsure of the current status
* Cron job for sending reminders to accept an answer
https://fedorahosted.org/fedora-infrastructure/ticket/3762
We have enabled this feature but it is essentially non-functional without the cron job running
* Enabling Ask Fedora to send emails async
https://fedorahosted.org/fedora-infrastructure/ticket/3763
Celery was an option but there seems to be some amount of concern with the additional complexity. Upstream is of the opinion that celery isn't that much of an overhead
http://askbot.org/en/question/10531/simpler-alternative-to-celery/
I looked out for options and the one that is actively maintained is django post office
https://pypi.python.org/pypi/django-post_office
It isn't packaged yet but requires no code changes and very simple configuration. If someone has the time, please test this in staging. I will do the packaging once it is confirmed that it serves our purpose.
Older pending tasks ---------------------------
* Fedora theme
Related:
* Making optional fields in FAS more obvious
https://lists.fedoraproject.org/pipermail/infrastructure/2013-March/012651.h...
Rahul
On Thu, Apr 25, 2013 at 05:50:36PM -0400, Rahul Sundaram wrote:
Hi
(cc'ing Ankur since he has expressed interest in helping with the admin tasks)
This is a good task list to keep track of. Thanks for compiling it, Rahul.
Ankur, I'd be glad to help brainstorm about how to fix each of these. Feel free to email me directly or get in touch on IRC if you'd like to start working through them.
Hi Ankur,
On 04/25/2013 10:45 PM, Ralph Bean wrote:
Ankur, I'd be glad to help brainstorm about how to fix each of these. Feel free to email me directly or get in touch on IRC if you'd like to start working through them.
Did you have a chance to look at this list? If you don't have time, let me know. Thanks!
Rahul
On Fri, 2013-05-03 at 22:45 -0400, Rahul Sundaram wrote:
Did you have a chance to look at this list? If you don't have time, let me know. Thanks!
Hi Rahul,
I've been in touch with Ralph off list (I didn't want to clutter the ML with my noob queries). I've just pushed a commit that should enable the cron job for reminders on staging. Can you please enable these from the django admin interface for staging[1] so we could check if it works? Could you also check the commit once, just to be sure I did it right (commit: 004cddd)?
Looks like my push created a new "testing" remote branch. I'm not sure where I got it from. Many apologies for this folks. It made zodbot go nuts trying to announce all the 14000+ commits. I reported this on #fedora-admin and relrod said he'd take care of it.
Luckily it isn't something irreparable. So much for an uneventful first commit :/
[1] https://ask.stg.fedoraproject.org/settings/EMAIL/
On Sat, 04 May 2013 17:46:59 +1000 Ankur Sinha sanjay.ankur@gmail.com wrote:
On Fri, 2013-05-03 at 22:45 -0400, Rahul Sundaram wrote:
Did you have a chance to look at this list? If you don't have time, let me know. Thanks!
Hi Rahul,
I've been in touch with Ralph off list (I didn't want to clutter the ML with my noob queries). I've just pushed a commit that should enable the cron job for reminders on staging. Can you please enable these from the django admin interface for staging[1] so we could check if it works? Could you also check the commit once, just to be sure I did it right (commit: 004cddd)?
Looks like my push created a new "testing" remote branch. I'm not sure where I got it from. Many apologies for this folks. It made zodbot go nuts trying to announce all the 14000+ commits. I reported this on #fedora-admin and relrod said he'd take care of it.
Luckily it isn't something irreparable. So much for an uneventful first commit :/
No worries. ;) it happens and it helped us fix something that could well have bitten us another time.
Thanks for working on the ask items!
kevin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hello,
I have been working on this last week. The current status according me is:
On Thu, Apr 25, 2013 at 05:50:36PM -0400, Rahul Sundaram wrote:
- Form for local login is still shown in the login page even though
this is disabled. This continues to cause confusion among new users and the fix is upstream
This does not show anymore.
- FAS openid doesn't seem to be working for some people. I am
unsure of the current status
This is a bug in FAS-OpenID (actually in HAProxy triggered by client code, but it's on the FAS-OpenID side), which I am currently working on.
Patrick
Hi
On Fri, Apr 26, 2013 at 2:44 AM, Patrick Uiterwijk wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hello,
I have been working on this last week. The current status according me is:
On Thu, Apr 25, 2013 at 05:50:36PM -0400, Rahul Sundaram wrote:
- Form for local login is still shown in the login page even though
this is disabled. This continues to cause confusion among new users and the fix is upstream
This does not show anymore.
- FAS openid doesn't seem to be working for some people. I am
unsure of the current status
This is a bug in FAS-OpenID (actually in HAProxy triggered by client code, but it's on the FAS-OpenID side), which I am currently working on.
Thanks for pitching in. Much appreciated
Rahul
On Thu, 2013-04-25 at 17:50 -0400, Rahul Sundaram wrote:
https://pypi.python.org/pypi/django-post_office
It isn't packaged yet but requires no code changes and very simple configuration. If someone has the time, please test this in staging. I will do the packaging once it is confirmed that it serves our purpose.
I've packaged it up and it's under review now[1]. As soon as it's approved, I'll test it over at staging and see how it goes.
https://bugzilla.redhat.com/show_bug.cgi?id=959172
On 05/05/2013 04:02 AM, Ankur Sinha wrote:
I've packaged it up and it's under review now[1]. As soon as it's approved, I'll test it over at staging and see how it goes.
Thanks. You can drop a mail to upstream of django post office and let him know. I *think* it stores the email in the db by default based on the template but might be useful to confirm this.
Rahul
Hi folks,
On Sun, 2013-05-05 at 13:38 -0400, Rahul Sundaram wrote:
Thanks. You can drop a mail to upstream of django post office and let him know. I *think* it stores the email in the db by default based on the template but might be useful to confirm this.
Rahul
The package got approved and I've just finished pushing updates to bodhi. Yep, it does seem to make use of the db to store mails.
The "installation" and "quick start" sections[1] detail how it's to be used:
Installation
.. image:: https://travis-ci.org/ui/django-post_office.png?branch=master
Install from PyPI (or you can `manually download it from PyPI http://pypi.python.org/pypi/django-post_office`_)::
pip install django-post_office
So, install the rpm, in our case
- Add ``post_office`` to your INSTALLED_APPS in django's ``settings.py``:
.. code-block:: python
INSTALLED_APPS = ( # other apps "post_office", )
Run ``syncdb``::
python manage.py syncdb
Set ``post_office.EmailBackend`` as your ``EMAIL_BACKEND`` in django's ``settings.py``::
EMAIL_BACKEND = 'post_office.EmailBackend'
Quickstart
To get started, make sure you have Django's admin interface enabled. Create an ``EmailTemplate`` instance via ``/admin`` and you can start sending emails.
.. code-block:: python
from post_office import mail mail.send( ['recipient1@example.com', 'recipient2@example.com'], 'from@example.com', template='welcome_email', # Could be an EmailTemplate instance or name context={'foo': 'bar'}, )
The above command will put your email on the queue so you can use the command in your webapp without slowing down the request/response cycle too much. To actually send them out, run ``python manage.py send_queued_mail``. You can schedule this management command to run regularly via cron::
* * * * * (/usr/bin/python manage.py send_queued_mail >> send_mail.log 2>&1)
I can set up the cron job at the end, like I did earlier for askbot. I'm not sure how to do the other steps on the server (is root access required?). Could you folks tell me how to go about it, (or do it, if you have the cycles yourself ;) )
I'll go drop upstream a mail in the time being.
On a related note, has anyone received any "accept answer reminders"? I was wondering how we'd test that.
[1] https://pypi.python.org/pypi/django-post_office
infrastructure@lists.fedoraproject.org