- General Workflow
Definition for Sakai
An error in design or implementation which directly impedes a user from achieving their expected result.
A new capability being added to Sakai.
A desired capability, which may be selected for implementation in a future release of Sakai.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b3211f19cbd3b1d2-bdc5bbd7-415d42fc-bb6a847b-f7206b99b2a7aecea19b7a04"><ac:plain-text-body><![CDATA[
A community-contributed patch to a particular version of sakai. The origin of such issues may lie in Bugs or Feature Requests which Sakai has not yet evaluated for implementation. Under such circumstances a linked issue is generally created by cloning the orignal issue in order to track Sakai's work on the issue. [Use at your own risk!]
- Issue is vetted for accuracy and completeness of information.
- What exactly happens next is being determined as part of our ongoing development of a community requirements process. The current practice is:
- Feature Requests are evaluated by designers and developers for inclusion in a future Sakai release. This generally occurs right after a release is completed, though by no means is limited to this time-frame.
- Feature Requests selected for incorporation are converted to one or more Tasks to track the actual implementation work.
The requirements process is still under development. During the the first requirements gathering phase over 300 issues were submitted. A rough attempt to clump and cluster related requirements resulted in over 200 requirements put forth to the greater Sakai community and the Sakai Institutional Reprsentatives for polling on relative importance; see results.
Requirement Issues which are adopted by existing Project Management Committees or Project Teams will be handled as Feature Requests are above; coverted to one or more Tasks in the Sakai Jira project to track its implementation. For requirements which are being worked on by volunteers in collaboration with existing Project Teams, the Requirements should be converted to either one or more Tasks or a Contributed Patch, depending the level of intereaction and commitment to integration with Sakai in the desired time-frame.