Kiran Jonnalagadda
Kiran Jonnalagadda
Immutable membership records are currently defined as a two-part model: 1. Identification of the subject, access privileges and other associated data, with metadata on who created the record and when....
Content on the website needs to be tagged and categorised to aid user-led discovery. The current account/project hierarchy is editorial-led and optimised for production, not consumption. We have the choice...
We accept a phone number in two places: at login, and when adding a phone number to the account. This input widget uses `type="tel"` and renders as a plain text...
The Notification system as introduced in #835 (originally defined in #605) does not host any content, by design. Instead it has a type defined as a Python class, a set...
There is a growing need for content moderation and automatic classification into spam, or into topics (from #1421). #669 introduced `CommentModeratorReport` model that is applied to spam in comments. It...
The sponsor model introduced in #465 (as a `SponsorMembership` since it has a membership base) is an okay start, but vastly insufficient to be a public feature. This issue attempts...
Membership records (#401) are designed to keep records for the platform's needs first. For instance, if someone has been removed from an organization and files a request with customer support,...
These membership types serve two overlapping purposes: 1. Grant access rights 2. Grant moral credit without access rights The latter case comes up when a collaborator in a submission must...