edx-platform

Files

Kyle McCormick 9f380b9ccd refactor: import common/lib/ modules from canonical locations (#30533 )

Unfortunately, some code in edx-platform is imported
relative to sub-projects instead of the repository root.
The only three remaining instances of this are:
* common/lib/xmodule/xmodule (imported as just 'xmodule')
* common/lib/capa/capa (imported as just 'capa')
* openedx/core/lib/xblock_builtin/xblock_discussion
  (imported as just 'xblock_discussion')

For more details on the situation, see:
https://openedx.atlassian.net/browse/BOM-2579
(public, but requires Atlassian account creation).

We would like to get to a point where all edx-platform
import paths match their folder paths, relative to the repo
root. For now, though, all common/lib/capa and common/lib/xmodule
code should be imported as just `from capa` and `from xmodule`,
respectively. Importing using the full `common.lib.xmodule.xmodule...`
path will often work, but it instantiates a second instance of all
modules imported this way, which in the past has led to very
difficult-to-diagnose bugs.  It also confuses tooling such as
import-linter, which we are trying to add to edx-platform
(see https://openedx.atlassian.net/browse/BOM-2576)

2022-06-06 09:54:16 -04:00

config

docs: update toggle docs

2021-04-01 21:58:29 -04:00

django_comment_client

feat: send email to moderators after content is reported

2022-04-27 22:18:56 +05:00

management

feat: Add management command for updating discussion user stats for all users in a course (#29973 )

2022-04-13 19:09:50 +05:00

notification_prefs

refactor: pyupgrade second iteration

2021-04-30 15:35:47 +05:00

rest_api

fix: added global staff to prevliged access (#30506 )

2022-05-31 13:01:03 +05:00

settings

docs: update toggle docs

2021-04-01 21:58:29 -04:00

signals

fix: fix issues with reported content email notifications (#30522 )

2022-06-02 11:09:32 +05:00

static/discussion

Short Circuit Digest preferences call on Discussion Home Page

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

templates/discussion

fix: fix variable name in email template

2022-06-02 12:38:24 +05:00

tests

feat: Added permissions for course staff to discussion MFE (#30143 )

2022-03-30 15:34:09 +05:00

__init__.py

Discssions as a plugin

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

apps.py

BOM-2358 : Pyupgrade in dashboard, debug, discussion apps (#26529 )

2021-02-22 15:42:21 +05:00

exceptions.py

BOM-2278 : Pylint amnesty in discussion, dashboard (#26275 )

2021-02-03 18:15:14 +05:00

plugins.py

fix: revert discussion tab redirection (#30492 )

2022-05-27 16:01:24 +05:00

README.rst

Remove notifier_api app DEPR-111 (#25464 )

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

tasks.py

refactor: import common/lib/ modules from canonical locations (#30533 )

2022-06-06 09:54:16 -04:00

toggles_utils.py

feat: send email to moderators after content is reported

2022-04-27 22:18:56 +05:00

toggles.py

refactor!: update CourseWaffleFlag (#30351 )

2022-05-10 15:08:59 -04:00

urls.py

BOM-2781: Django codemods on LMS (2) (#28852 )

2021-11-11 17:52:57 +05:00

views.py

feat: allow banner for discussions moderators (#30502 )

2022-05-31 13:00:41 +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
==================