Skip to content

Find and Assign Small Improvement Issues

Problem Statement

Who will benefit?

  • External Team (e-valuation) will benefit from clarity of team action
  • Course Instructor will benefit from clarity of actions
  • Team Members will benefit from lack of ambiguous tasks
  • Other volunteers will benefit from

Benefits and risks

  • EvaP Team benefits from more clear communication of intent
  • EvaP Volunteers benefit from more understandable process
  • Course Instructor benefits from more understandable process
  • Team Members benefit from more refined work process
  • Team Members at risk of getting confused/bogged down in these steps

Proposed solution

Deliverable

  • Primarily Documentation in the Repo itself (Contributing)
  • New Issues should be generated from this

Priority/Severity

  • High (This will bring a huge increase in performance/productivity/usability/legislative cover)
  • Medium (This will bring a good increase in performance/productivity/usability)
  • Low (anything else e.g., trivial, minor improvements)

Step Template for Follow On Issues

  1. Find an Issue on GitHub
  2. Explore Issue Details
  3. Attempt to Recreate Issue in Code/Locate Source of Error
  4. If solution is apparent, create a notifying message on the issue on GitHub
  5. Create a mirror issue in this repo's issue tracker
  6. Make a new branch on the local GitLab mirror of EvaP and name it after the issue (like 1663-prioritize-grading)
  7. Comment a link to your branch on the GitLab issue you opened and on the original GitHub issue
  8. Commit your changes and run tests to the local mirror
  9. Once satisfied, create a new Pull Request on the EvaP GitHub repo
  10. Update issues with details once submitted

Tasks

  • Create Detailed Issue
  • Update Decisions (Cancelled)
  • Notify Team of More Details on Contributing
  • Update Contributing
  • Write More detailed explanation of contribution process (Cancelled)

Notify

@cap399 @ets43 @hn374 @jp3592 @pjm349

Edited by Peter Mangelsdorf