Project:Package Manager Specification/Future EAPI process

Requirements for a future EAPI proposal
For a change to be included in a future EAPI, the four following tasks need to be done (in any order):
 * 1) A future EAPI bug needs to be open for the change. The bug should shortly describe the change. It should be used to track the progress and feedback on the change until it is eventually included.
 * 2) A patch for the PMS needs to be prepared and approved. The PMS team will review the patch for factual correctness, clarity and consistency with the document style. The team may also have useful remarks regarding the patch but it will not reject it even if they disagree with the idea.
 * 3) A reference implementation for Portage needs to be prepared and approved. The Portage team will review it for inclusion.
 * 4) The change needs to be discussed on the gentoo-dev mailing list. For simple changes, the discussion as part of the Council agenda proposal may be enough. However, for more complex or controversial changes, starting a dedicated thread early is recommended.

Some of the teams or developers may offer to do some of the above steps for your idea. However, they are not required to do so. Furthermore, a promise that a team will do the work is not equivalent to it actually being done.

Please note that while a change might be tentatively included in the next EAPI proposal before all of the above steps are complete, the Council can remove it afterwards if the implementation is getting delayed or it is complex/controversial and did not receive enough time for discussion and/or testing.