{"action":"opened","issue":{"url":"https://api.github.com/repos/sigmavirus24/github3.py/issues/605","repository_url":"https://api.github.com/repos/sigmavirus24/github3.py","labels_url":"https://api.github.com/repos/sigmavirus24/github3.py/issues/605/labels{/name}","comments_url":"https://api.github.com/repos/sigmavirus24/github3.py/issues/605/comments","events_url":"https://api.github.com/repos/sigmavirus24/github3.py/issues/605/events","html_url":"https://github.com/sigmavirus24/github3.py/issues/605","id":151984146,"number":605,"title":"Organization.events should be public_events","user":{"login":"bboe","id":48100,"avatar_url":"https://avatars.githubusercontent.com/u/48100?v=3","gravatar_id":"","url":"https://api.github.com/users/bboe","html_url":"https://github.com/bboe","followers_url":"https://api.github.com/users/bboe/followers","following_url":"https://api.github.com/users/bboe/following{/other_user}","gists_url":"https://api.github.com/users/bboe/gists{/gist_id}","starred_url":"https://api.github.com/users/bboe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bboe/subscriptions","organizations_url":"https://api.github.com/users/bboe/orgs","repos_url":"https://api.github.com/users/bboe/repos","events_url":"https://api.github.com/users/bboe/events{/privacy}","received_events_url":"https://api.github.com/users/bboe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-29T22:52:01Z","updated_at":"2016-04-29T22:52:01Z","closed_at":null,"body":"I just discovered that `Organization.events` lists only the public events of an organization, and excludes the events to private repositories. The resource that includes private events is:\r\n\r\n    GET /users/:username/events/orgs/:org\r\n\r\nSource: https://developer.github.com/v3/activity/events/#list-events-for-an-organization\r\n\r\nIt seems there should be two functions which seems could either be named:\r\n\r\n* `events` -- all events (must be a member of the organization)\r\n* `public_events` -- all public events\r\n\r\nor\r\n\r\n* `all_events` -- all events (must be a member of the organization)\r\n* `events` -- all public events\r\n\r\nThe latter doesn't seem like a good fit, however, as `all_events` corresponds to public events at the top-level: https://github3py.readthedocs.io/en/latest/api.html?highlight=all_events#github3.all_events\r\n\r\nHowever, using the former requires a breaking change to what currently exists in the alpha version. Since 1.0 is in alpha that could be okay, but may break people's code who aren't locking their dependencies on the precise alpha version.\r\n\r\nI'm happy to implement the function when I get a chance, I would just like to know which of these naming schemes is preferred (or another one altogether). Thanks!"}}