| Section | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
OLE Contribution Requirements
| Enhancement/Functional Bug Process | Technical Bug Process | Documentation Process |
|---|---|---|
|
|
|
Contribution Checklist
| Note |
|---|
You must have a CLA/CCLA agreement signed and turned in to the Operations Manager, Megan Nolan. |
Proposal
Provide functional requirements (template) and acceptance criteria so others know how the contribution is supposed to work.
Note the expected delivery date for the functionality on the JIRA ticket
- What technologies are being used (KIM, KNS, KRAD, other libraries, and why?). See "Additional Resources for Contributions" below
- What access would we have to the contributor for questions? - Add to note section
...
Documentation Lead will conduct a review of the documentation to ensure documentation is complete. For documentation types and instructions, see Documentation Standards and Best Practices. Once satisfied, documentation is incorporated into the core documentation code by the Documentation Lead.
...
Review the License Agreement Process.
- Follow the 3rd Party Evaluation Process if you are considering using 3rd party code in work for the Kuali OLE.
Refer to the Kuali Application Security Working Group for security training and recommendations
Refer to the Kuali Rice Policies and Standards including the Kuali Rice Development Standards for code coherence tips.
Other Ways to Contribute
...