Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue Type

Definition for Sakai

Bug

An error in design or implementation which directly impedes a user from achieving their expected result.

Task

A new capability being added to Sakai.

Feature Request/Requirement

A desired capability, for inclusion in a future release of Sakai; ideas that come with resources interested in implementing them are more likely to be developed than those offered with the hope that someone else will step forward to do the work.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7306bd10d0d63bf9-b24c2323-4ad2457d-aeae9f97-384bae7ecd39a9469c9fb2e3"><ac:plain-text-body><![CDATA[

Contributed Patch

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!]

]]></ac:plain-text-body></ac:structured-macro>

...

  • Issue is vetted for accuracy and completeness of information.
  • A matching Bug or Feature Request issue is generated (Cloned) to track Sakai's design and development progress on addressing the issue and is linked ; cloning auotmatically links it to the original Contributed Patch issue.
  • What exactly happens next is being determined as part of our ongoing development of a community requirements process. The current practice is: Contributed Patches, like Feature Requests, are evaluated for inclusion in a Sakai releaseThe issue is evaluated, just like a Feature Request or Requirement.
    • In some cases, a Contributed Patch may run counter to the Sakai design and cannot be incoporated, then the corresponding Bug or Task issue will be marked as Won't Fix and an explanation as to why provided. In this case, the contributor of the Patch may choose to continue developing the patch for future versions of Sakai.
  • When the Bug or Task is addressed, either by integrating the patch into Sakai or develop another solution with the same outcome, the Bug or Task is Resolved as normal and goes on to QA. The oringal Contributed Patch issue can be Closed at this point with a comment pointing to the Resolved issue.
  • Until the patch is integrated in Sakai, the community encourages the contributor to be responsive to comments and feedback provided by other users of the patch and to continue to update the patch to current versions of Sakai.

General Workflow by Task

Anchor
Requirements
Requirements
Requirements/Design

...