-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to Collaborators section coming in later #295
Comments
@Preeticp are you okay to take ownership of this? |
As of now, I am not covering Auth, I thought you were @mishaone. Either ways, I can take the ownership. Eventually this issue, most likely, would need to be split into multiple smaller issues dealing with different services at which point I might need help, depending on my backlog at the time. |
Yep, I'm covering whatever is needed, @Preeticp but since you reported this change, I thought you might be the best person to keep an eye on it. I can take it on if you don't have the bandwidth. |
Sounds good, will assign myself. Afaik, it is to be still implemented, so will try to pick up/limit issues keeping this in mind around the time it will be implemented. |
Great, thanks! If you find you don't have the bandwidth when there is something actionable for this or any other issue, please do just pass it on or use the help wanted tag. |
Checked with Dev, slated for around middle of J train |
Presentation link: https://docs.google.com/presentation/d/1doJGnM2OlZVWkD9ETq1dJf8Dyf9CoajZRUx_G0x0VJA/edit?usp=sharing Blue Jeans Link: https://bluejeans.com/s/Os4mi |
Spreadsheet by Planner team(interested folks please add your comments/inputs to this document): DOC: https://docs.google.com/spreadsheets/d/1ALVEMyI_i5dvOwx_0ChN9WvlyGhHkCwchylje2SrpdQ/edit?ts=5b3206d6#gid=0 Spreadsheet by Auth team: Auth team's presentation on 'Permissions' from IC: Link to the meeting recording: As per the meeting, Planner is to be a first client for auth. |
As per the kabal session today, Collaborators section could change to Users and Roles. This should be in post I train.
Some of the changes mentioned:
Note all this is merely in discussion phases as of now, and we can expect a lot of churn before they are implemented.
Considering the nature of the feature, it would affect all the services in varying degrees.
The text was updated successfully, but these errors were encountered: