Mentat

I have verified (sorry for the spam), that the mailing to group managers works when following conditions are met: group must have self management enabled, user must request group membership during registration. Information about mails being sent in now logged more verbosely into /var/mentat/log/mentat-hawat.py.log file.

We can make the "Requested group memberships:" field required in the registration form to prevent this from happening again, if that is desirable. Also we can remove the "self management enabled" requirement by discarding the managed column from groups table and simply always send information emails in case group has any managers set.

Should I do the aforementioned changes?

Pavel Kácha wrote in #note-3:

Jan Mach wrote in #note-2:

I have verified (sorry for the spam), that the mailing to group managers works when following conditions are met: group must have self management enabled, user must request group membership during registration. Information about mails being sent in now logged more verbosely into /var/mentat/log/mentat-hawat.py.log file.

Thanks! On the devel, or deployed on hub also?

Only on mentat-alt. There were no major code changes, I have just added some log writes to be able to better verify the code flow. There are no code flow fixes.

We can make the "Requested group memberships:" field required in the registration form to prevent this from happening again, if that is desirable. Also we can remove the "self management enabled" requirement by discarding the managed column from groups table and simply always send information emails in case group has any managers set.

Should I do the aforementioned changes?

I'd NOT go for required field - sometimes it is desirable to have users, which are members of no group (707 developers, students, ...)

OK.

Discarding 'managed' column makes sense (if admin does not want to manage group, it does not have to be an admin). However, couldn't there be a clash with Žerdík's changes, which Rajmund is going to integrate (#6239)? If so, I'd wait with it.

No, there should not be any clashes. Žerdik`s changes are related to reporting settings contained mostly in reporting_settings table. This is a managed column in groups table, unrelated to reporting.

After the discussion we will proceed to remove managed column from groups table.

I have removed all uses of managed attribute from Group model. Ready to merge to devel branch for testing.

Merged into devel.

Marking as resolved. When you think it was tested for enough time, we can close. I have already deleted the branch, in case the fix is needed it will be better to do it directly in devel branch to save some time.

Changing back to in-review as it is at mentat-alt. (See Development_guidelines.)

In 7cdebc18 in the migration c2b4c2af6196_removed_groups_managed.py the managed column is set as not null. But there is no default value, so downgrading results in IntegrityError. I use downgrading quite often so I would appreciate if it was possible to downgrade.

As it was discussed on 2021-12-01 meeting, I patched the downgrade, pushed the commit to devel and deployed the new version on mentat-alt.