edx-platform

Files

David Ormsbee a333a71411 Format blackout dates to match rest of Discussions API.

Technically, both "2020-10-20T23:59:00Z" and "2020-10-20T23:59:00+00:00"
are ISO-8601 compliant, though the latter is preferred. The Discussions
API uses the "Z" notation for almost all its dates, except for the
course blackout dates (those times when students aren't allowed to post
anything because it would threaten exam integrity). That's because the
blackout dates are manually formatted using datetime.isoformat().

As best as I can tell, we've always passed back the "+00:00" for the
blackout dates. But at some point, this broke the expectations of the
mobile apps, which expect the "+Z" format, like the rest of the API.
This commit changes the blackout dates to be returned in +Z format when
the blackout datetimes are specified by the user in UTC (which is almost
always the case–I suspect the mobile clients would break if the dates
were specified in other timezones anyhow).

2020-11-23 10:30:12 -05:00

config

Fixing code-annotations (#25539 )

2020-11-06 12:52:08 -05:00

django_comment_client

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

management

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

notification_prefs

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

rest_api

Format blackout dates to match rest of Discussions API.

2020-11-23 10:30:12 -05:00

settings

Store Discussions ID Map on CourseDiscussionSettings model when course publish signal is fired.

2018-05-03 17:23:30 -04:00

signals

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

static/discussion

Short Circuit Digest preferences call on Discussion Home Page

2020-04-24 16:00:46 +05:00

templates/discussion

Suppress PII from discussion/forum (#25298 )

2020-10-08 19:02:41 +05:00

tests

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

__init__.py

Discssions as a plugin

2018-02-23 09:23:53 -05:00

apps.py

Extracting plugin app from edx-platform (#24678 )

2020-08-12 07:48:53 -04:00

exceptions.py

Make the team discussion thread private

2019-10-18 13:06:50 -04:00

plugins.py

Use full names for lms.djangoapps imports (#25401 )

2020-11-04 08:48:33 -05:00

README.rst

Remove notifier_api app DEPR-111 (#25464 )

2020-10-29 11:17:23 -04:00

tasks.py

set code_owner for celery tasks

2020-11-17 15:33:33 -05:00

urls.py

Fix failures caused by removing lms/djangoapps from sys.path

2020-09-23 10:05:37 -04:00

views.py

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

README.rst

Status: Maintenance

Responsibilities
================
The Discussion app powers the Open edX forums experience.

Direction: Move and Extract
===========================
Discussions related functionality is scattered across a number of places and should be better consolidated. Today we have:

* ``lms/djangoapps/discussion``
* ``openedx/core/djangoapps/django_comment_common``
* ``openedx/core/lib/xblock_builtin/xblock_discussion``

Ideally, what we want in the long term is for all of this extracted into a new repository that holds the code for both the inline discussion XBlock as well as all the Django apps.

That being said, it's not clear what the path forward for this app is. Forum functionality is something that has not been actively worked on for a while, and it's been suggested that we should remove this app altogether in favor of having better integration with other more established forum software. This decision is usually complicated by the desire to have tight integration with courseware and access to data for analytics.

Regardless, check with Product before undertaking any major refactoring work here.

Glossary
========

More Documentation
==================