Are you sure you want to delete this task? Once this task is deleted, it cannot be recovered.
i-robot bc3332b511 | 2 years ago | |
---|---|---|
.. | ||
XXX-mep-template | 2 years ago | |
mep-adaptive | 3 years ago | |
mep-ai4earth | 3 years ago | |
mep-akg | 3 years ago | |
mep-datacompliance | 2 years ago | |
mep-dx | 3 years ago | |
mep-gnn | 3 years ago | |
mep-mm | 3 years ago | |
mep-mslite | 3 years ago | |
mep-parallel | 3 years ago | |
mep-quantum | 2 years ago | |
mep-reinforcement | 2 years ago | |
mep-research | 3 years ago | |
mep-serving | 2 years ago | |
mep-usability | 2 years ago | |
README.md | 3 years ago |
A MindSpore Enhancement Proposal (MEP) is a way to propose, communicate and coordinate on new efforts for the MindSpore project. The MEP guidelines adopted here is heavily
influenced by the Kubernetes Enhancement Proposals (KEPs) designed by Kubernetes community.
NOTICE: For similar structures some of the same wordings from KEPs are borrowed to adhere to the originally construed meaning.
More or less, yes.
Having a rich set of MEPs in one place will make it easier for people to track
what is going in the community and find a structured historical record.
MEPs are required for most non-trivial changes. Specifically:
Beyond these, it is up to each SIG to decide when they want to use the MEP
process. It should be light-weight enough that MEPs are the default position.
Our aim with MEPs is to clearly communicate new efforts to the MindSpore contributor community.
As such, we want to build a well curated set of clear proposals in a common format with useful metadata.
Benefits to MEP users (in the limit):
We are inspired by Kubernetes KEPs, IETF RFCs, Python PEPs and Rust RFCs.
Almost all MEPs should go into SIG subdirectories. In very rare cases, such as
MEPs about MEPs, we may choose to keep them in the root.
Things we'd like to see happen to consider MEPs well on their way:
Even so, the process can evolve. As we find new techniques we can improve our processes.
MEPs are now prefixed with their creation time (eg. yyyy-mm-dd). This gives
both the MEP a unique identifier and provides an easy breadcrumb for people to
find the issue where the current state of the MEP is being updated.
MindSpore community
Markdown Python Jupyter Notebook Text Diff other
Dear OpenI User
Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.
For more agreement content, please refer to the《Openl Qizhi Community AI Collaboration Platform Usage Agreement》