aleksis/AlekSIS-Core

Fork 0

Include agreements #157

New issue

Open

opened 2020-01-15 11:17:25 +01:00 by nik · 15 comments

nik commented

2020-01-15 11:17:25 +01:00

Owner

Most schools will need consent from users to do several things, or just inform them about legal stuff and get their acknowledgement. ~~I propose django-letsagree for that. It can handle different types of agreements for different groups, i.e. teachers can get the specific agreements for the class register, etc.~~

Most schools will need consent from users to do several things, or just inform them about legal stuff and get their acknowledgement. ~~I propose django-letsagree for that. It can handle different types of agreements for different groups, i.e. teachers can get the specific agreements for the class register, etc.~~

nik commented

2020-01-15 11:17:25 +01:00

Author

Owner

changed due date to January 24, 2020

nik commented

2020-01-15 11:17:32 +01:00

Author

Owner

assigned to @nik

nik commented

2020-01-25 11:21:29 +01:00

Author

Owner

removed due date

nik commented

2020-02-06 15:28:59 +01:00

Author

Owner

unassigned @nik

nik commented

2020-04-13 15:34:57 +02:00

Author

Owner

changed milestone to %"2.0a2"

nik commented

2020-04-17 16:41:27 +02:00

Author

Owner

assigned to @debdolph

tteichler commented

2020-04-17 17:03:25 +02:00

Owner

created merge request !1869 to address this issue

tteichler commented

2020-04-17 17:03:25 +02:00

Owner

mentioned in merge request !1869

nik commented

2020-04-24 12:12:07 +02:00

Author

Owner

This is absolutely necessary for 2.0a2. @debdolph please discuss with @hansegucker whether the behaviour of letsagree and the frontend you drafted are ok, or if we want to look into alternatives.

nik commented

2020-05-29 16:52:20 +02:00

Author

Owner

unassigned @debdolph

hansegucker commented

2020-12-22 21:38:31 +01:00

Owner

@debdolph and I decided that django-letsagree doesn't match our purposes. We have to look into alternatives because we need the option to get user consent.

nik commented

2022-08-15 11:58:17 +02:00

Author

Owner

mentioned in merge request AlekSIS-App-Alsijil!1860

nik commented

2022-08-15 12:00:07 +02:00

Author

Owner

changed title from Include {-django-lets-}agree to Include agree{+ments+}

changed title from **Include {-django-lets-}agree** to **Include agree{+ments+}**

nik commented

2022-08-15 12:00:07 +02:00

Author

Owner

changed the description

nik commented

2022-09-06 18:23:04 +02:00

Author

Owner

This gains new traction together with the Alsijil feature for instructions.

We need a generic framework that can call on users, or parents, to acknowledge something.

Scenarios to take into account:

Agreements on registration/login
Agreements linked to the use of a certain OAuth app
Agreements acknowledged manually, e.g. from Alsijil
Agreements triggered by certain workflows in downstream apps, like Teckids' Paweljong (event registration)

We probably should implement a generic requirements system that can also handle things like "this action requires an address to be available for the person", and the likes.

This gains new traction together with the Alsijil feature for instructions. We need a generic framework that can call on users, or parents, to acknowledge something. Scenarios to take into account: * Agreements on registration/login * Agreements linked to the use of a certain OAuth app * Agreements acknowledged manually, e.g. from Alsijil * Agreements triggered by certain workflows in downstream apps, like Teckids' Paweljong (event registration) We probably should implement a generic requirements system that can also handle things like "this action requires an address to be available for the person", and the likes.