◄ ► | Edit | Home | Admin | en de fr et | Sign in

#6244 (The Groupwise mixin (PrivacyRelated))

by Luc Saffre · in Developers · assigned to Luc Saffre

Summary

I thought that this might become what the ledgers plugin (#5904 (Lino sites with multiple "spaces" (or ledgers or systems or communities)) ) is trying to be. The synodalworld.org website is a first concrete use case. It then turned out that these are different stories.

Children

Comments

  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : This little observation triggered a little series of changes: I renamed groups.Groupwise to users.PrivacyRelated, and the private field is now also defined in the mixin. And I moved the private_default plugin setting from comments to users.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : todo: in chatter, Bert doesn't see Andy's comments to the Hitchhiker's group.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : After some meditating I believe that the comments about a ticket should follow their ticket to the new group when somebody gives ta ticket to another team. But rather than returning to the old situation where we had no Comment.group field, I now changed the GroupwiseChecker so that when the group of...
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : Yes, the Groupwise mixin is not a solution for #5904 (Lino sites with multiple "spaces" (or ledgers or systems or communities)). Does it make sense then to have a group field on each comment? For example if I create a ticket in group A and we start to discuss about it, then change the ticket's group from A to B: should the first comments remain in group A? Or should they automa...
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : I start to realize that my basic assumption for the Groupwise mixin was wrong: we cannot replace the ledgers plugin by groups. Also Slack has "channels", which are an equivalent of the teams in Jane. I have to meditate on this.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) (1 reply) : There is still some problem with the data checker: Comment #17688 still has an empty group field although its owner (a ticket) has a group..
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : I pushed a first series of changes. Until now there is no visible advantage. Next step will be to let publisher.Page inherit from Groupwise, but before this I'd upgrade Jane and test this first series of changes.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) (2 replies) : todo: add a way to select your current group
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : I just realized that django.contrib.auth also has a Group model. But there are a few fundamental differences between user groups à la Django and user groups à la Lino. For example in Lino they are linked by Membership objects and you have at most one membership per user and group while in Django the...
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : I started updating the documentation.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) (1 reply) : It seems that also Comment will become Groupwise. Until now a comment asks its owner for the group.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : Maybe the Ticket.group field should no longer be nullable. But making it mandatory will break a few test cases and thus cause "administrative" work. The question is important if we start using groups in the meaning of the ledgers plugin.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : As a side effect, Lino Noi no longer accepts tickets without a group or whose author is not member of the group. But I'm not yet sure how to restore existing data, we will probably need a "default group".
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : I have a first implementation on my computer but I still need to meditate. In a first step, tickets.Ticket is Groupwise, but I also want publisher.Page, accounting.Journal and many others to become groupwise.
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : The groups.Groupwise mixin would add a pointer to a groups.Group and then extend get_request_queryset() to filter this record based on the user's current_group. If the user has no current_group, it would still filter to see only rows in a group for which the user ís a member. Except for SiteAdmin us...
  • 1 year, 2 months ago by Luc Saffre about #6244 (The Groupwise mixin (PrivacyRelated)) : Created new Ticket #6244 (The Groupwise mixin).