[YUNIKORN-999] [UMBRELLA] Define and publish YuniKorn Improvement Proposal (YIP)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Component/s: community, documentation, website
• Labels: documentation
• Assignee: Bowen Li
• Reporter: Bowen Li
• Created: 07/Jan/22 23:13
• Updated: 23/Feb/24 15:47
• Resolved: 23/Feb/24 15:47

Description

In dev mailing list, we have discussed and voted to have YuniKorn Improvement Proposal (YIP).

 
a YIP will define the following parts, including but not limited to:

• what's considered a "major change" that needs a YIP
• what should be included in a YIP (e.g. motivation/business justifications, use case requirements, proposed changes, API changes, migration/compatibility, rejected alternatives, etc)
• who should initiate or be involved in a YIP
• end-to-end process
   
  This is an umbrella and will create subtasks.
   
  We can publish the YIP process to website, and keep all finalized YIP in Confluence. There're projects keeping their XIPs on confluence but I found that is 1) hard to track changes and version control 2) hard to comment or propose changes as not everyone has confluence access . Keep YIP itself on website will solve those issues and make it easier to find.

Sub-Tasks

• YIP: define and publish section of "definition of 'major change' that needs a YIP": Closed
• YIP: define and publish section of "what should be included in a YIP": Closed
• YIP: define and publish section of "who should initiate or be involved in a YIP": Closed
• YIP: define and publish end-to-end process of a YIP: Closed