-
Notifications
You must be signed in to change notification settings - Fork 133
Document how OG handles access and permissions #693
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great writeup thanks!
Sometimes we write OG sometimes Organic Groups, I'd try to be consistent and use Organic Group everywhere but I'll let you decide.
We should probably also reference this document from the README.md
Co-authored-by: Maarten Segers <MPParsley@users.noreply.github.com>
I usually write the first occurrence in the doc as "Organic Groups (OG), ...", and then continue with OG |
Adding to the milestone since this is closely related to the work done to OG Access in the upcoming release, it would be good to also include this documentation along with the changes. |
This has already been approved, but changes were made afterwards. @amitaibu or @MPParsley do these changes look OK? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, looks great, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge this. The phpcs issues are not related to this PR.
Error in Travis will be fixed in #720.
|
Thanks! Good job preparing the release, unfortunately I don't have the availability to assist at the moment. |
Fixes #510.