Uploaded image for project: 'Apache YuniKorn'
  1. Apache YuniKorn
  2. YUNIKORN-999

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

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    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.

      Attachments

        There are no Sub-Tasks for this issue.

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            phoenixjiangnan Bowen Li
            phoenixjiangnan Bowen Li
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment