Difference between revisions of "Meetings/KeystoneMeeting"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
| Line 11: | Line 11: | ||
* High priority code reviews | * High priority code reviews | ||
** [https://review.openstack.org/#/c/38308/ Allow policy enforcement on the target of an API] | ** [https://review.openstack.org/#/c/38308/ Allow policy enforcement on the target of an API] | ||
| + | * Keystone client public/private (Brant) | ||
| + | ** See http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces | ||
| + | ** Not following this convention today. So what do we do? | ||
| + | *** Interpret the way it is for the code that exists (essentially everything is private) | ||
| + | *** Start a new code base that follows the convention. Deprecate old codebase? | ||
* Open discussion | * Open discussion | ||
Revision as of 22:36, 19 August 2013
Weekly Keystone team meeting
If you're interested in identity for OpenStack, we hold public meetings weekly in #openstack-meeting, on Tuesdays at 18:00 UTC. Please feel free to add items to the agenda below with your name and we'll cover them.
Agenda for next meeting
- Announcement: FeatureProposalFreeze August 28th
- Reminder: Havana milestone 3 cut September 4th
- Critical issues?
- Pagination vs FeatureProposalFreeze
- High priority code reviews
- Keystone client public/private (Brant)
- See http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces
- Not following this convention today. So what do we do?
- Interpret the way it is for the code that exists (essentially everything is private)
- Start a new code base that follows the convention. Deprecate old codebase?
- Open discussion
Previous meetings
Logs and meeting summaries of previous meetings are located here.
