OpenConext / OpenConext/OpenConext-manage
Interaction between revisions and requests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7
- Forks
- 13
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 7
Description
Currently, if a change-request is made (from SP-dashoard), and it is approved, the revision status in Manage will show that the approver has made changes, en the approved request is removed.
So the information of who requested the original changes, and what changes were made by the approver (if any?) are lost.
Can we think of a better way to administer this, so that the revision reflects that this was a one-on-one approval of a request?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the change-request flow between SP-dashboard and Manage, focusing on how approval changes revision status and removes the approved request. Map what information is currently lost; done means the revision preserves the original requester, approver, and any changes while representing the one-on-one approval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100