Thorough example code
Quality example code will be necessary for this SDK to gain user uptake. This project aims to be useful for developers both inside and outside of the OpenStack project, and as such, it must cater to a wide range of knowledge and abilities.
Example code should make no assumptions that users of the SDK have insider knowledge of the APIs they're using. While examples should certainly support advanced and deep use cases of the services, it should not require implementation knowledge, for example.
Examples do not replace documentation.
Blueprint information
- Status:
- Complete
- Approver:
- Terry Howe
- Priority:
- Essential
- Drafter:
- Brian Curtin
- Direction:
- Needs approval
- Assignee:
- Terry Howe
- Definition:
- Approved
- Series goal:
- Accepted for master
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Terry Howe
- Completed by
- Terry Howe
Related branches
Related bugs
Sprints
Whiteboard
I think most of the example code should be related to the feature that is being developed, but I'll call this done when the jenkins example is merged:
https:/
I think we could use some more examples, but are we good enough to call this bp done?
