Tuesday, 2022-06-14

tkajinamgmann, hi. will we have the policy meeting today (June 14th) ?03:53
*** gthiemon1e is now known as gthiemonge13:15
gmanntkajinam: hi, we do not have meeting today. I am still collecting feedbacks from etherpads and will schedule the next meeting next week or so. 14:06
tkajinamgmann, ack. understood thanks14:06
tkajinamI haven't get any useful input from our partners so far. I'd check status of our internal discussion/checking14:07
gmanntkajinam: ack, that will be helpful 14:07
tkajinambut atm I'm not sure whether we can get actual feedback and we might need to depend on feedback only from ops/users.14:07
tkajinamanyway let's see14:07
gmannyeah, that's true. we will take call based on that or if any other we are able to get. 14:08
dansmiththe feedback from the etherpads I've seen has been pretty much what I expected,14:08
dansmithwhich is "reader role: yes, service role: yes, system scope: wtf is system scope?"14:08
tkajinamyeah14:09
dansmithand also some of "people are already confused enough with admin, system scope will create more issues"14:09
tkajinamit might be enough to prioritize reader and leave scope now, as we discussed earlier. or leave scope just optional... a problem with that would be we'd need a different mechanism to differentiate project reader and system reader14:13
tkajinamit might be a problem, though. since we required project scope for project resources, a project reader can't get list of all instances while system reader can't access project resources14:13
tkajinamit might be already a problem *14:14
gmannyeah, if we leave scope then there is no system reader14:14
* tkajinam does not have full understanding about the current implementation of reader14:14
dansmithyeah, my suggestion is that we decouple scope, move it to the end of the list and pursue the persona roles, service role, etc and get this actually turned on for people14:14
gmannanyways let me schedule meeting next week and will send invite and discuss the feedback and the next step14:15
tkajinamyup14:15
gmannyeah, that seems reasonable step in current situation 14:15
dansmithtbh, we could have a standard role called system_reader (we need a better name to avoid confusion) and handle the system reader thing without any more complication than that14:15
tkajinamit's all good, as we are getting feedback what we expected and was concerned about.14:16
tkajinamyeah > the system-reader role.14:18
*** dasm|off is now known as dasm14:31
*** lajoskatona_ is now known as lajoskatona15:24
*** dasm is now known as dasm|off21:02

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!