SimpleITK/Design And Proposals: Difference between revisions
Line 2: | Line 2: | ||
= SimpleITK Improvement Proposals (SIPs?) = | = SimpleITK Improvement Proposals (SIPs?) = | ||
We wish to engage and promote the SimpleITK user community in improving, guiding and evolving SimpleITK. Additionally, we want to keep these proposed changes | We wish to engage and promote the SimpleITK user community in improving, guiding and evolving SimpleITK. Additionally, we want to keep these proposed changes organized so that they can be referenced and looked upon in the future. | ||
The SimpleITK Improvement Proposals (SIPs?) are simply wiki pages, with the proposed improvement along with sections for users to comment. The author(s) is responsible to refining the proposal and linking it to a JIRA ticket to keep track of any resulting changes. | The SimpleITK Improvement Proposals (SIPs?) are simply wiki pages, with the proposed improvement along with sections for users to comment. The author(s) is responsible to refining the proposal and linking it to a JIRA ticket to keep track of any resulting changes. |
Revision as of 18:07, 5 October 2015
SimpleITK Improvement Proposals (SIPs?)
We wish to engage and promote the SimpleITK user community in improving, guiding and evolving SimpleITK. Additionally, we want to keep these proposed changes organized so that they can be referenced and looked upon in the future.
The SimpleITK Improvement Proposals (SIPs?) are simply wiki pages, with the proposed improvement along with sections for users to comment. The author(s) is responsible to refining the proposal and linking it to a JIRA ticket to keep track of any resulting changes.
The scope of a SIP is for an architecture change, a significant backwards compatibility change, or any improvement where additional feedback from the community is needed. Normal JIRA tickets should be used for bug fixes, standard improvements along the current design, along with feature requests.
SIP 000 SimpleITK Improvement Proposals Template
History
Advisory Review Board (ARB)
The initial design of SimpleITK was done as part the the ITKv4 effort and had an Advisory Review Board. The ARB was composed of groups and individual who are potential users of the Simple ITK Layer. They provided advice to ITK developers of the simple layer regarding the design and implementation of the SimpleITK API.
Survey
A Survey was conducted to aid in establishing design goals and facilitate design choices.
TCONS
There were regular TCONS with the SimpleITK team. Now SimpleITK is discussed regularly at ITK Confab of TCON.